phase-2-convention

Standardize coding conventions and generate CONVENTIONS.md for AI-assisted projects.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/joshua3403/giit-template --skill phase-2-convention
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase-2-convention
Source: https://github.com/joshua3403/giit-template/tree/main/.agent/skills/phase-2-convention
Command: npx skills add https://github.com/joshua3403/giit-template --skill phase-2-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes coding conventions to ensure consistent code style and collaboration across AI-assisted projects.

Core Features & Use Cases

  • Naming rules, structure guidelines, environment variable conventions, and architecture principles to guide AI-generated code and team contributions.
  • Phase-aware deliverables: conformance docs (CONVENTIONS.md), plan docs, and references to templates.

Quick Start

Start Phase 2 by drafting core naming rules and a minimal folder-structure guide. Then generate CONVENTIONS.md and docs/01-plan/naming.md.

Frequently Asked Questions about phase-2-convention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent coding conventions for AI-assisted development?▼

Enforce coding conventions by generating a CONVENTIONS.md file with naming rules, folder structure guidelines, and architecture principles to standardize AI-generated code and team contributions.

What should be included in a coding conventions document for clean architecture?▼

A coding conventions document should include naming rules, minimal folder-structure guides, environment variable conventions, and clean-architecture principles to direct AI-generated code outputs.

How do I start standardizing naming rules and folder structure for a new project?▼

Start standardizing by drafting core naming rules and a minimal folder-structure guide, then generate deliverables like CONVENTIONS.md and docs/01-plan/naming.md to establish project guidelines.

Can I use a PDCA workflow to manage environment variable conventions and project documentation?▼

Yes, you can use a PDCA-driven workflow to manage environment variable conventions and deliver phase-ready design artifacts including planning docs, references, and templates for ongoing AI-assisted development.

Does this convention standardization approach work for ongoing AI-assisted projects?▼

Yes, this standardization approach applies to both new projects and ongoing AI-assisted development, enforcing consistent code style and collaboration through phase-aware deliverables and architecture guidelines.

What are the limitations of relying on generated documentation for code style consistency?▼

Relying on generated documentation requires continuous team adherence to the defined naming rules and architecture principles, as the deliverables only provide guidelines rather than automated code-level enforcement.