dev-brainstorm
REQUIRED Phase 1 of /dev workflow. Uses Socratic questioning to understand requirements before exploration.
dev-clarify
REQUIRED Phase 3 of /dev workflow. Asks targeted questions based on codebase exploration findings.
ds-review
REQUIRED Phase 4 of /ds workflow. Reviews methodology, data quality, and statistical validity.
ai-anti-patterns
This skill should be used when reviewing AI-generated text, checking for AI writing patterns, detecting undisclosed AI content, or before finalizing any written content. Covers 12 categories of AI writing indicators from Wikipedia's comprehensive guide.
dev-debug
This skill should be used when the user asks to 'debug', 'fix bug', 'investigate error', 'why is it broken', 'trace root cause', 'find the bug', or needs systematic bug investigation and fixing with verification-driven methodology using ralph loops.
dev-delegate
Internal skill used by dev-implement during Phase 5 of /dev workflow. NOT user-facing - should only be invoked by dev-ralph-loop inside each implementation iteration. Handles Task agent spawning with TDD enforcement and two-stage review (spec compliance + code quality).
dev-design
REQUIRED Phase 4 of /dev workflow. Proposes architecture approaches with trade-offs and gets user approval.
dev-explore
REQUIRED Phase 2 of /dev workflow after dev-brainstorm. This skill should be used when you need to 'explore the codebase', 'map architecture', 'find similar features', 'discover test infrastructure', 'trace execution paths', 'identify code patterns', or understand WHERE code lives and HOW it works before implementation. Launches parallel explore agents and returns prioritized key files list.
dev-implement
REQUIRED Phase 5 of /dev workflow. Orchestrates per-task ralph loops with delegated TDD implementation.
dev-ralph-loop
Per-task ralph loop pattern for implementation and debugging. One loop per task, not one loop per feature.
dev-review
REQUIRED Phase 6 of /dev workflow. Combines spec compliance and code quality checks with confidence scoring.
dev-tdd
Test-Driven Development protocol. RED-GREEN-REFACTOR cycle with mandatory test-first approach.
dev-test-chrome
Chrome MCP browser testing. Console/network debugging, JS execution, GIF recording.
dev-test-hammerspoon
macOS desktop E2E testing with Hammerspoon, screencapture, and cliclick.
dev-test-linux
Linux desktop E2E testing with ydotool (Wayland), xdotool (X11), grim, and D-Bus.
dev-test-playwright
Playwright MCP browser testing. Headless E2E, cross-browser, CI/CD automation.
dev-test
Testing tool router. Routes to platform-specific skills: Chrome MCP, Playwright, Hammerspoon, Linux.
dev-tools
This skill should be used when the user asks "what plugins are available", "list dev tools", "what MCP servers can I use", "enable code intelligence", or needs to discover available development plugins like serena, context7, or playwright.
Page 1 of 3 · 40 results