ui-ux-pro-max
[Frontend] Use when designing beautiful or aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.
test
[Testing] Use when you need to run tests locally and analyze the summary report.
code-simplifier
[Code Quality] Use when you need to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.
review-changes
[Code Quality] Use when reviewing current changes, staged or unstaged diffs, or branch-to-branch diffs.
watzup
[Utilities] Use when you need to review recent changes and wrap up the work.
commit
[Git] Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Flag: --push (a.k.a. "commit and push") stages + commits + pushes to remote in one shot.
test-ui
[Testing] Use when you need full-site QA audit (accessibility, performance, security, SEO) with visual reports.
web-design-guidelines
[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.
compact
[Utilities] Use when you need to compress context to optimize token usage (user-facing alias for context-optimization Strategy #3 Compress).
webapp-testing
[Testing] Use when you need individual page/component testing with Python Playwright scripts.
context-optimization
[Utilities] Use when managing context window usage, compressing long sessions, or optimizing token usage.
code-review
[Code Quality] Use when evaluating review feedback, requesting targeted code-quality review, or verifying completion claims.
ck-help
[Utilities] Use when you need claudeKit usage guide - just type naturally.
why-review
[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.
checkpoint
[Utilities] Use when you need to save analysis context to a checkpoint file for recovery (user-facing alias for memory-management Part 1 CHECKPOINT_CREATE).
context
[Utilities] Use when you need to load project context for current session.
sequential-thinking
[AI & Tools] Use when you need to apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification.
coding-level
[Utilities] Use when you need to set coding experience level for tailored explanations.
scout
[Investigation] Use when quickly locating relevant files and affected areas across a large codebase.
refactoring
[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.
recover
[Utilities] Use when you need to restore workflow context from checkpoint after session loss.
pr
[Git] Use when you need to create pull request with standard format.
research
[Planning] Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
project-manager
[Project Management] Use when you need to generate project status reports, track dependencies, manage risk registers, and facilitate team sync meetings.
package-upgrade
[Code Quality] Use when the user asks to analyze package upgrades, check for outdated dependencies, plan npm/NuGet updates, or assess breaking changes in package updates.
release-notes
[Git] Use when creating release notes from git history.
memory-management
[Utilities] Use when saving or recovering task progress across sessions via file checkpoints — especially before context compaction.
problem-solving
[Utilities] Use when applying structured problem-solving frameworks to complex, blocked, recurring, or uncertain decisions.
product-owner
[Project Management] Use when you need to capture ideas, manage product backlogs, apply prioritization frameworks (RICE, MoSCoW), and facilitate stakeholder communication.
markdown-to-pdf
[Document Processing] Use when you need to convert markdown files to PDF with syntax highlighting and custom CSS support.
markdown-to-docx
[Document Processing] Use when you need to convert markdown files to Microsoft Word ( DOCX) format with GFM support and math rendering.
plan-analysis
[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.
plan-validate
[Planning] Use when you need to validate a plan with critical questions interview.
pdf-to-markdown
[Document Processing] Use when you need to convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR).
lint
[Code Quality] Use when you need to run linters and fix issues for backend or frontend.
learn
[Utilities] Use when you need to teach Claude lessons that persist across sessions.
plan-review
[Planning] Use when you need to auto-review a plan for validity, correctness, and best practices — recursive: review, validate findings with why-review, fix validated findings, full re-review until no findings.
plan
[Planning] Use when you need intelligent plan creation with prompt enhancement. Flag: --mode={ci|cro} (default none — standard planning); --mode=ci plans a fix from a GitHub Actions CI run/log, --mode=cro plans conversion-rate optimization (25-item CRO framework).
figma-design
[Frontend] Use when you need to extract design context from Figma URLs via MCP, REST API, or screenshot fallback.
devops
[DevOps] Use when deploying to Cloudflare (Workers, R2, D1, KV, Pages), Docker, or GCP (Compute Engine, GKE, Cloud Run).
git-merge
[Git] Use when you need ⚠️ Merge code from one branch to another.
fix
[Implementation] Use when you need to analyze and fix issues [INTELLIGENT ROUTING]. Flag: --target={ci|issue|logs|test|types|ui} scopes the fix; --target=types resolves TypeScript errors inline.
frontend-design
[Frontend] Use when you need to create distinctive, production-grade frontend interfaces with high design quality.
docs-update
[Documentation] Use when updating impacted documentation after code, spec, or test changes.
investigate
[Fix & Debug] Use when you need to investigate and explain how existing features or logic work. Flag: --mode=explain produces a one-way developer-narrative explanation (Purpose → How → Why → Impact) tuned by coding level; use /understand for the standalone prompt-driven explainer.
documentation
[Code Quality] Use when the user asks to enhance documentation, add code comments, create API docs, improve technical documentation, document code, or update README files.
docx-to-markdown
[Document Processing] Use when you need to convert Microsoft Word ( DOCX) files to Markdown with GFM support (tables, images, code blocks).
worktree
[Git] Use when you need to create isolated git worktree for parallel development.
docs-seeker
[Documentation] Use when finding technical documentation for libraries, frameworks, repositories, or implementation topics.
docs-init
[Documentation] Use when you need to initialize project reference docs via hook + scan skills.
Page 1150 of 1635 · 81738 results
