creating-rules

You create Claude rules by structuring and documenting best-practice rule files under the .claude/rules directory, applying frontmatter conventions and folder layouts to ensure each rule is machine-discoverable and maintains consistent project standards.

The recommended folder structure organizes Claude rule files under .claude/rules across multiple project directories, applying specific naming conventions and frontmatter structure to support team sharing, automation, and machine-discoverability.

Frontmatter structure in markdown rule templates standardizes metadata at the top of each file under .claude/rules, ensuring the rule is well-scoped and descriptive for automated parsing and machine-discoverability.

Yes, you can establish testing guidelines and security requirements by creating topic-specific rule files under .claude/rules, using provided templates to standardize coding styles and security practices across project directories and teams.

The best way to organize markdown guidelines is applying a structured folder layout under .claude/rules, using consistent naming conventions and frontmatter to keep rules well-scoped, descriptive, and machine-discoverable across multiple project directories.

No dependencies are required to set up best-practice rules; you simply create markdown files under .claude/rules with proper frontmatter structure, following the provided templates and folder layout guidance for organization.