project-rules

You can enforce coding conventions by referencing a central rules file to validate naming consistency, file structure, error handling, and type safety against established project architecture decisions automatically.

Automated checks for naming consistency and file structure validate your codebase against predefined project rules, ensuring architectural alignment and detecting policy violations during the development workflow.

Validating current context reads active task details and goals to ensure ongoing work remains consistent with established coding conventions, architecture principles, and specific project prohibitions.

Yes, project rule enforcement supports automated checks specifically for type safety, error handling inclusion, and policy violations to maintain consistent code quality across the software project.

You need to define your coding conventions, architecture principles, and naming rules in a memory file, plus a current context file detailing active tasks to enable automated validation checks.

Automated project rules validation is limited when your development context lacks defined architecture decisions or naming conventions, as the checks rely entirely on referencing established rule files.