dev-playbook
v0.4.0Your team's coding standards, in context. Connects to a dev-playbook server (run it locally with Docker) over MCP to serve guardrails, definition of done, per-language rules and task workflows - and scaffolds them for a repo that has none. Run /dev-playbook-init to set it up.
By Arockiaraj RayappanLicense: Apache-2.02 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 17, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install dev-playbook for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dev-playbook@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/arockiaraj1994/dev-playbookClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/dev-playbook/.
Plugin files
├── .claude-plugin/plugin.json├── skills/scaffold-standards/SKILL.md└── skills/using-standards/SKILL.md
Included Skills2
Create a dev-playbook standards project for a repo that has none - detect its languages, pick the template packs, fill the placeholders from the actual source, preview, and write. Use when a playbook read tool reports an unknown project, or when the user asks to set up, bootstrap or scaffold coding standards.
Read the team's coding standards before writing or changing code. Use when starting any coding task in a repo that has a dev-playbook standards project - to get its guardrails, definition of done, per-language rules and the workflow for the task at hand. Also covers how to name the project correctly on every dev-playbook tool call.
Plugin manifests1
{
"name": "dev-playbook",
"version": "0.4.0",
"description": "Your team's coding standards, in context. Connects to a dev-playbook server (run it locally with Docker) over MCP to serve guardrails, definition of done, per-language rules and task workflows - and scaffolds them for a repo that has none. Run /dev-playbook-init to set it up.",
"author": {
"name": "Arockiaraj Rayappan",
"email": "[email protected]"
},
"homepage": "https://github.com/arockiaraj1994/dev-playbook",
"repository": "https://github.com/arockiaraj1994/dev-playbook",
"license": "Apache-2.0",
"keywords": [
"standards",
"guardrails",
"code-review",
"scaffolding",
"mcp"
],
"userConfig": {
"server_url": {
"type": "string",
"title": "Server URL (SSE)",
"description": "The dev-playbook server's MCP SSE endpoint. Defaults to a locally-run Docker server (docker compose up -d serves port 8420). Point it at a shared team server instead if you have one; a bare host has /sse appended.",
"default": "http://localhost:8420/sse"
},
"token": {
"type": "string",
"title": "Bearer token",
"description": "Bearer token, from POST /auth/login. Only needed when the server has auth enabled (a shared/team server). Leave empty for a local Docker server with auth off.",
"sensitive": true,
"default": ""
},
"server_path": {
"type": "directory",
"title": "Server directory (contributors)",
"description": "Only for running the server from a source checkout instead of Docker: the repo's mcp/ directory, used by scripts/playbook-mcp.sh. Not needed for the default SSE connection.",
"default": ""
},
"enforce_standards": {
"type": "boolean",
"title": "Enforce standards",
"description": "Block Write/Edit in a repo that has no dev-playbook project, instead of only warning. /dev-playbook-init turns this on for you (via a marker) - this option forces it on regardless.",
"default": true
}
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[dev-playbook on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dev-playbook)