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