developer-kit
Developer Kit for Claude Code: a modular marketplace of plugins (core + language/infra/tooling plugins) that provide reusable skills, agents, and slash commands to drive a repeatable development workflow (brainstorm/spec-to-tasks/task management/feature development/code review & debugging).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README indicates a Python pre-tooluse hook `prevent-destructive-commands` to block dangerous Bash commands, which is a positive safety measure. However, no details are provided about how secrets are handled, how credentials are stored, or how permissions/scope boundaries are enforced for plugin actions. The manifest snippet only shows `PyYAML` as a dependency for a different package (`claude-validator`), not for the full developer-kit; dependency hygiene for the full project is therefore unclear from the provided data.
⚡ Reliability
Best When
You want consistent, spec-driven engineering workflows inside Claude Code across multiple languages/frameworks using a plugin marketplace model.
Avoid When
You need a standalone HTTP API/SDK with formal OpenAPI contracts, or you cannot accept that plugin actions (e.g., repo edits, command execution) depend on agent/tool behavior not fully specified here.
Use Cases
- • Generating functional specifications and acceptance criteria for new features
- • Decomposing specifications into executable tasks with complexity scoring
- • Implementing features or executing specific task steps in supported languages/frameworks
- • Reviewing/refactoring/debugging code against specs and conventions
- • Standardizing development workflows across teams using Claude Code
Not For
- • Directly exposing a secure public API for external systems (it is primarily a Claude Code plugin/command system)
- • Highly regulated environments without verifying plugin behavior and data handling
- • Use cases requiring strong, explicit authentication/authorization controls from this package alone
Interface
Authentication
No explicit authentication scheme for the package itself is described in the provided README content. Security model likely depends on Claude Code environment and how plugins execute tools/actions.
Pricing
Pricing is not described in the provided content.
Agent Metadata
Known Gotchas
- ⚠ Commands may perform destructive operations unless guarded; a hook for blocking dangerous Bash commands is mentioned, but the overall safety boundary is not fully specified here.
- ⚠ Task/spec files are written to repository paths (docs/specs/*); repeated runs could overwrite or create duplicates if not designed to be idempotent.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for developer-kit.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.