convention-enforcer

To enforce code conventions automatically, you need a tool that analyzes repository manifests for established styles like camelCase or snake_case and applies them during code generation. This skill detects existing patterns and ensures new code adheres to them.

The best way to ensure file organization compliance is to analyze the repository's directory structures for routes, models, and tests. This skill directs newly generated files to their appropriate directories based on those detected patterns.

Standardizing error handling requires enforcing consistent patterns like try-catch or .catch() across the codebase. This skill ensures compliance with these specific error handling patterns during code generation.

Yes, you can ensure test files match repository patterns by analyzing whether the project uses co-located tests or a separate directory. This skill enforces testing pattern adherence based on the detected structure.

Yes, naming convention enforcement works with snake_case and PascalCase styles. The skill detects the repository's established naming conventions for variables, functions, and classes, then ensures generated code matches them.

Generated code misses directory structure conventions when the generation process lacks repository manifest analysis. This skill solves that by analyzing manifest patterns for routes and models to direct new files appropriately.