devkit-knowledge
Knowledge base for the Cadre DevKit. Use when answering questions about the devkit structure, commands, skills, hooks, agents, or workflows.
When & Why to Use This Skill
The Cadre DevKit Knowledge Base is a specialized Claude skill designed to streamline the development process within the Cadre ecosystem. It provides instant access to documentation regarding devkit structure, command implementation, and agent workflows, helping developers navigate complex configurations, debug hooks, and maintain project consistency through standardized methodologies.
Use Cases
- Navigating DevKit Architecture: Quickly locate global and project-specific configurations, commands, and hooks within the .claude directory structure.
- Extending Functionality: Access step-by-step instructions and markdown templates for creating new custom commands and skills to enhance agent capabilities.
- Workflow Standardization: Implement optimized development cycles for new or existing projects, including research, planning, implementation, and shipping phases.
- Troubleshooting & Debugging: Resolve issues with non-responsive hooks or inactive skills using specific environment variables and validation checklists.
- Architectural Guidance: Clarify the distinction between Skills (knowledge-based methodology) and Agents (task-oriented workers) to optimize system design.
| name | devkit-knowledge |
|---|---|
| description | Knowledge base for the Cadre DevKit. Use when answering questions about the devkit structure, commands, skills, hooks, agents, or workflows. |
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