agentleFS
Sign inStart free
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/project-constitution/SKILL.md

project-constitution

Skill1 starsChanged 5 months agoMITView on GitHub

Define a short, durable set of governing principles that constrain every later phase of work (spec, plan, tasks, implementation) so decisions stay consistent across sessions and agents. Use when bootstrapping a project, when recurring disagreements reveal missing shared principles, or when an agent keeps re-litigating the same trade-offs (quality vs speed, simplicity vs flexibility). Re-read before any non-trivial spec or architecture decision. Project goals, non-negotiable constraints (quality, simplicity, verification, privacy, attribution, maintainability), team norms, and any prior CONSTITUTION.md. A CONSTITUTION.md…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when bootstrapping a project, when recurring disagreements reveal missing shared principles, or when an agent keeps re-litigating the …

    line 22
  2. Very specific:

    Read the existing CONSTITUTION.md if present.

    line 33
  3. Distinctive:

    Keep it under ~2 pages; cut anything that cannot be checked.

    line 38
  4. Distinctive:

    Not applied: upstream constitution file format, command names, or any generated CLI scaffolding.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Constitution

Purpose

Define a short, durable set of governing principles that constrain every later phase of work (spec, plan, tasks, implementation) so decisions stay consistent across sessions and agents.

When to use

Use when bootstrapping a project, when recurring disagreements reveal missing shared principles, or when an agent keeps re-litigating the same trade-offs (quality vs speed, simplicity vs flexibility). Re-read before any non-trivial spec or architecture decision.

Inputs

Project goals, non-negotiable constraints (quality, simplicity, verification, privacy, attribution, maintainability), team norms, and any prior CONSTITUTION.md.

Workflow

  1. Read the existing CONSTITUTION.md if present; otherwise start from templates/constitution-template.md.
  2. State 4–9 principles as short, testable rules, each with a one-line rationale.
  3. For each principle, note how it is enforced (review, validation, gate).
  4. Record explicit non-goals so the constitution does not expand into process bloat.
  5. Cross-link to the spec, plan, and checkpoint skills that enforce the principles.
  6. Keep it under ~2 pages; cut anything that cannot be checked.

Outputs

A CONSTITUTION.md (or section) with numbered principles, rationale, enforcement notes, and non-goals.

Failure modes

  • Principles are aspirational slogans that cannot be verified.
  • The constitution grows into a heavyweight process document.
  • Principles conflict with each other and offer no tie-breaker.
  • It is written once and never consulted.

Verification checklist

  • Each principle is short and testable.
  • Each principle names how it is enforced.
  • Non-goals are explicit.
  • Conflicts have a stated priority order.
  • Spec/plan/checkpoint skills reference the constitution.

Applied / Not Applied

  • Applied: the idea (from github/spec-kit) of an explicit, durable principles artifact that governs later phases.
  • Not applied: upstream constitution file format, command names, or any generated CLI scaffolding. The local constitution is original and CLI-free.

Ghi chú tiếng Việt

Hiến chương dự án là bộ nguyên tắc ngắn, kiểm chứng được, chi phối mọi pha sau (spec, plan, tasks, implement). Học ý tưởng từ spec-kit nhưng viết lại bằng ngôn ngữ local, không copy định dạng hay CLI upstream. Mỗi nguyên tắc phải nêu cách thực thi và có non-goals rõ ràng. Liên kết: skills/core/spec-first-development/SKILL.md, skills/core/checkpoint-validation/SKILL.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free