aif-rules

You can enforce project conventions by automatically aggregating new policies into a central RULES.md artifact. This approach applies project-specific policies across the codebase using deterministic rule creation with conflict checks.

To add a new project convention rule safely, append it to the central RULES.md file using a process that includes conflict checks. This ensures deterministic rule creation and safe integration into your existing implementation workflow.

Yes, config.yaml supports area-specific rules by loading project-specific overrides from the .ai-factory directory. Area-aware registration ensures specific rules are mirrored in the configuration for accurate policy enforcement.

The best way to maintain consistent coding standards is by automatically consolidating policies into a central RULES.md file. Loading context overrides from config.yaml guides updates and ensures safe integration into automated implementation workflows.

Project conventions may not apply correctly if skill-context overrides in .ai-factory are not loaded properly. Deterministic rule creation requires loading these context-aware updates from config.yaml to guide accurate policy enforcement across the codebase.