constitution

To define coding principles and project governance rules, you can generate a project constitution that analyzes your project structure and documentation to tailor team standards and patterns. This establishes clear rules and expectations for development workflows.

A project constitution is a document defining your team's coding principles, governance rules, and standards. You need one when starting a new project or updating existing team standards to ensure alignment and clear expectations across developers.

You generate a companion prompt by creating a project constitution that defines coding principles and team standards, which then produces a prompt file to guide automated development workflows based on your project specifics.

Yes, you can upgrade existing governance templates by updating your project constitution. The process analyzes your current project structure and documentation to ensure alignment with existing governance templates and coding principles.

The best way to establish coding patterns and governance is to run an automated workflow that analyzes your project structure to generate a personalized constitution and companion prompt, defining clear development rules and expectations.

You need existing project structure and documentation for the constitution generation process to analyze. The skill uses these project specifics to tailor coding principles, governance rules, and team standards accurately to your environment.