Codified practices for AI agents — teach your agents the way.
See the Manifesto for why this exists.
| Concept | Kata term | Description |
|---|---|---|
| Skills | kata | Codified practices agents follow |
| Rules | dojo kun | Always-on constraints applied to every session |
| Roles | sensei profiles | Agent role definitions with scoped permissions |
| Prompts | kata forms | Standardized templates for commits, PRs, reviews |
| ADRs | dojo records | Architecture decisions preserved for the school |
| MCP server | the dojo | Where kata are served and practiced |
| Framework | the ryu (school) | The complete system of practices |
Kata in this repo are platform-agnostic. They follow the Agent Skills specification and work with any agent that supports it — Kiro, Claude Code, OpenCode, or others. Skills avoid coupling to specific tooling, MCP servers, or platform-specific features so they remain portable across environments.
Each kata lives in its own folder under skills/. To use a kata:
- Copy the skill folder into your project's
.agents/skills/directory - Your agent will discover it automatically on the next session
cp -r skills/create-adr /path/to/your-project/.agents/skills/Or use the dojo (MCP server) to install kata into your project — see cmd/openkata-mcp/README.md for setup.
| Kata | Description |
|---|---|
| create-adr | Detects architectural decisions in conversation and guides creation of Architecture Decision Records |
| commit-conventions | Enforces Conventional Commits format and branch naming conventions |
| create-skill | Creates agent skills by investigating repo conventions, designing workflows, and writing SKILL.md files |
| create-rule | Creates always-on agent rules by investigating repo conventions and writing RULE.md files |
| create-profile | Creates sensei profiles that define agent roles with scoped permissions and constraints |
| grill-me | Challenges a plan, spec, or ADR by interviewing the user until all corners are covered |
| makefile-conventions | Structures Makefiles as a universal command interface using modular includes and self-documenting help |
| spec-workflow | Drives feature development through a phased workflow: specify, design, tasks, implement, and validate |
| Rule | Description |
|---|---|
| markdown-style | Consistent markdown formatting conventions applied to all generated files |
| bash-style | Bash scripting conventions based on the Google Shell Style Guide |
| design-system | Token-based CSS design system conventions |
| git-naming | Branch naming, commit message format, and trailer conventions |
| Profile | Description |
|---|---|
| frontend-developer | Frontend developer scoped to web UI — templates, styles, and handlers only |
| spec-planner | Plans features through specs, designs, and task breakdowns |
See CONTRIBUTING.md for how to add skills and rules. See AGENTS.md for build commands, code style, and commit conventions. See RELEASING.md for how to publish skills and deploy.
MIT — see LICENSE.