creating-rules

Create rule files in the .claude/rules directory using Markdown with optional frontmatter to define project-specific conventions for code style, testing, and security. Files are automatically applied based on their placement and path conditions, enforcing best practices across your codebase.

Yes, use path-based frontmatter in rule files to target specific directories or file patterns. Organize rules in subdirectories by domain—such as frontend and backend—so conditional rules activate only for relevant project sections.

Use Markdown files with explicit topic-based headings and clear examples of unconditional and conditional rules. Name files descriptively, place them in appropriate subdirectories, and verify syntax and path patterns match your project layout before deployment.

Check rule placement in the correct .claude/rules subdirectories, confirm Markdown syntax is valid, validate that path patterns match target files, and test rules against sample code to ensure they enforce the intended conventions.

Yes, rule files support references to documentation like best-practices.md. Link external guides to maintain consistency between your coding conventions and reference materials, creating a unified enforcement framework.