mine.constitution

You can define project-level constraints for architecture and code style through a guided interview process that captures your requirements for technology, testing, performance, and security, generating a constitution.md file to maintain consistency.

A project constitution file is used to document core architecture and quality tenets, ensuring all new code and designs align with agreed-upon standards throughout the development lifecycle.

To validate new designs against established project constraints, you first define your architecture and quality principles in a constitution file, which then provides a basis for design validation tools to check new designs against those rules.

Yes, the guided interview supports defining security and operations constraints, walking you through principles for architecture, technology, testing, performance, code style, and operations.

Yes, you can update an existing constitution.md file without losing previous constraints, as the skill creates or updates the file in your project root to reflect new requirements while maintaining existing standards.

The best way to enforce code style and technology standards is to document them in a project constitution file, ensuring all team members and design validation processes adhere to the agreed-upon constraints.