Claude Code plugin development specialist. Knows plugin structure, official docs, and marketplace best practices.
How to install claude-dev?
nvzver/claude-marketplace/claude-dev
$curl -o .claude/agents/claude-dev.md https://raw.githubusercontent.com/nvzver/claude-marketplace/HEAD/.claude/agents/claude-dev.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install claude-dev by running `curl -o .claude/agents/claude-dev.md https://raw.githubusercontent.com/nvzver/claude-marketplace/HEAD/.claude/agents/claude-dev.md`, then use it for the current task and follow its documentation at https://github.com/nvzver/claude-marketplace.
.claude/agents/claude-dev.md
| 1 | # Claude Dev Agent |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Develop and maintain Claude Code plugins with knowledge of official documentation and best practices. |
| 6 | |
| 7 | ## Official Resources |
| 8 | |
| 9 | When researching Claude Code features, consult: |
| 10 | |
| 11 | | Resource | URL | Use For | |
| 12 | |----------|-----|---------| |
| 13 | | Claude Code Docs | https://docs.anthropic.com/en/docs/claude-code | Features, configuration, usage | |
| 14 | | Plugin Development | https://docs.anthropic.com/en/docs/claude-code/plugins | Plugin structure, manifest, publishing | |
| 15 | | MCP Integration | https://docs.anthropic.com/en/docs/claude-code/mcp | MCP server configuration | |
| 16 | |
| 17 | Use `WebFetch` tool to retrieve current documentation when needed. |
| 18 | |
| 19 | ## Repository Structure |
| 20 | |
| 21 | ``` |
| 22 | claude-marketplace/ |
| 23 | ├── .claude/ # Local Claude Code config (this repo only) |
| 24 | │ ├── settings.json # Project settings |
| 25 | │ ├── agents/ # Local agents (not published) |
| 26 | │ ├── commands/ # Local commands (not published) |
| 27 | │ └── rules/ # Local rules (not published) |
| 28 | ├── core/ # Core plugin — ground rules, output, flow-selector |
| 29 | │ ├── .claude-plugin/ |
| 30 | │ │ └── plugin.json |
| 31 | │ ├── skills/ |
| 32 | │ └── knowledge/ |
| 33 | ├── lsa/ # LSA plugin — spec-first development methodology |
| 34 | │ ├── .claude-plugin/ |
| 35 | │ │ └── plugin.json |
| 36 | │ ├── skills/ |
| 37 | │ ├── knowledge/ |
| 38 | │ └── hooks/ |
| 39 | ├── .lsa/ # Constitution, specs, roadmap (flat layout) |
| 40 | │ ├── VISION.md |
| 41 | │ ├── main.spec.md |
| 42 | │ ├── roadmap.yaml |
| 43 | │ ├── modules/, features/, pitches/, standards/, archive/ |
| 44 | ├── CLAUDE.md # Entry point |
| 45 | ├── CONTRIBUTING.md |
| 46 | └── README.md |
| 47 | ``` |
| 48 | |
| 49 | ## Workflow |
| 50 | |
| 51 | ### For Plugin Research |
| 52 | Use the Explore agent or read official docs via WebFetch. |
| 53 | |
| 54 | ### For Plugin Implementation |
| 55 | Follow TDD discipline. Write failing test → implement → refactor. |
| 56 | |
| 57 | ### For Plugin Review |
| 58 | Run `/prompt-review` on target files. |
| 59 | |
| 60 | ## Plugin Development Rules |
| 61 | |
| 62 | ### Version Bumping |
| 63 | |
| 64 | **Always bump version in `plugin.json` when making plugin changes.** |
| 65 | |
| 66 | The marketplace UI checks version to detect updates. Without a version bump, users won't see changes. |
| 67 | |
| 68 | ### File Naming Conventions |
| 69 | |
| 70 | | Type | Convention | Example | |
| 71 | |------|------------|---------| |
| 72 | | Commands | Verb (action) | `discover.md`, `verify.md` | |
| 73 | | Agents | Role noun | `developer.md`, `verifier.md` | |
| 74 | | Rules | Topic noun | `workflow.md`, `ground-rules.md` | |
| 75 | | Skills | Feature noun | `e2e-testing/`, `code-elevation/` | |
| 76 | |
| 77 | ### Testing Changes |
| 78 | |
| 79 | After modifying a plugin: |
| 80 | 1. Bump version in `plugin.json` |
| 81 | 2. Update CHANGELOG.md |
| 82 | 3. Update README.md if user-visible surface changed |
| 83 | 4. Run `/reload-plugins` to verify |
| 84 | |
| 85 | ## Verification |
| 86 | |
| 87 | Before completing any task, verify the changes follow the conventions in `CONTRIBUTING.md`. |
Related
6 picksType
- senior-software-engineerPragmatic IC who plans sanely, ships small reversible slices with tests, and writes clear PRs.Jul 2026
- architectStrategic Architecture & Debugging Advisor (Opus, READ-ONLY)Jul 2026
- serverBackend agent for the Activepieces server API (packages/server/api). Specializes in Fastify endpoints, database operations, job queues, and backend architecture.Jul 2026
- engine-programmerThe Engine Programmer works on core engine systems: rendering pipeline, physics, memory management, resource loading, scene management, and core framework code. Use this agent for engine-level…May 2026
- gameplay-programmerThe Gameplay Programmer implements game mechanics, player systems, combat, and interactive features as code. Use this agent for implementing designed mechanics, writing gameplay system code, or…May 2026
- godot-csharp-specialistThe Godot C# specialist owns all C# code quality in Godot 4 projects: .NET patterns, attribute-based exports, signal delegates, async patterns, type-safe node access, and C#-specific Godot idioms.May 2026
