standards-kit

You can enforce code quality by applying automated rules that restrict cyclomatic complexity under 8 and forbid console.log, magic numbers, and unused imports. This ensures strict code hygiene and reduces brittle logic during everyday implementation.

To restrict UI components to approved libraries, apply an approved UI-only policy that limits component creation to shadcn, Aceternity UI, or Magic UI. This aligns teams on visual consistency and prevents UI divergence across the project.

Standardize code structure by enforcing PascalCase for UI and Types, camelCase for Logic, and applying strict import ordering. This improves readability and generates cleaner diffs during refactoring and component creation.

Yes, you can apply these standards to everyday implementation and refactoring tasks. It enforces unified development and design standards across code changes, component creation, and logic updates to prevent inconsistent code quality.

Keeping cyclomatic complexity under 8 reduces brittle logic and maintenance risk. Enforcing this complexity limit during code changes ensures your codebase remains readable and easier to maintain across logic updates.