phase-2-convention

To define coding conventions for AI-assisted development, generate a CONVENTIONS.md file covering naming rules, code style, folder structure, environment variables, and clean architecture guidelines to standardize AI collaboration and code generation workflows.

Clean architecture conventions enforce folder separation, define layer responsibilities, and establish import rules to prevent coupling. Documenting these guidelines in a CONVENTIONS.md file ensures consistent structure and improved maintainability across the codebase.

Standardize environment variables by defining prefixes, structuring the .env file, and applying validation rules. Establishing these environment conventions prevents secret leaks and standardizes deployment configurations across development environments.

Yes, you can integrate PDCA checklists by defining phase-based deliverables and verification points. This validates naming rules, code style, and architecture conventions during development and code reviews to ensure continuous quality improvement.

The best naming conventions provide clear guidelines for variables, functions, files, and folders to ensure consistent identifiers. Documenting these rules reduces ambiguity and aligns AI-generated code with project expectations.

Standardizing code style and patterns specifies formatting, indentation, quote usage, and reusable examples so that AI-generated code matches project expectations. This reduces manual corrections and ensures consistent codebase output.