Global Conventions

Enforce consistent project structure by establishing global conventions for directory organization (src, public, components, pages), configuration files (astro.config.mjs, tsconfig.json, package.json), and environment variable management. This standardization reduces onboarding friction and prevents technical debt from inconsistent practices.

Organize environment variables using standardized configuration files and naming conventions defined in your project's global conventions. Centralized environment variable governance ensures consistency across development, staging, and production while preventing configuration drift.

Implement conventional commits by establishing messaging standards that guide commit structure and content across your team. Conventional commit practices improve version control clarity, enable automated changelog generation, and streamline code review workflows.

Yes. By defining global conventions for project structure, naming, and development practices, you direct AI to generate code that adheres to your standards rather than creating inconsistent implementations requiring manual rework.

Project documentation standards should cover READMEs with consistent structure and ADRs (Architecture Decision Records) that document decisions systematically. Standardized documentation practices accelerate onboarding and preserve institutional knowledge across team transitions.

Global conventions standardize build processes and deployment setups across your project, reducing deployment failures caused by inconsistent configurations. Aligned deployment practices enable reliable, repeatable releases and simplify troubleshooting across environments.