When should I use the Phase 2 Convention skill?

This skill should be used proactively at the start of a new project or when you need to establish clear coding standards to ensure consistency between human developers and AI agents.

What kind of architecture does this skill promote?

It promotes Clean Architecture principles, specifically a 4-layer structure consisting of Presentation, Application, Domain, and Infrastructure layers to ensure code is resilient to change.

Can I use this on an existing project?

It is generally not recommended for projects with established conventions, as it is designed to define new rules from scratch. Using it on existing projects may cause conflicts with existing styles.

How does it help with security?

The skill establishes environment variable conventions, including prefixing rules (e.g., NEXT_PUBLIC_) and templates for .env.example to ensure sensitive keys are never committed to version control.

Phase 2: Coding Convention

Name: Phase 2: Coding Convention
Author: applewave

byapplewave

0•

Developer Tools

Establishes standardized coding rules, naming conventions, and architectural principles for consistent AI-human collaboration.

The Phase 2 Convention skill is designed to lay a solid foundation for new software projects by defining clear coding standards and architectural guidelines. It automates the creation of comprehensive documentation for naming conventions (PascalCase, camelCase, kebab-case), folder structures, and Clean Architecture layers. By standardizing environment variable management and security principles early in the development process, this skill ensures that both AI agents and developers maintain a high-quality, maintainable codebase that scales from small starter projects to complex enterprise systems.

Key Features

01Comprehensive environment variable security and naming templates

02Automated generation of CONVENTIONS.md and architectural documentation

03Scalable rule sets for Starter, Dynamic, and Enterprise project levels

040 GitHub stars

05Standardized naming rules for components, functions, and file structures

06Clean Architecture implementation with defined layer responsibilities

Use Cases

01Setting up environment variable schemas and security checklists

02Initializing a new project with robust coding and naming standards

03Defining architectural boundaries and dependency rules for a clean codebase

Key Features

01Comprehensive environment variable security and naming templates

02Automated generation of CONVENTIONS.md and architectural documentation

03Scalable rule sets for Starter, Dynamic, and Enterprise project levels

040 GitHub stars

05Standardized naming rules for components, functions, and file structures

06Clean Architecture implementation with defined layer responsibilities

Use Cases

01Setting up environment variable schemas and security checklists

02Initializing a new project with robust coding and naming standards

03Defining architectural boundaries and dependency rules for a clean codebase