Hooks
Rules enforced at every tool boundary. The agent can't self-approve, can't skip a phase, can't ignore the guardrails it was given.
Baseline is the open-source workflow Friedbot Studio uses to build software with Claude Code. Hooks enforce the rules. Memory keeps context. Skills run the playbooks. Discipline becomes structural, not advisory.
Out of the box, the agent improvises. It writes code without reading the surrounding system. It skips the steps you wanted enforced. It approves its own work. For one-off scripts that's fine. For production engineering it isn't. Baseline closes the gap with rules the agent can't argue with.
Baseline is a repository overlay. It installs hooks, skills, memory, and a constitutional contract that ride alongside every Claude Code session.
Rules enforced at every tool boundary. The agent can't self-approve, can't skip a phase, can't ignore the guardrails it was given.
Repeatable recipes for the work the agent has to do. Write the recipe once, run it through every project that needs it.
Persistent context that travels with the session. The agent remembers the constitution, the in-progress plan, and the team's decisions.
A staged pipeline from intake to commit, with user-controlled gates that pause the agent when a decision matters.
Run npx @friedbotstudio/create-baseline@latest in the repo you want to discipline. Baseline drops in its overlay.
Run /init-project inside Claude Code. Baseline writes its constitution into the project.
Move through the eleven-phase workflow. Hooks enforce the rules. Gates pause for you when a decision matters.
FBS uses Baseline across every project: the website you're reading, the client work, even the next release of Baseline itself. The project bootstraps its own discipline. We open-sourced it because the tools we use to build with should be available to engineers who want to work the same way.
Install in a minute. Ship through it for years.