Amby constitution
Spec-Driven Development framework that helps AI coding assistants build better software — author your specs, user stories, UI design, plans and tasks once, and emit native config for Claude Code, OpenCode, GitHub Copilot, Cursor, Antigravity and more.
npx -y skills add ambystechcom/AmbyKit --skill amby-constitutionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create or amend the project constitution — durable, cross-feature principles.
SKILL.md
1.0 KB, as published. Nobody here has run it
<!-- 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.
- 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.