project-rules-design

To structure engineering documentation, you inventory existing rules and restructure them into domain-based folders. This creates a stable architecture with an entrypoint like CONTRIBUTING.md and per-domain indexes under docs/ to ensure consistent navigation and AI routing.

Organizing project rules by domain involves defining clear boundaries between architecture, coding, UI, and AI-guide areas. You assign responsibilities to each domain and establish index.md and rules.md files per domain to clarify governance and identify coverage gaps.

To migrate project rules, you apply domain classification using reference patterns like shadcn-admin. This guides the transition to a target structure with domain indexes, references, and optional asset folders, while flagging coverage gaps against stack checklists.

You should audit your engineering rules system when your project lacks clear boundaries between architecture, coding, UI, and AI-guide domains. An audit clarifies rule responsibilities, identifies framework gaps, and establishes stable entry points for consistent navigation.

Yes, you can define boundaries between architecture, coding, UI, and AI-guide rules. The process involves assigning specific responsibilities to each domain and creating separate index.md and rules.md files to maintain clear governance and structural separation.

Creating a CONTRIBUTING.md entrypoint involves establishing it as the central navigation point for your engineering rules. It routes users and AI to per-domain indexes under docs/, ensuring consistent access to architecture, coding, and UI guidelines.