Slash Commands de Claude Code · página 9

Resume a long-running DMP workflow (engagement / campaign-plan / content-engine / seo-audit / competitor-analysis / campaign-audit / launch-campaign) that was interrupted partway through

Run a comprehensive SEO audit — technical health, on-page, content gaps, E-E-A-T, link profile, and competitor benchmarking

Compare two SEO snapshots (GSC / GSC AI Performance / rank tracker / AEO probe) and surface top movers per metric with auto-classification — growth / decline / reshuffle / stable / new / lost

Unified status snapshot of the active brand: profile, engagements, recent insights, recent compliance violations, Python dependency mode.

Analyze user corrections and log them into the error notebook

Review the error notebook — flip through past corrections before working

Create a handoff file for another session to pick up

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

Guided version bump — validate, tag, and create GitHub release

Run pre-release validation checks on all SKILL.md files and JSON databases

Execute validated plans with isolated agents and two-stage review

Iterative planning with human checkpoints at every phase

Final shipping gate. PR creation, documentation updates, and merge with human approval.

Post-execution verification gate. Tests, lint, type-check, then see it working.

Estimate and track token usage and cost across the knowledge pipeline. Run before expensive tasks to budget, after tasks to log actuals.

Activate Nemp Pro with your license key

View captured activity log

Enable or disable automatic activity capture

Enable or disable automatic cross-provider memory export

Enable or disable automatic syncing to CLAUDE.md

Search memories by keyword and show relevant context

Nemp Cortex — memory intelligence layer (Pro)

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

Export memories to CLAUDE.md

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

Delete a memory by key

Run diagnostics on Nemp Memory health and integrity

Import memories from other AI providers (Pro)

Auto-detect project stack and save as memories

List all global memories

List all saved memory keys

View memory access log (reads, writes, deletes)

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

Retrieve a global memory

Retrieve a memory by key or search query

Save a memory globally across all projects

Save a key-value memory entry to persistent storage

Analyze activity and suggest memories to save

Two-way sync between Nemp Memory and CLAUDE.md

Audit recurring context files and suggest usage-limit optimizations.

Explain or summarize Governor vs Caveman performance benchmark results.

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

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

Check current changes against the latest approved implementation contract.

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

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

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

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

Show Claude Code Governor usage dashboard and waste heat map.

Enable strict governance behavior for the current task.

Get CTO-level strategic and technical guidance

Get strategic guidance on build vs buy and technology decisions

Design system architecture with roadmap and technology recommendations

Validate plans, roadmaps, or proposals with ruthless honesty

Enter REVIEW mode to validate implementation

List all memories across branches

Recall memories from current branch's memory bank

Save context to branch-aware memory bank

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

Enter EXECUTE mode to implement approved plan

Enter INNOVATE mode for brainstorming approaches

Enter PLAN mode to create detailed technical specifications

Enter RESEARCH mode for information gathering

Enable strict RIPER protocol enforcement

Execute full RIPER workflow for a feature

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

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

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

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

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

Initialize project documentation, preferences, or design tokens

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.

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

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

Deploy feature through automated staging validation to production with rollback testing

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

Audit workflow effectiveness and generate improvement recommendations after epic completion

Apply workflow improvements discovered during audit with approval workflow

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

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

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

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

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

Manage workflow context (handoffs, todos, session status)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Interactive wizard to configure user preferences for command defaults and behavior

Generate 8 project design documents (overview, architecture, tech-stack, data, API, capacity, deployment, workflow) via interactive questionnaire or config file