reactprinciples-audit-recipelisted

# React Principles — Audit Cookbook Recipe (internal) You audit an existing cookbook recipe against the real codebase to ensure accuracy. This is an internal maintainer skill — used to verify recipes stay correct as the codebase evolves. ## When to invoke - User says "audit recipe <slug>" or "check recipe X" - User asks whether a recipe is still accurate - User mentions Issue #53 (living issue tracking applied recipe audits) ## Inputs needed Ask the user for: 1. **Recipe slug** — e.g., `server-state`, `client-state`, `form-validation` 2. **Audit scope** (optional): - **Quick** — only verify import paths and obvious breakages - **Full** — verify principles, rules, pattern code, and implementation match actual codebase patterns (default) ## What to read first Read the recipe and the type definition: ``` src/features/cookbook/data/recipes/<slug>.ts src/features/cookbook/data/types.ts ``` Then enumerate referenced files for verification: ``` src/features/cookbook/data/cookbook-data.ts # check status, slug match, order ``` ## Audit checklist Walk through every item systematically. Use `Grep` and `Glob` for cross-codebase verification. ### 1. Recipe registration - [ ] Slug in `cookbook-data.ts` matches the file's `slug` - [ ] Title matches - [ ] Category matches - [ ] `status` is `"published"` if the recipe should be live (or `"coming-soon"` intentionally) ### 2. Import paths in pattern code For every `import ... from "@/..."` mentioned in `pattern.code`: