Skip to content

Commit 497b4e0

Browse files
KevenWMarkhamclaude
andcommitted
docs(claude): add available skills reference to commands.md
- Add Superpowers skills (brainstorming, TDD, debugging, code review) - Add Document skills (xlsx, docx, pptx, pdf) - Add Creative skills (canvas-design, algorithmic-art, artifacts) - Add Builder skills (skill-creator, mcp-builder, webapp-testing) - Document skill usage rules and priority order Sprint: epic-01/sprint-01 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent ba1eada commit 497b4e0

File tree

1 file changed

+69
-0
lines changed

1 file changed

+69
-0
lines changed

.claude/commands.md

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -227,6 +227,75 @@ specs/epics/epic-XX-name/sprints/sprint-XX/deployment/
227227

228228
---
229229

230+
## Available Skills
231+
232+
Claude has access to specialized skills. Invoke with `/skill-name` or use the Skill tool.
233+
234+
### Superpowers Skills (Development Workflow)
235+
236+
| Skill | When to Use |
237+
| --------------------------------------------- | ------------------------------------------------------------------ |
238+
| `/superpowers:brainstorming` | **BEFORE any creative work** - features, components, modifications |
239+
| `/superpowers:write-plan` | Create detailed implementation plans with bite-sized tasks |
240+
| `/superpowers:execute-plan` | Execute plans in batches with review checkpoints |
241+
| `/superpowers:test-driven-development` | Before writing implementation code |
242+
| `/superpowers:systematic-debugging` | When encountering bugs, test failures, unexpected behavior |
243+
| `/superpowers:verification-before-completion` | Before claiming work is complete or creating PRs |
244+
| `/superpowers:requesting-code-review` | After completing tasks or major features |
245+
| `/superpowers:receiving-code-review` | When receiving feedback, before implementing suggestions |
246+
| `/superpowers:finishing-a-development-branch` | When implementation complete, deciding merge/PR/cleanup |
247+
| `/superpowers:using-git-worktrees` | Starting feature work needing isolation |
248+
| `/superpowers:dispatching-parallel-agents` | When facing 2+ independent tasks |
249+
| `/superpowers:writing-skills` | Creating or editing skills |
250+
251+
### Document Skills
252+
253+
| Skill | When to Use |
254+
| ----------------------- | ------------------------------------------------ |
255+
| `/document-skills:xlsx` | Create, edit, analyze spreadsheets (.xlsx, .csv) |
256+
| `/document-skills:docx` | Create, edit Word documents with tracked changes |
257+
| `/document-skills:pptx` | Create, edit PowerPoint presentations |
258+
| `/document-skills:pdf` | Extract text, fill forms, merge/split PDFs |
259+
260+
### Creative Skills
261+
262+
| Skill | When to Use |
263+
| ----------------------------------- | ------------------------------------------------ |
264+
| `/example-skills:canvas-design` | Create visual art, posters, designs (.png, .pdf) |
265+
| `/example-skills:algorithmic-art` | Generative art using p5.js |
266+
| `/example-skills:artifacts-builder` | Complex multi-component HTML artifacts |
267+
| `/example-skills:slack-gif-creator` | Animated GIFs for Slack |
268+
| `/example-skills:theme-factory` | Style artifacts with themes |
269+
| `/example-skills:brand-guidelines` | Apply Anthropic brand colors/typography |
270+
271+
### Builder Skills
272+
273+
| Skill | When to Use |
274+
| -------------------------------- | -------------------------------------- |
275+
| `/example-skills:skill-creator` | Create new skills for Claude |
276+
| `/example-skills:mcp-builder` | Build MCP servers for LLM integrations |
277+
| `/example-skills:webapp-testing` | Test web apps with Playwright |
278+
| `/example-skills:internal-comms` | Write internal communications |
279+
280+
### Skill Usage Rules
281+
282+
1. **Check for applicable skills BEFORE any response**
283+
2. **Invoke skill if even 1% chance it applies**
284+
3. **Brainstorming skill required before creative/feature work**
285+
4. **TDD skill before implementation**
286+
5. **Verification skill before claiming completion**
287+
288+
### Skill Priority Order
289+
290+
When multiple skills apply:
291+
292+
1. **Process skills first** (brainstorming, debugging)
293+
2. **Implementation skills second** (frontend, mcp-builder)
294+
295+
Example: "Build feature X" → brainstorming first, then implementation skills
296+
297+
---
298+
230299
## Remember
231300

232301
1. **NO CODE** when orchestrating

0 commit comments

Comments
 (0)