Skip to main content
ClaudeWave

Claude Code Slash Commands · page 11

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

1,134 slash commands1-command install
  1. Review the error notebook — flip through past corrections before working

  2. Create a handoff file for another session to pick up

  3. 翻錯題本 — 複習之前被改過的地方

  4. Audit recurring context files and suggest usage-limit optimizations.

  5. Explain or summarize Governor vs Caveman performance benchmark results.

  6. Automatically compress CLAUDE.md or other memory files with protected-span safety. One-command token savings.

  7. full133

    Temporarily ask Governor to avoid compacting tool output for the next diagnostic step.

  8. Check current changes against the latest approved implementation contract.

  9. Install Governor compact-mode rule files into a project for Codex, Gemini, Cursor, Windsurf, or Cline.

  10. off133

    Disable Governor compact response mode while keeping telemetry/tool hooks available.

  11. on133

    Enable Governor compact professional mode for all prompts in this Claude Code session.

  12. plan133

    Create a compact implementation contract before broad app/site/game/refactor work.

  13. Show Claude Code Governor usage dashboard and waste heat map.

  14. Enable strict governance behavior for the current task.

  15. Activate Nemp Pro with your license key

  16. View captured activity log

  17. Enable or disable automatic activity capture

  18. Enable or disable automatic cross-provider memory export

  19. Enable or disable automatic syncing to CLAUDE.md

  20. Search memories by keyword and show relevant context

  21. Nemp Cortex — memory intelligence layer (Pro)

  22. Cortex decay engine — auto-archive stale memories (Pro)

  23. Export memories to CLAUDE.md

  24. Predict and return only memories relevant to your prompt (Pro)

  25. Delete a memory by key

  26. Run diagnostics on Nemp Memory health and integrity

  27. Import memories from other AI providers (Pro)

  28. init128

    Auto-detect project stack and save as memories

  29. List all global memories

  30. list128

    List all saved memory keys

  31. log128

    View memory access log (reads, writes, deletes)

  32. Export Nemp memories to Codex CLI, Cursor, and Windsurf rule files

  33. Retrieve a global memory

  34. Retrieve a memory by key or search query

  35. Save a memory globally across all projects

  36. save128

    Save a key-value memory entry to persistent storage

  37. Analyze activity and suggest memories to save

  38. sync128

    Two-way sync between Nemp Memory and CLAUDE.md

  39. cto112

    Get CTO-level strategic and technical guidance

  40. Get strategic guidance on build vs buy and technology decisions

  41. Design system architecture with roadmap and technology recommendations

  42. Validate plans, roadmaps, or proposals with ruthless honesty

  43. Aurora - independent community smart home orchestrator. Routes any smart home request to the right specialist skill and recommends the correct Claude model. Use this as your starting point for Home Assistant, ESPHome, Node-RED, or any IoT automation task.

  44. Resume from the most recent saved handoff

  45. List recent handoffs and resume from a selected one

  46. Save a rich handoff summary for resuming later

  47. Security audit for Solana programs (Anchor/native)

  48. Benchmark CU usage and compare against baseline for regression detection

  49. Build web client application (Next.js, React, Vite)

  50. Build Solana program (Anchor or native)

  51. Build Unity project (WebGL, Desktop, or PSG1)

  52. Initialize forked template — setup CLAUDE.md and remove config repo scaffolding

  53. Reproduce and debug a user-reported failing transaction against forked cluster state, mapping the failure back to source code

  54. Deploy Solana program (devnet first, then mainnet)

  55. AI-powered diff review for Solana-specific issues and code quality

  56. Explain complex Solana/blockchain code with visual diagrams and step-by-step breakdowns

  57. Generate TypeScript client from Solana program IDL using Codama or Anchor

  58. Migrate from @solana/web3.js to @solana/kit

  59. Plan feature implementation with technical specifications for Solana projects

  60. Profile compute unit usage per instruction in a Solana program

  61. Quick commit with automatic formatting, linting, and conventional commit message

  62. Resync external skill submodules to latest upstream versions

  63. Scaffold a new Solana project with programs, frontend, tests, and CI

  64. Setup CI/CD pipeline with automated security checks for Solana programs

  65. Configure MCP server API keys in .env

  66. Run tests and automatically fix common issues

  67. Run .NET/C# tests for Unity projects and backend services

  68. Run Rust tests for Solana programs and backend services

  69. Run TypeScript tests for Solana frontends and Anchor programs

  70. Update solana-ai-kit to latest version from upstream

  71. Generate documentation for Solana programs, APIs, and components

  72. Infrastructure-first security audit — secrets, supply chain, CI/CD, LLM/skill security, OWASP, STRIDE. Complements /audit-solana (program-level)

  73. Health check for the dev environment and solana-ai-kit config — read-only, with one exact fix-it command per failure

  74. Memory consolidation — dedupe, contradiction-check, prune, and re-rank MEMORY.md + CLAUDE.md Project Learnings. Run after major refactors

  75. Product quality review — first-time-user walkthrough, 8-dimension scorecard, prioritized fix roadmap. --harsh for the brutal roast variant

  76. Enter REVIEW mode to validate implementation

  77. List all memories across branches

  78. Recall memories from current branch's memory bank

  79. Save context to branch-aware memory bank

  80. Rebase current branch onto trunk (origin/master or origin/main), predict and resolve conflicts

  81. Enter EXECUTE mode to implement approved plan

  82. Enter INNOVATE mode for brainstorming approaches

  83. Enter PLAN mode to create detailed technical specifications

  84. Enter RESEARCH mode for information gathering

  85. Enable strict RIPER protocol enforcement

  86. Execute full RIPER workflow for a feature

  87. Execute multiple sprints in parallel based on dependency graph from sprint-plan.md

  88. Build and validate locally for projects without remote deployment (prototypes, experiments, local-only dev)

  89. Execute multi-sprint epic workflow from interactive scoping through deployment with parallel sprint execution and self-improvement

  90. Execute feature development workflow from specification through production deployment with automated quality gates

  91. Analyze workflow state and provide context-aware guidance with visual progress indicators and recommended next steps

  92. Initialize project documentation, preferences, or design tokens

  93. Implement small bug fixes and features (<100 LOC) without full workflow. Use for single-file changes, bug fixes, refactors, and minor enhancements that can be completed in under 30 minutes.

  94. Enter deep craftsman mode - question everything, plan like Da Vinci, craft insanely great solutions, then materialize to roadmap

  95. Display Vercel and Railway deployment quota usage with 24h rolling window analysis, quota reset predictions, and deployment strategy recommendations

  96. Deploy feature through automated staging validation to production with rollback testing

  97. Validate staging deployment before production through automated test review, rollback capability testing, guided manual validation, and optional gap capture for feedback loops

  98. Audit workflow effectiveness and generate improvement recommendations after epic completion

  99. Apply workflow improvements discovered during audit with approval workflow

  100. Display workflow health dashboard with velocity trends, quality metrics, and improvement tracking