Menü
Knowledge base for the Cadre DevKit. Use when answering questions about the devkit structure, commands, skills, hooks, agents, or workflows.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
| name | devkit-knowledge |
| description | Knowledge base for the Cadre DevKit. Use when answering questions about the devkit structure, commands, skills, hooks, agents, or workflows. |
This skill helps you find information in the devkit. Read the actual files - they are the source of truth.
| 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 |
Create ~/.claude/commands/my-command.md:
---
description: What this command does
argument-hint: [optional args]
---
# My Command
Instructions for Claude...
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 inform how to do something. Agents actually do things.
CLAUDE_HOOK_DEBUG=1settings.json has hook registeredchmod +x)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)
| Location | Scope |
|---|---|
~/.claude/ | All projects (personal) |
./.claude/ | This project only (team) |
Project-level config takes precedence over global.
Read the actual files. This skill points you where to look - don't rely on this skill having the latest info.
Basierend auf der SOC-Berufsklassifikation
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.
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.
