app-rules-architect

To prevent product decision drift, extract recurring product decisions and formalize them into reusable rules at the principle, app, and feature levels. This codifies guidance into structured documentation like APP_RULES.md templates to ensure consistent behavior across teams.

Documenting product rules for governance involves separating universal principles from project-specific guidance. You generate reusable outputs such as PRODUCT_PRINCIPLES.md and APP_RULES_TEMPLATE.md files to accelerate alignment and guide ongoing rule governance across projects.

Extracting and categorizing product rules involves identifying recurring decisions and formalizing them into a structured hierarchy. You organize these into principle, app, and feature rule categories to build a durable rules framework for multiple product domains.

Yes, you can apply a single rules template across multiple product domains. The system separates universal principles from project-specific guidance, allowing shared UX decisions to be codified into a durable framework ensuring consistent behavior across different apps.

To start capturing reusable product rules, you simply create or update an APP_RULES.md file. This serves as the foundational template to begin extracting, categorizing, and documenting your team's product decisions for ongoing alignment.