Skip to content

Genesis

Markdown that steers an LLM is code. Design it before you write it.

Genesis ports the software architect’s role to agentic systems — decomposition, contracts, and cross-cutting concerns applied to workflows where LLMs are the runtime.

Software engineering needed architecture, not just style guides, the moment systems crossed a complexity threshold. AI-coding-agent systems crossed that threshold a while ago. The downstream cost is paid by the developers using the agents you ship: poor user experience, unreliable behavior, regressions that look like the model failing when in fact the system around the model has no architecture. Genesis is the architectural layer that was missing.

If you’ve built anything non-trivial with AI coding agents, one of these has happened to you:

  • Monolithic instruction files. The forty-line rule file became four hundred. No modules, no boundaries, no separation of concerns.
  • Copy-paste duplication across primitives. The same convention lives in three skills and two rule files. The agent contradicts itself depending on which path the harness loads first.
  • Behavioral drift on long sessions. Constraints that held at turn one are silently dropped by turn twenty.

Genesis names the primitives, the patterns, and the refactor moves — so you compose instead of copy, and review instead of guess.

Install

Add Genesis to any compatible agent in one command. Install →

Quick start

Five-minute walkthrough of the architect’s loop on a real prompt. Quick start →

Primitives

The six substrate concepts every agent harness implements. Reference →

Harnesses

Per-harness file paths, gotchas, and how /genesis resolves. Harness setup →