Enforces best practice development standards including DRY/SOLID principles, comprehensive testing, type checking, linting, validation, and structured workflows across all projects.
You are working in the commands directory. Commands are the framework's public API: the `/` entries a user types to invoke a workflow.
Diagnose a failure to its root cause via a reproduce-then-hypothesise loop. Produces a root-cause report; does not change code.
Execute a complete bug fix workflow with investigation, implementation, and validation.
Write a fresh session-state file and update the MEMORY.md index, then signal readiness for /clear.
View Claude Code session logs and activity history.
You are working in the agents directory. Agents are subprocess LLM invocations with their own tool allowlist, context, and contract. They return typed `AgentVerdict` structures. They are the judgment layer of the framework.
Reason-tier analyst that consumes two api-contract.json snapshots — `before` and `after` — and emits the detected differences classified by breaking-ness (breaking / potentially-breaking / non-breaking) and severity. Output is a structured plan, not a verdict; Phase 6+ API stack reviewers consume it. Phase 3 ships the contract only — full review-side support is deferred. Validates against schemas/reports/api-breaking-changes.schema.json.
Read-tier scanner that walks the project's source tree and extracts API contracts from declared sources — OpenAPI / Swagger spec files, tRPC router definitions, GraphQL schemas. Output is a JSON report validated against schemas/reports/api-contract.schema.json. Phase 3 ships first-class OpenAPI parsing; tRPC and GraphQL get presence detection with detailed parsing deferred to Phase 6+ stack agents. Source-only — never invokes a live API.
Fires at the 60K soft-warn guideline. Compresses older conversation turns into a structured summary block placed immediately before the current turn — near the attention hotspot, away from the LITM zone. Never runs synchronously on the critical path.
Background agent that aggregates per-agent quality metrics from the framework telemetry log into quality-scores.json. Reads framework-memory/telemetry/<date>.jsonl, computes precision, p95 latency, p95 cost, and run-count per agent, and writes the canonical scores file Phase 5+ agents read to learn from prior runs.
Enforces best practice development workflow for any code task. Triggers on: feature implementation, bug fixes, refactoring, code changes, debugging, testing, and any development work. Ensures DRY/SOLID principles, comprehensive testing, validation, proper git commits, and structured planning with TLDR summaries.
Execute the standards orchestrator with phase sequencing, checkpoints, and handoffs. Run development standards across domains (logging, error, type, lint, test, validation, git, housekeeping, naming) with enforced workflow phases: Design -> Validate Design -> Build -> Test -> Validate.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Enforce consistent development standards across all your projects with automated hooks, specialized agents, workflow commands, and best-practice skills.
# Add this repo as a marketplace (one-time)
/plugin marketplace add myenquiringmind/dev-standards-plugin
# Install in any project
/plugin install dev-standards@myenquiringmind
# That's it! Standards now enforced automatically.
| Hook | What It Does |
|---|---|
| SessionStart | Loads git status + TODO context, logs session, checks for updates |
| UserPromptSubmit | Logs prompts for session history |
| PreToolUse | Blocks dangerous commands, protects main branch |
| PostToolUse | Auto-formats, type checks, lints, logs activity, venv-aware |
| Stop | Validation checkpoint (tests, types, lint) |
| SubagentStop | Ensures subagents provide summaries |
.venv on first Python file editpython -m venv (fallback)| Agent | Purpose | When to Use |
|---|---|---|
@investigator | Deep root cause analysis | Complex bugs, unknown failures |
@code-reviewer | Quality & security review | Before commits, PR reviews |
@doc-writer | Documentation updates | API changes, new features |
| Agent | Domain | Expertise |
|---|---|---|
@standards-orchestrator | Workflow | Coordinates domain agents through phases |
@logging-standards | Logging | Structured logging, log levels, debug mode |
@error-standards | Errors | Exception handling, error types, recovery |
@type-standards | Types | JSDoc types, TypeScript, mypy |
@lint-standards | Linting | ESLint, ruff, code style, auto-fix |
@test-standards | Testing | Unit/integration tests, coverage, mocking |
@validation-standards | Validation | Input validation, sanitization, security |
@git-standards | Git | Conventional commits, branch naming, .gitignore |
@housekeeping-standards | Hygiene | Project layout, temp dirs, cleanup |
@naming-standards | Naming | File/function/class naming conventions |
Note:
@test-writerwas merged into@test-standardsin v1.3.0
| Command | Purpose |
|---|---|
/plan | Create structured implementation plan with TLDR |
/fix | Complete bug fix workflow |
/validate | Comprehensive validation checklist |
/review | Code review with quality gates |
/setup | Initialize project configuration |
/typecheck | On-demand type checking + linting |
/logs | View session activity and history |
| Skill | Triggers On |
|---|---|
dev-workflow | Any code task - features, fixes, refactoring |
orchestrate | Standards enforcement via /orchestrate domain=<domain> |
The orchestrator provides systematic standards enforcement with checkpoints and handoffs.
/orchestrate domain=git # Single domain
/orchestrate domain=all # All domains (dependency-sorted)
/orchestrate domain=logging phase=design # Start from specific phase
Design → Validate Design → Build → Test → Validate
| Phase | Purpose |
|---|---|
| Design | Analyze current state, propose improvements |
| Validate Design | Review proposal for completeness and conflicts |
| Build | Implement the approved design |
| Test | Write and run tests for implementation |
| Validate | Final verification that everything works |
After design and build phases, execution pauses for user approval:
approve, yes, proceed, or lgtm to continuereject or rollback to stop executionWhen the orchestrator runs:
feat/orchestrator-<domain>-<timestamp>/orchestrate domain=git gitMode=auto # Default - automatic commits
/orchestrate domain=git gitMode=manual # Manual commit control
/orchestrate domain=git gitMode=disabled # No git operations
Step 1: Host this repo on GitHub (public or private)
# Fork or clone this repo
git clone https://github.com/myenquiringmind/dev-standards-plugin
cd dev-standards-plugin
npx claudepluginhub myenquiringmind/dev-standards-plugin --plugin dev-standardsSkills for development standards: commit messages, code review, testing, documentation, and more. Supports 25 comprehensive skills for the full development lifecycle.
This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurrent agents) and sub-agents (lint touched files before task completion). Prevents claiming "production ready" code without verification. Includes linting rules knowledge base for ruff, mypy, and bandit, plus the linting-root-cause-resolver agent for systematic issue resolution.
AI-First SDLC — zero-debt development with validators, enforcement, and workflows
AI-powered development workflow automation - Phase-based planning, implementation orchestration, preflight code quality checks with security scanning, ship-it workflow, and development principles generator for CLAUDE.md
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use