One config — rules, hooks, and shared memory across every coding agent. Your team's playbook, enforced.
Works with Claude Code_
GYRD doesn't replace your AI tools. It's the practice layer they're missing — one config that makes every agent follow your team's playbook.
Pre-commit hooks catch what prompts miss. Lint, typecheck, security gates before every commit. Hooks = 100%. Prompts ≈ 80%.
Code review, security rules, agent orchestration — pre-configured from real research. Not opinions. Not vibes.
New research, better prompts, improved workflows. gyrd update pulls the latest. Your customizations stay untouched.
“The more autonomy you give AI agents,
the more discipline they need. GYRD is that discipline.”
When your team uses GYRD, every agent — on every machine — follows the same conventions. No more “works on my machine” for AI.
Commit CLAUDE.md and .cursor/rules/ to your repo. Every teammate's agent inherits the same rules — code style, review process, security.
Agents share PROGRESS.md and DECISIONS.md — status, blockers, architectural decisions. Your PM's agent knows what the dev's agent just shipped.
Persistent memory across machines — patterns learned, mistakes avoided. Your team's AI gets smarter with every session.
Leave your email — we'll send setup instructions and early updates.
npx create-gyrd, and it generates config files that make your AI agents produce more reliable code. It's a practice layer — not a new tool, but structure for the tools you already use.CLAUDE.md for Claude Code, .cursor/rules/ for Cursor, AGENTS.md for Copilot. Plus pre-commit hooks. All from one gyrd.toml config. Sections marked [GYRD-MANAGED] get updated by gyrd update; your customizations stay untouched.PROGRESS.md and DECISIONS.md. We're building shared persistent memory next.[GYRD-MANAGED] tags. gyrd update only touches those sections. Everything you've customized stays untouched.