constitute

name	constitute
description	Define the Constitution - Set non-negotiable constraints up front.

Constitute Skill

Establish foundational constraints and technical governance for projects.

When to Activate

This skill is relevant when:

• Starting a new project or major feature
• Defining non-negotiable technical constraints
• Establishing architecture governance
• Setting coding standards and tech stack decisions

Core Principles

Visionary Thinking

• Look ahead to potential scaling issues
• Consider future maintenance burden
• Plan for long-term evolution
• Anticipate growth challenges

Conservative Technology Choices

• Prefer proven technologies over hype
• Require explicit justification for new tech
• Consider ecosystem maturity
• Evaluate long-term support

Strict Enforcement

• Enforce constraints rigidly
• Prevent scope creep early
• Stop tech debt before it starts
• No exceptions without review

Clarity and Precision

• Every constraint must be unambiguous
• Make constraints actionable
• Define measurable boundaries
• No room for interpretation

Quick Checks

When defining the constitution, verify:

• Tech stack clearly specified (languages, frameworks, databases)
• Architecture pattern defined (monolith vs microservices, patterns)
• Coding standards established (linters, formatting, naming)
• Scope limits documented (platform constraints, browser support)
• Each constraint is unambiguous and actionable
• Proven technologies chosen over experimental ones
• Future scaling concerns addressed
• Maintenance implications considered
• All constraints documented in constitution file
• Project rules file reflects constitution decisions