cadre-devkit-claude

You are in **Backlog Mode** - documenting bugs and improvements WITHOUT implementing them.

Discover and specify a new software project from scratch

Learn about Claude Code, the devkit, commands, skills, and workflows

Plan a new feature or task with proper structure before implementation.

Save research findings as reusable knowledge documents

Deep research on a topic with parallel sub-agents

Review code changes for quality and best practices

Commit and ship validated changes

Remove AI-generated code slop from current branch

Validate implementation before shipping

Reviews code for adherence to coding standards, best practices, and style guidelines. PROACTIVELY use after completing any significant code changes (new features, refactors, bug fixes). Auto-invoke when code is ready for review before committing.

Systematically analyzes errors, stack traces, and logs to identify root causes. PROACTIVELY use when user reports bugs, errors, crashes, or unexpected behavior. Auto-invoke when stack traces or error messages appear in conversation.

Researches official documentation, latest best practices, and current tech stack information. PROACTIVELY use when evaluating libraries, checking API usage, or when implementation involves unfamiliar frameworks. Auto-invoke before using any library/API features from training data.

Assists with Git operations following branching strategy and commit conventions. PROACTIVELY use when creating branches, making commits, resolving conflicts, or managing git workflows. Auto-invoke for any git-related questions or operations.

Analyzes and optimizes code performance. PROACTIVELY use when user mentions slow, laggy, timeout, memory issues, or optimization needs. Auto-invoke when performance-critical code is being written (loops, data processing, API calls).

Safely refactors code while maintaining behavior. PROACTIVELY use when user asks to restructure, extract, rename, or clean up code. Auto-invoke when code smells are detected (duplication, long functions, poor organization).

Clarifies vague requirements by asking probing questions, identifying edge cases, and creating comprehensive specifications. PROACTIVELY use when requirements are vague, ambiguous, or incomplete. Auto-invoke before implementing features that lack clear acceptance criteria.

Provides REST and GraphQL API design patterns for Node.js, Flask, and FastAPI. Use when designing endpoints, request/response structures, API architecture, pagination, authentication, rate limiting, or when working in /api/ or /routes/ directories.

Formats code according to Ben's style guidelines for TypeScript, Python, and general best practices. Use when formatting code, fixing linting issues, checking naming conventions, organizing imports, or when user mentions formatting, style, linting, Prettier, Black, or ESLint.

Knowledge base for the Cadre DevKit. Use when answering questions about the devkit structure, commands, skills, hooks, agents, or workflows.

Generates README files, API documentation, and inline code comments following best practices. Use when creating project documentation, writing READMEs, documenting APIs, or explaining complex code.

Provides battle-tested error handling patterns for TypeScript and Python. Use when implementing error handling, creating try/catch blocks, or handling exceptions.

Create distinctive, memorable user interfaces that avoid generic AI aesthetics. Use when designing UI/UX, planning visual direction, or building pages and layouts.

Methodology for discovering and specifying new software products. Use when starting greenfield projects, exploring new ideas, or defining MVP scope.

Modern React patterns for TypeScript applications including hooks, state management, and component composition. Use when building React components, managing state, or implementing React best practices.

Consistent Tailwind CSS patterns for React/Next.js applications. Use when styling components with Tailwind, adding responsive design, implementing dark mode, or organizing utility classes.

Generates Jest or Pytest tests following Ben's testing standards. Use when creating tests, adding test coverage, writing unit tests, mocking dependencies, or when user mentions testing, test cases, Jest, Pytest, fixtures, assertions, or coverage.

5 hooks across 3 events