Generates lean CLAUDE.md (~50-100 lines) with progressive disclosure. Use when setting up a new project or when CLAUDE.md is missing or bloated.
npx claudepluginhub pipemind-com/pipemind-marketplace --plugin spec-driven-developmentThis skill is limited to using the following tools:
Analyzes your codebase and generates a **lean** `CLAUDE.md` following the "less is more" principle. References `docs/` for detailed content.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Analyzes your codebase and generates a lean CLAUDE.md following the "less is more" principle. References docs/ for detailed content.
Claude reliably follows ~150 instructions. Claude Code's system prompt uses ~50, leaving ~100 for CLAUDE.md + agents combined. A bloated CLAUDE.md degrades all instruction-following.
Always use fd instead of find for filesystem discovery. fd is safe by design (no -exec, no -delete).
1. Pre-Flight Validation:
CLAUDE.md exists, update it unconditionally; report "updated" (not "created") in the summary2. Codebase Analysis:
.claude/agents/planner.md and builder.md (triggers Workflow section)3. Code Exploration:
4. Generate Lean CLAUDE.md (~50-100 lines):
docs/ files5. Validation:
--focus "area": Emphasize specific patterns (e.g., "caching", "auth")/compiling-project-docs afterward for detailed docs.# Project Context
**Mission:** One sentence — what the project does and who it serves.
Brief context (1-2 sentences).
## About This Project
[Tech stack, 2-3 sentences max]
## Key Directories
- `src/` — Source code
- `tests/` — Test files
- [5-8 items max]
## Commands
```bash
[command] # Dev server
[command] # Run tests
[command] # Build
When implementing multi-part features:
Before specific tasks, read relevant documentation:
docs/architecture.mddocs/testing.md
Read only what's relevant to your current task.Generate docs with: /compiling-project-docs
## The 80% Rule
**Only include instructions relevant to 80%+ of sessions.**
Include in CLAUDE.md: essential commands, critical conventions, key directories, gotchas, tech stack overview.
Move to `docs/`: detailed deployment steps, comprehensive code style, full architecture, database schema, edge case handling.
Do NOT include: linting rules (use actual linters), what Claude can infer, task-specific instructions (belong in agents), sensitive info (API keys, credentials).
Run `/compiling-project-docs` to generate the `docs/` content.