You MUST use this before any creative work or multi-step task. Explores intent, requirements, and design before implementation. Then documents the plan before coding.
From cmnpx claudepluginhub tody-agent/codymaster --plugin cmThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Implements distributed tracing with Jaeger/Tempo for microservices, including Kubernetes/Docker setup and OpenTelemetry instrumentation (Python/Flask). Use for debugging latency, dependencies, and request flows.
Two phases, one skill: Explore WHAT to build, then document HOW.
ALWAYS before:
Understand Intent — What does the user ACTUALLY want?
Explore Options — What are the approaches?
Define Scope — What's in and what's out?
openspec/changes/[initiative-name]/specs/Design — How should it work?
cm-ui-preview to preview on Google Stitch before codingStandard: Fission-AI OpenSpec (
https://github.com/Fission-AI/OpenSpec/) Output artifacts exactly toopenspec/changes/[initiative-name]/to ensure human/AI alignment.
1. openspec/changes/[initiative-name]/design.md
# Design: [Goal]
## Context & Technical Approach
Why this approach and how it works.
## Proposed Changes
### [Component/File]
- What changes
- Why this approach
## Verification
How to verify it works.
2. openspec/changes/[initiative-name]/tasks.md
# Implementation Checklist
- [ ] 1.1 First component setup
- [ ] 1.2 First component logic
- [ ] 2.1 Next component integration
- [ ] Verification testing
✅ DO:
- Break into small, testable steps
- Order by dependency (foundations first)
- Include verification for each step
- Keep steps bite-sized (15-30 min each)
❌ DON'T:
- Write vague steps ("refactor the code")
- Skip verification steps
- Plan more than needed
- Over-engineer the plan itself
After writing an implementation plan, ALWAYS update .cm/CONTINUITY.md:
- Active Goal: → Set to the plan's #Goal
- Next Actions: → Set to first 3 tasks from the plan
- Current Phase: → Set to "planning"
- Working Context: → Key architecture decisions from the plan
Token savings: Next session picks up from CONTINUITY.md (~200 tokens) instead of re-reading the full plan (2,000+ tokens).
| After planning... | Use skill |
|---|---|
| Complex initiative/enhancement? | cm-brainstorm-idea (run BEFORE planning) |
| Need isolated workspace | cm-git-worktrees |
| Execute the plan (same session) | cm-execution |
| Write tests first | cm-tdd |
| Building UI/frontend | cm-ui-preview |
Think before you build. Document before you code. No exceptions.