am-command-init-rules

To create project-specific rules, apply discovery, configuration, and generation phases to surface internal conventions and anti-patterns, then output structured rule files under the rules/ directory with YAML frontmatter describing each rule.

Non-obvious codebase rules are internal conventions, module boundaries, and edge cases that aren't immediately apparent from reading the code; you need them to formalize governance and prevent anti-patterns across a growing repository or monorepo.

You can codify anti-patterns by analyzing repository conventions and framework configurations, using a question tool to gather global and path-specific contexts, and then generating actionable, topic-based rule files for future enforcement.

Yes, you can scope project-specific rules by file paths; the generation process captures both global and path-specific contexts to ensure rules apply precisely to the relevant modules and directories within the codebase.

The best way to formalize repository governance is through discovery-driven rule authoring that analyzes existing patterns and outputs structured rule files with frontmatter, creating a standardized format for future automated enforcement.