Main
Treat OrchestKit as an “ops layer” for your coding agent:
- Start with
/ork:setupso the plugin can recommend MCP servers and align on project conventions. - Use
/ork:expector/ork:verifyafter changes to force evidence-driven validation (diff-aware checks). - Enable hooks to block common footguns: skipping tests, unsafe branches, or missing conventions.
README excerpt (verbatim)
Explore the Docs → ·
OrchestKit Users Group →
Skill browser, demo gallery, setup wizard
Why OrchestKit?
Every Claude Code session starts from zero. You explain your stack, patterns, preferences—again and again.
OrchestKit gives Claude persistent knowledge of production patterns that work automatically:
| Without | With OrchestKit |
|---|---|
| "Use FastAPI with async SQLAlchemy 2.0..." | "Create an API endpoint" → Done right |
| "Remember cursor pagination, not offset..." | Agents know your patterns |
| "Don't commit to main branch..." | Hooks block bad commits |
| "Run tests before committing..." | /ork:commit runs tests for you |
What You Get
One unified plugin, everything included.
| Component | Details |
|---|---|
| 109 Skills | RAG patterns, FastAPI, React 19, testing, security, database design, ML integration — loaded on-demand, zero overhead |
| 37 Agents | Specialized personas (backend-architect, frontend-dev, security-auditor) — route tasks to the right expert |
| 195 Hooks | Pre-commit checks, git protection, quality gates, browser safety — ship with confidence |
FAQ
Q: Do I need to install everything?
A: README presents a single /plugin install ork flow; skills load on-demand and hooks can be enabled as needed.
Q: Does it configure MCP servers? A: README says the setup wizard recommends MCP servers based on your stack.
Q: How do I troubleshoot?
A: Use /ork:doctor (README) to run a health check and diagnose common issues.