The Layered System
Your Claude Code knowledge lives in layers:| Layer | Purpose | Example |
|---|---|---|
| CLAUDE.md | Project-specific context | ”We use Prisma, run npm test for tests” |
| Skills | Domain patterns | How to write Zod schemas, Tailwind conventions |
| References | Deep docs | Full API guides, architecture specs |
Building Your Stack
Search for skills that match your tech stack, then install the ones that fit.- React / Next.js
- Node.js API
- Fullstack
Discovering Skills
Composing Skills That Work Together
Skills are independent by design — each triggers on its own conditions. But some combinations are particularly effective:- Testing skill + framework skill — Test patterns that match your framework conventions
- Validation skill (Zod) + API skill — Input validation patterns that align with your API layer
When to Create Your Own
Install existing skills when:- A community skill covers your need
- The patterns are standard (React, Tailwind, etc.)
- Your team has specific conventions not covered elsewhere
- You have internal libraries or frameworks
- You want to encode institutional knowledge (how your team does auth, deploys, etc.)