content-auditlisted

# content-audit Audit prose against `content-design.md`, and report violations with suggested rewrites. ## When invoked Use this skill when asked to audit copy, check prose quality, find AI-writing tells, or review text against the content guide — phrases like "content audit", "audit the copy on the homepage", "does this read like AI", "check this against content-design.md". ## Instructions 1. **Determine scope.** Accept one of: - A specific file path (a page, a data file, a markdown doc) - `site-updates` → `website/src/data/site-updates.json` (titles + story bodies) - `registry` → the `description` fields in `src/components/registry.json` - `case-studies` → the `title` and `dek` fields in `website/src/data/case-studies.json` (shipped copy on /work and the home page) - `readme` → `README.md` prose plus `src/stories/Configure.mdx`. README's marked regions (`component-count`, `component-list`, `npm-badge`) are **generated** from `src/components/registry.json` — a rewrite inside them silently reverts on the next build, so fix that copy through the `registry` scope instead; the `/blueprints` page copies under `website/public/` are generated too (synced from the root specs by `scripts/sync-blueprints.mjs` on every build), so edit the root file, never the copy - `skills` → the `displayDescription` frontmatter strings across `.claude/skills/` (they render on /skills, so they are published copy; skill instruction *bodies* are out of scope) - `website` → user