/astro-builder:audit

/astro-builder:audit

You are auditing this Astro 6 project for quality issues. Run a thorough inspection across four categories, then produce a prioritized report.

Step 1 — Load project context

Read:

1. CLAUDE.md — project rules and quality gates.
2. .astro-builder/anti-patterns.md — project-specific anti-patterns.
3. .astro-builder/content-schema.md — expected content structure.
4. .astro-builder/style-guide.md — writing rules.
5. astro.config.ts — i18n config, integrations, adapter.
6. src/content.config.ts — collection schemas.

Also read the canonical Astro 6 anti-patterns from docs/astro-patterns.md.

Step 2 — Architecture audit

Check for violations of the page-views pattern:

• Thin pages: Every file in src/pages/ should be ≤5 lines — a single import and component render. Flag any page that contains markup, data fetching, or logic.
• Page-view imports: Every page-view in src/page-views/ should use Astro.currentLocale — flag any that accept a lang prop instead.
• No prop threading: Components should never receive lang or tl as props — each resolves its own locale. Grep for lang={ and tl={ in component calls.
• Config file location: src/content/config.ts must not exist. Only src/content.config.ts is valid.
• Astro config extension: astro.config.mjs must not exist. Only astro.config.ts is valid.

Step 3 — i18n audit

• Missing locale pages: For every page in src/pages/en/, check that a matching page exists in every other configured locale folder. List missing pages.
• Missing translation keys: For every key in src/i18n/en.json, check that the same key exists in all other locale JSON files. List missing keys with the English fallback value.
• Missing translationKey: For every content entry, check that translationKey is set. Flag entries that are missing it.
• Unlinked translations: For entries that have translationKey, verify a matching entry exists in every configured locale. List entries with no translation.
• Hardcoded strings: Grep .astro files for literal English text outside of tl() calls (e.g. >About<, >Home<). Flag suspected hardcoded UI strings.

Step 4 — Content schema audit

For each content collection defined in src/content.config.ts:

• Check that all content files have all required frontmatter fields.
• Check that lang values match valid configured locales.
• Check that date fields are valid ISO dates.
• Check that tags are arrays (not strings).
• Flag any files with frontmatter errors.

Step 5 — Style guide audit

Read .astro-builder/style-guide.md and check a sample of 5 content files per collection:

• Does the tone match the defined voice?
• Are sentences within the defined length guidelines (if specified)?
• Are there obvious grammar issues or inconsistencies?

This is a best-effort check — report findings but don't auto-fix style issues.

Step 6 — Build validation

Run pnpm build. If it fails, include the full error output in the report as a P0 issue. Run tsc --noEmit. Include any TypeScript errors as P0 issues. Run biome check . if Biome is configured. Include lint errors as P1 issues.

Step 7 — Report

Produce a structured report in this format:

## Audit Report — {date}

### P0 — Must fix (build broken or data loss risk)
- [ ] {issue description} → {file:line} → {suggested fix}

### P1 — Should fix (correctness or i18n gaps)
- [ ] {issue description} → {file:line} → {suggested fix}

### P2 — Nice to fix (style, consistency, minor issues)
- [ ] {issue description} → {file:line} → {suggested fix}

### Summary
- Files audited: {n}
- Issues found: {P0: n, P1: n, P2: n}
- Build status: PASS / FAIL

After presenting the report, ask: "Would you like me to fix all P0 and P1 issues automatically?"

If yes, fix them autonomously, then re-run pnpm build and tsc --noEmit to confirm all P0/P1 issues are resolved.

Constraints

• Never auto-fix P2 style issues without asking.
• Never modify content body text during the audit without explicit instruction.
• Always follow the Astro 6 documentation: https://docs.astro.build/llms-small.txt