forge-constitution
Skill0 starsChanged 3 months agoMITView on GitHub
Writes a project constitution — the non-negotiable technical principles that every specification, design and review must respect, and against which the agent checks itself. Produces .forge/constitution.md. Use this skill at the start of any new project, whenever the user mentions standards, conventions, project rules, quality bars, or "how I want this done", and whenever a design decision needs arbitration but no guiding principle exists yet.
In this repository6 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Ask one question per area, with concrete options.
- Distinctive: line 89
When a design collides with a principle, the design is not always the one that is wrong.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project constitution
The constitution is the one document the agent rereads at every step. It states universal constraints that nothing may bypass — not preferences.
It is written once, early, and amended rarely. It is short: past one page it stops being read, and therefore stops existing.
The admission test
A principle enters the constitution only if it passes all three filters:
- It is checkable. You can look at a design and say "compliant" or "not compliant." "Code must be clean" fails. "No external dependency for state storage in v1" passes.
- It costs something. A principle that forbids nothing steers nothing. If it has never made you drop an option, it is decorative.
- It holds across all features. A rule that only applies to one module belongs in the design, not the constitution.
Aim for 5 to 9 principles. Below that it arbitrates nothing; above it becomes a ritual.
Areas to cover
Ask one question per area, with concrete options. Don't aim for exhaustiveness: pick the areas that will actually arbitrate decisions on this project.
- Simplicity boundary — how many services, repositories, languages? The solo default: one repository, one service, one database, until proven otherwise.
- Data — where it lives, who reads it, sovereignty, encryption, backups and above all tested restores. A backup never restored is not a backup.
- Testing — what level of proof before something counts as done. The realistic solo bar is not "90% coverage" but "every critical path has a test that fails when you break it."
- Operations — reproducible deployment? logging? What happens when it falls over at night? The honest answer: it stays down until morning. Write that down.
- Security — secrets, authentication, exposed surface. A non-negotiable minimum, not a compliance programme.
- Reversibility — which dependencies can be swapped in a day, which ones are a marriage. Forbid undocumented marriages.
- Cost — monthly infrastructure ceiling. One number. It will settle architecture debates on your behalf.
- Solo reach — every decision must be understandable by one person after six months away. This principle is what justifies refusing elegant architectures.
Format
# Constitution — <project>
Version 1.0 · YYYY-MM-DD
## P1. <Principle title>
**Rule.** <One imperative, checkable sentence.>
**Why.** <The cost it avoids. One sentence.>
**How we check.** <What you look at to say compliant / not compliant.>
**Exception.** <None | or the single condition, with a mandatory ADR.>
## P2. …
## Amendments
| Date | Principle | Change | Reason |A correctly written principle
P3. One data store. Rule. All persistent data lives in PostgreSQL. No second storage system (distributed cache, search engine, message queue) without an accepted ADR. Why. Each extra store adds a backup, a restore, a partial failure mode and a consistency model for one person to carry. How we check. The design lists its infrastructure dependencies; more than one for state means non-compliant. Exception. None in v1.
Downstream use
- The specification does not cite the constitution (it is technology-free), but it must not demand behaviour no compliant design could deliver.
- The design explicitly names the principles that eliminated an option.
- The consistency review fails if a design violates a principle without an ADR owning it.
- A justified violation is not forbidden: it requires an amendment or an ADR. What is forbidden is the silent violation.
Amending
When a design collides with a principle, the design is not always the one that is wrong. Propose the amendment, explain what is gained and what is lost, and let the human decide. Record the date and reason in the amendments table. A principle that has been worked around twice is badly written — rewrite it rather than working around it a third time.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

