devkit-knowledge
Cadre DevKit Knowledge Base
This skill helps you find information in the devkit. Read the actual files - they are the source of truth.
Where to Find Things
| Topic | Location |
|---|---|
| Global config | ~/.claude/CLAUDE.md |
| Commands | ~/.claude/commands/*.md |
| Skills | ~/.claude/skills/*/SKILL.md |
| Hooks | ~/.claude/hooks/ + settings.json |
| References | ~/.claude/references/*.md |
| Agents | Defined in system, use Task tool |
Quick Answers
How do I add a command?
Create ~/.claude/commands/my-command.md:
---
description: What this command does
argument-hint: [optional args]
---
# My Command
Instructions for Claude...
How do I add a skill?
Create ~/.claude/skills/my-skill/SKILL.md:
---
name: my-skill-name
description: What it does and when to use it.
---
# My Skill
Instructions and examples...
Skills vs Agents?
- Skills = Knowledge (methodology, templates, best practices)
- Agents = Workers (spawned via Task tool to do tasks independently)
Skills inform how to do something. Agents actually do things.
Debug hooks not running?
- Enable debug mode:
CLAUDE_HOOK_DEBUG=1 - Check
settings.jsonhas hook registered - Verify file is executable (
chmod +x)
Skill not activating?
- Check YAML frontmatter is valid (name + description)
- Ensure description has trigger keywords
- Try explicit reference: "Use the X skill"
Command workflow?
New Project:
/greenfield → SPEC.md + DESIGN.md + PLAN.md → /plan [feature] → implement → /review → /validate → /ship
Existing Project:
/plan [feature] → implement → /slop (optional) → /review → /validate → /ship
Research:
/research [topic] → findings → /progress (save as docs)
Project vs Global
| Location | Scope |
|---|---|
~/.claude/ |
All projects (personal) |
./.claude/ |
This project only (team) |
Project-level config takes precedence over global.
For Everything Else
Read the actual files. This skill points you where to look - don't rely on this skill having the latest info.
Version
- v2.0.0 (2025-12-05): Refactored to reference actual files instead of duplicating content
- v1.0.0 (2025-11-15): Initial version
More from benshapyro/cadre-devkit-claude
frontend-design
Create distinctive, memorable user interfaces that avoid generic AI aesthetics. Use when designing UI/UX, planning visual direction, or building pages and layouts.
10error-handler
Provides battle-tested error handling patterns for TypeScript and Python. Use when implementing error handling, creating try/catch blocks, or handling exceptions.
5react-patterns
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.
4tailwind-conventions
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.
4product-discovery
Methodology for discovering and specifying new software products. Use when starting greenfield projects, exploring new ideas, or defining MVP scope.
4test-generator
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.
3