# Amby Constitution

> Create or amend the project constitution — durable, cross-feature principles.

- Skill: `ambystechcom/amby-constitution` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ambystechcom/amby-constitution`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ambystechcom/amby-constitution/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ambystechcom (https://skillmd.com/u/ambystechcom)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ambystechcom/amby-constitution

---

<!-- GENERATED by AmbyKit from src/prompts/constitution.md — do not edit by hand; run `ambykit sync`. -->

Establish or update the project **constitution** at `.amby/constitution.md`.

1. If the file is missing, create it from `@.amby/templates/constitution.md` and fill it in. If it
   exists, amend only the section relevant to `the user's request that followed this skill invocation` (or, with no argument, review all principles briefly).
2. Interview the user only where a principle is unclear — ask one focused question at a time.
3. Keep each principle short, imperative, and **numbered** so later phases can cite it.
4. Cover: code quality, testing standards, UX consistency, performance/reliability, security. Add
   project-specific non-negotiables as needed.
5. Bump the version and update the date. Do not restate feature requirements — those belong in specs.

Output only the edited constitution. Be concise.