Loading...
Loading...
Found 149 Skills
Deterministic 3-phase service health monitoring: Discover, Check, Report. Use when user asks about service status, process health, uptime, or whether services are running. Use for "health check", "is service up", "service status", "what's running", or "check if alive". Do NOT use for HTTP endpoint validation, performance profiling, or log analysis without a specific health concern.
Fish shell configuration: config.fish, functions, abbreviations, variable scoping, conf.d modules, and PATH management. Use when user's $SHELL is fish, editing .fish files, working in ~/.config/fish/, or migrating from Bash. Use for "fish config", "fish function", "abbr", "conf.d", "fish_add_path", or "funcsave". Do NOT use for Bash/Zsh-only scripts, POSIX shell portability, or non-shell configuration tasks.
Restore session state from handoff artifacts and route to the next action. Priority cascade: HANDOFF.json (highest) > .continue-here.md > incomplete task_plan.md > git log. Presents a status dashboard, then executes the next action. Use for "resume", "continue", "pick up where I left off", "what was I doing", "continue work". Do NOT use for starting new tasks (use /do), reviewing past sessions (use /retro), or reading task plans (read task_plan.md directly).
Weighted decision scoring framework for architectural and technology choices. Frames decisions with 2-4 options, scores against weighted criteria, detects close calls, and records decisions in the active ADR or task plan. Use when: "should I use X or Y", "which approach", "compare options", "trade-offs between", "help me decide", "evaluate alternatives"
Persistent memory system for Claude Code. Two-layer architecture (hot cache + knowledge wiki), safety hooks, /close-day end-of-day synthesis. Zero external dependencies.
Read-only exploration, status checks, and reporting without modifications. Use when user asks to check status, find files, search code, show state, or explicitly requests read-only investigation. Do NOT use when user wants changes, fixes, refactoring, or any write operation.
DAG-based multi-skill orchestration: Discover, Plan, Validate, Execute. Builds execution graphs for tasks requiring multiple skills in sequence or parallel with dependency resolution and context passing. Use when a task requires 2+ skills chained together, parallel skill execution, or conditional branching between skills. Use for "compose skills", "chain workflow", "multi-skill", or "orchestrate skills". Do NOT use when a single skill can handle the request, or for simple sequential invocation that needs no dependency management.
Systematic 6-phase analysis of external repositories for ideas worth adopting: clone, parallel deep-read, self-inventory, synthesize gaps, targeted audit of affected subsystems, reality-grounded report. Use when evaluating whether an external repo provides value, analyzing repos for useful patterns, or comparing approaches. Do NOT use for general codebase exploration (use explore-pipeline instead).
Validate a published or draft-preview WordPress post in a real browser using Playwright. Checks rendered title, heading structure, image loading, OG/meta tags, JavaScript errors, and responsive layout at mobile/tablet/desktop breakpoints. When Chrome DevTools MCP is available, can use it for live browser inspection as an alternative to Playwright. Use for "validate wordpress post", "check live post", "verify published post", "wordpress post looks right", "check og tags", or "responsive check wordpress". Do NOT use for source markdown validation (use pre-publish-checker), SEO keyword analysis (use seo-optimizer), or uploading content (use wordpress-uploader).
CLI-based image generation from text prompts using Google Gemini APIs via Python. Use when user needs "generate image", "create image with AI", "gemini image", "text to image", "create sprite", or "generate character art". Supports model selection, batch generation, watermark removal, and background transparency. Do NOT use for web app image features (use nano-banana-builder), video/audio generation, or non-Gemini models.
Maintain /do routing tables and command references when skills or agents are added, modified, or removed. Use when skill/agent metadata changes, after skill-creator-engineer or agent-creator-engineer runs, or when routing tables need synchronization. Use for "update routes", "sync routing", "routing table", or "refresh /do". Do NOT use for creating new skills/agents, modifying skill logic, or manual /do table edits.
Context-driven aesthetic exploration with anti-cliche validation: typography, color, animation, atmosphere. Use when starting a frontend needing distinctive aesthetics, refreshing generic designs, or auditing for "AI slop" patterns. Use for "distinctive frontend", "unique aesthetics", "avoid generic design", "creative frontend". Do NOT use for quick prototypes, strict brand compliance, backend projects, or data visualization.