Skip to main content
ClaudeWave

Claude Code Slash Commands · page 10

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

1,092 slash commands1-command install
  1. Cortex decay engine — auto-archive stale memories (Pro)

  2. Export memories to CLAUDE.md

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

  4. Delete a memory by key

  5. Run diagnostics on Nemp Memory health and integrity

  6. Import memories from other AI providers (Pro)

  7. init124

    Auto-detect project stack and save as memories

  8. List all global memories

  9. list124

    List all saved memory keys

  10. log124

    View memory access log (reads, writes, deletes)

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

  12. Retrieve a global memory

  13. Retrieve a memory by key or search query

  14. Save a memory globally across all projects

  15. save124

    Save a key-value memory entry to persistent storage

  16. Analyze activity and suggest memories to save

  17. sync124

    Two-way sync between Nemp Memory and CLAUDE.md

  18. cto110

    Get CTO-level strategic and technical guidance

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

  20. Design system architecture with roadmap and technology recommendations

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

  22. Bootstrap or verify agents-shipgate as the deterministic merge gate for AI-generated agent capability changes

  23. 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.

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

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

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

  27. Build Solana program (Anchor or native)

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

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

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

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

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

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

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

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

  36. Plan feature implementation with technical specifications for Solana projects

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

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

  39. Resync external skill submodules to latest upstream versions

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

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

  42. Configure MCP server API keys in .env

  43. Run tests and automatically fix common issues

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

  45. Run Rust tests for Solana programs and backend services

  46. Run TypeScript tests for Solana frontends and Anchor programs

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

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

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

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

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

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

  53. Resume from the most recent saved handoff

  54. List recent handoffs and resume from a selected one

  55. Save a rich handoff summary for resuming later

  56. Enter REVIEW mode to validate implementation

  57. List all memories across branches

  58. Recall memories from current branch's memory bank

  59. Save context to branch-aware memory bank

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

  61. Enter EXECUTE mode to implement approved plan

  62. Enter INNOVATE mode for brainstorming approaches

  63. Enter PLAN mode to create detailed technical specifications

  64. Enter RESEARCH mode for information gathering

  65. Enable strict RIPER protocol enforcement

  66. Execute full RIPER workflow for a feature

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

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

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

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

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

  72. Initialize project documentation, preferences, or design tokens

  73. 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.

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

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

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

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

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

  79. Apply workflow improvements discovered during audit with approval workflow

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

  81. Post release announcement to X (Twitter) with GitHub link reply

  82. Expert prompt engineer that creates optimized, XML-structured prompts with intelligent depth selection

  83. Automate complete release workflow for Spec-Flow package (version bump, CHANGELOG, git tag, GitHub release, npm publish)

  84. Initialize and manage parallel AI developer worktrees (Dev Studio). Creates persistent worktrees for concurrent Claude Code agents.

  85. Manage workflow context (handoffs, todos, session status)

  86. Generate project-specific skills, commands, or hooks based on detected patterns from workflow audits

  87. Create Claude Code extensions (prompts, commands, agents, skills, hooks)

  88. Delegate one or more prompts to fresh sub-task contexts with parallel or sequential execution

  89. Diagnose and repair corrupted workflow state. Use when state.yaml is invalid, phases are stuck, or domain-memory.yaml has stale locks.

  90. Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success)

  91. Execute systematic debugging workflow via spec-cli.py, track failures in error-log.md, and generate session reports

  92. Finalize documentation (CHANGELOG, README, help docs), update GitHub milestones/releases, and cleanup branches after production deployment

  93. Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits

  94. Run 15 parallel quality gates (core checks, E2E/visual, pre-CI validation, plus contracts/load/integrity for epics) with auto-retry for transient failures

  95. Generate implementation plan from spec using research-driven design (meta-prompting for epics)

  96. Generate complete feature specification with research, requirements analysis, and quality validation

  97. Generate TDD task breakdown from plan.md with test-first sequencing and mockup-first mode (--ui-first)

  98. Analyze spec, plan, and tasks for consistency violations, breaking changes, and constitution compliance. Generates analysis-report.md with CRITICAL/MAJOR/MINOR findings.

  99. Add, update, or remove engineering principles in docs/project/engineering-principles.md with atomic versioned commits

  100. Interactive wizard to configure user preferences for command defaults and behavior