Skip to main content
ClaudeWave

Claude Code Slash Commands · page 7

Slash commands for Claude Code collected from the directory: prompt definitions you can install into ~/.claude/commands with one command.

967 slash commands1-command install
  1. Validate that vulnerability findings are real, reachable, and exploitable

  2. Web application security scanner (alpha)

  3. One-shot MAXIMAL autonomous pentest — the full scan+validate pipeline PLUS a parallel red-team agent war-game, adversarially verified and stitched into a kill-chain Red Team Report.

  4. Commit what is already staged — runs the commit subagent in the background, following the ATLAS commit convention.

  5. Interview Boss about the project, then reason from first principles to design the ideal ATLAS operating identity/system-prompt for it — free to drop KISS/YAGNI/DRY/clean-architecture entirely when the project (and the LLM's own distribution) calls for a different mindset

  6. Initialize project context — understand the project, configure conventions, and set up project rules

  7. Brainstorm an idea into a clickable multi-screen React prototype — model the mind (Theory of Mind), interview to kill ambiguity, build a no-build CDN-React prototype under misc/prototypes/, run it, iterate until it matches Boss's vision.

  8. Quickly sketch a standalone low-fidelity wireframe as self-contained HTML — gray boxes, dashed borders, no framework. Lighter than /plan:create-phase, static unlike /brainstorm:prototype.

  9. Discover the project's visual identity, prototype 3 HTML design variants for Boss to compare in a browser, iterate, then lock in DESIGN.md (Stitch-format, machine + human readable). The single source of truth AI coding agents read before generating UI.

  10. log300

    Show recent git commits with a brief summary and continual context tied to the working directory / staging area.

  11. Stage and commit all working-directory changes — runs the commit subagent in the background until the tree is clean.

  12. Create a development phase the lean way — resolve ambiguity through Q&A, then capture it as a self-contained low-fidelity wireframe HTML document you implement from in plan mode

  13. Guided feature development with codebase understanding and architecture focus

  14. Author human-readable manual test cases (markdown) into docs/living-test-cases/ — the living artifact that /qa:manual-test-run executes

  15. One-shot an app autonomously — free-will the founding fork, build with deliberate decisions at every trigger, then adversarial review and a conscious final pass before delivery

  16. Run the Customer Discovery workflow (research -> JTBD -> opportunities -> problem)

  17. Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call)

  18. Run the Feature Kickoff workflow (problem -> hypothesis -> PRD -> stories)

  19. Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis)

  20. Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff

  21. Run the Post-Launch Learning workflow (instrumentation -> dashboard -> results -> retro -> lessons)

  22. Run the Product Strategy workflow (competitive analysis -> stakeholders -> opportunities -> solution -> ADR)

  23. Run the Sprint Planning workflow (refinement -> stories -> edge cases)

  24. Run the Stakeholder Alignment workflow (stakeholders -> problem -> solution -> launch)

  25. Run the Technical Discovery workflow (spike -> ADR -> design rationale)

  26. Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)

  27. Scout given directories to respond to the user's requests

  28. Bootstrap a new project

  29. Brainstorm a feature

  30. Analyze the current copy issues and enhance it

  31. fast290

    Analyze and fix the issue [FAST]

  32. good290

    Create an immersive design

  33. cook290

    Implement a feature

  34. Debugging technical issues and providing solutions.

  35. 3d290

    Create immersive interactive 3D designs with Three.js

  36. Describe a design based on screenshot/video

  37. Create a design based on screenshot

  38. Create a design based on video

  39. init290

    Analyze the codebase and create initial documentation

  40. Analyze the codebase and update documentation

  41. Analyze the codebase and update documentation

  42. ci290

    Analyze Github Actions logs and provide a plan to fix the issues

  43. hard290

    Use subagents to plan and fix hard issues

  44. logs290

    Analyze logs and fix issues

  45. test290

    Debugging technical issues and providing solutions.

  46. Fix type errors

  47. cm290

    Stage all files and create a commit.

  48. cp290

    Stage, commit and push all code in the current branch

  49. Implement payment integration with Polar.sh

  50. plan290

    Research, analyze, and create an implementation plan

  51. two290

    Research & create an implementation plan with 2 approaches

  52. Review recent changes and wrap up the work

  53. |

  54. Launch the API documentation specialist for OpenAPI specs

  55. api272

    Launch the API development agent for backend implementation

  56. Alternative command for content creation

  57. Debug an error or issue

  58. Alternative command for DevOps deployment tasks

  59. Launch the DevOps specialist for CI/CD and deployment

  60. Generate or update documentation

  61. Launch the frontend development agent for UI implementation

  62. Launch the marketing content specialist

  63. plan272

    Launch the project planning agent for strategic task decomposition

  64. Launch the product management specialist

  65. Refactor code for better structure and maintainability

  66. Alternative command for requirements gathering

  67. Trigger code review on recent changes

  68. Scan for security vulnerabilities

  69. Launch the ShadCN UI builder agent for component-based UI development

  70. tdd272

    Launch the TDD specialist for test-driven development

  71. Alternative command for TDD specialist focusing on test-first approach

  72. test272

    Run tests and fix failures

  73. ui272

    Launch the ShadCN UI builder agent for interface design and implementation

  74. Run an accessibility audit on the current project for WCAG compliance.

  75. Reverse-engineer a Product Requirements Document from existing code.

  76. Build a competitive analysis matrix comparing products or tools.

  77. Assess financial health of a SaaS business using key metrics.

  78. Apply a focused, minimal-change bugfix with minimal blast radius.

  79. cm260

    Stage working tree changes and create a Conventional Commit (no push).

  80. cp260

    Stage, commit, and push the current branch following git governance rules.

  81. pr260

    Create a pull request from the current branch.

  82. okr260

    Create or review OKRs (Objectives and Key Results).

  83. Activate a cross-domain persona for the current session.

  84. Design or review a CI/CD pipeline for the current project.

  85. Audit installed plugins, extensions, and dependencies for security and health.

  86. prd260

    Create a Product Requirements Document from scratch.

  87. Assess overall project health across code quality, tests, docs, and activity.

  88. Run a sprint retrospective with data-driven insights from git history.

  89. Run the local review gate before pushing.

  90. rice260

    RICE-score features or tasks for prioritization.

  91. Generate a SaaS health dashboard with key business metrics.

  92. Run the security scan gate before pushing.

  93. Run an SEO audit on web content and HTML files.

  94. Check current sprint health and identify risks.

  95. Plan a sprint by analyzing backlog, estimating capacity, and selecting work.

  96. tdd260

    Guide a Test-Driven Development workflow for the current task.

  97. Scan and prioritize technical debt in the codebase.

  98. Create well-structured user stories with acceptance criteria.

  99. Check the daily pipeline's state — last run, today's report files, Sonnet quota, recent failures

  100. Trigger the daily digest now (background via OS scheduler) and monitor until completion