aif-best-practices

To establish universal code quality guidelines, apply centralized rules for naming conventions, directory structures, and API boundaries. This enforces maintainability and consistency across multiple languages and tech stacks during onboarding and refactoring.

A comprehensive code review checklist for maintainability should cover naming conventions, directory structures, API boundaries, error handling, and testing practices. Using a centralized reference ensures consistent peer reviews across the entire team.

Yes, you can enforce project-specific overrides for error handling and testing practices using skill-context rules. This allows teams to apply universal standards while respecting SKILL.md frontmatter and body configurations during implementation.

The best way to standardize naming conventions and directory structures is implementing a centralized best practices reference. This provides clear API boundaries and consistent guidelines that reduce onboarding friction and maintenance costs.

Applying coding standards helps during onboarding and refactoring by providing a centralized reference of best practices. This reduces onboarding friction for new developers and ensures reliable, maintainable code modifications during structural improvements.

No specific dependencies are required to support code quality best practices across multiple languages. The guidelines act as a universal framework applicable to various stacks, ensuring consistent structure, testing, and code reviews without external tool limitations.