Cookbook

Requirements use RFC 2119 keywords correctly, are independently testable, and describe behavior rather than implementation.

No section is empty without explanation, all gaps are tracked with NEEDS REVIEW, and edge cases and test vectors provide comprehensive coverage.

Recipe aligns with applicable cookbook guidelines and does not contradict platform-wide principles for security, accessibility, and error handling.

Naming, structure, and depth are consistent across sibling recipes so the cookbook reads as a coherent whole.

Recipe accurately captures what the source code does without invention, idealization, or omission of documented quirks.

Recipe follows the standard template structure with valid frontmatter and all required sections in correct order.

Comprehensive lint checklist for validating Claude Code agent structure, content quality, and best practices

Reference for Claude Code agent file format, frontmatter fields, tool access patterns, and permission modes

Best practices for creating Claude Code skills, agents, and rule files.

Comprehensive lint checklist for validating Claude Code rule file content quality, best practices, and optimization

Reference for Claude Code rule file format, quality criteria, optimization guidelines, and comparison with skills and agents

Comprehensive lint checklist for validating Claude Code skill structure, content quality, and best practices

Reference for Claude Code skill directory layout, frontmatter fields, string substitutions, and invocation control

Properties that test vectors in cookbook artifacts (ingredients, recipes) should exhibit — adapted from Kent Beck's Test Desiderata.

How to write test vectors in cookbook artifacts — use AAA structure, one concept per vector, descriptive names.

Canonical platform design sources that cookbook artifacts MUST reference when specifying UI behavior, spacing, and appearance.