generate-pr
Generate a complete pull request when the user asks to create/open a PR, fill the PR template, or mentions "/generate-pr". Fills every section of…
The project constitution AND the reasoning method. Apply it in ALL planning and execution of non-trivial work: reason like a proof system — hold the axioms fixed, derive each step from them, order work as a topological sort of its dependency DAG, treat every uncertain claim as a
$ npx -y skills add gabrieldabbah/genesis --skill axiomatic-induction --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/axiomatic-inductionContext preview
The summary Claude sees to decide when to auto-load this skill.
The project constitution AND the reasoning method. Apply it in ALL planning and execution of non-trivial work: reason like a proof system — hold the axioms fixed, derive each step from them, order work as a topological sort of its dependency DAG, treat every uncertain claim as a
name: axiomatic-induction description: >- The project constitution AND the reasoning method. Apply it in ALL planning and execution of non-trivial work: reason like a proof system — hold the axioms fixed, derive each step from them, order work as a topological sort of its dependency DAG, treat every uncertain claim as a conjecture with an attached experiment, and prove the postcondition (observed, not hoped) before declaring done. Universally: make illegal states unrepresentable, keep changes surgical, and verify with a real run. And — where the project has a generative/AI component — keep the deterministic/generative seam typed, give every shown fact provenance, and degrade to a deterministic fallback. If a lower document conflicts with an axiom here, the constitution wins — fix the other. A direct operator request outranks the constitution: name the conflicting axiom once, then follow the operator's decision; record a standing override as an amendment, never absorb it silently. license: MIT allowed-tools: Read
This skill is the **supreme law** of the repo and the **thinking discipline** every agent adopts before non-trivial work. Reason like a proof system, not an improviser. **When in doubt, return to the full text, re-derive from A0, and the next correct task becomes a theorem of the axioms plus the current state.** If a lower document conflicts with an axiom, **the constitution wins — fix the other.** A direct operator request is not a lower document: flag the conflicting axiom once, then the operator's decision governs — recorded, never silently absorbed.
if none licenses it, you are speculating, stop (A1). Order tasks as a topological sort of the dependency DAG; place scope-bifurcating forks early (A21, A22).
(A6); effects at the boundary, a pure/total core (A7); every shown fact carries provenance (A15); generative paths **ground → generate → verify → degrade** to a deterministic fallback (A16); make illegal states unrepresentable (A8); keep the diff surgical (A12).
happy path hoped** (A2). Any unchecked box ⟹ not done.
1. Hold the axioms fixed. 2. State the task as a proposition — a triple `{P} C {Q}` or a rule `p ⊢ r`. 3. Find the governing axiom(s); if none, stop. 4. Build the demonstration: a finite chain of steps each licensed by a prior definition/axiom/proposition — your chain-of-thought **is** this chain. 5. Mark every probabilistic step a **conjecture** and attach its falsifier. 6. Order steps by dependency; execute in topological order. 7. Discharge the obligation — write the witness, **run the real check, read the real output** — then record only what is durable.
validated type (A6/P3).
runtime check duplicates a type-guaranteed postcondition (A8/P7).
deterministic fallback that was actually exercised (A16/P3/P4).
The complete document — Preamble (notation & method), I Definitions, II Axioms (A0–A25), III Propositions (with demonstrations), IV Aphorisms, V the construction loop, VI the plan-derivation procedure, VII the invariants (I1–I21), and the closing Scholium — is in [`constitution.md`](./constitution.md). Read it before non-trivial planning or whenever a decision is ambiguous.
> **Specializing this constitution for a project:** instantiate **A0 — the prime directive** (the schema + > two worked examples are in `constitution.md` §II). The remaining axioms are universal — leave them intact.
Ultimate Opus 5 builder. Genesis creates and transforms any setup into the ultimate setup for generation 5 models. Genesis turns an empty folder into a working SaaS, web app, API, or CLI, running autonomously on your machine in Claude Code.
Repo: gabrieldabbah/genesis
Generate a complete pull request when the user asks to create/open a PR, fill the PR template, or mentions "/generate-pr". Fills every section of…
Build a new project from an empty folder, or bring an existing repository up to standard. Use when the user says \"/genesis\", \"start a new project\",…
Stage, write a Conventional Commits message from the actual diff, commit, and push. Use when the user asks to commit, save work to git, or mentions…
Rules for working in a repository where other Claude sessions are editing at the same time — no git writes, no process kills, strict scope, and verification…
Set a repository up so it cannot merge broken code and cannot quietly rot: continuous integration, automated dependency updates, a protected default branch,…
Audit a surface for security problems, score them honestly, and turn each into a task with a fix. Use before declaring work done, after wiring an integration,…