Menü
Routes users to the right vibe-engineering skill for their current task. Use when user asks "what skill should I use?" or seems unsure about which skill to invoke.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Dispatches research agents to find real projects, papers, and documented failures before proposing any feature, architecture, or technology choice. Triggers on creative/design tasks, not on implementation of already-designed specs.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests.
Detects and prevents shortcut rationalization — when the agent is about to skip a step, simplify a requirement, or optimize away a constraint. Triggers proactively when rationalization patterns are noticed.
Provides a persistent cross-session task queue for work that should be done but isn't blocking current tasks. Enables background and future-session work tracking.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
| name | vibe-help |
| description | Routes users to the right vibe-engineering skill for their current task. Use when user asks "what skill should I use?" or seems unsure about which skill to invoke. |
| user-invocable | true |
You are the vibe-engineering skill router. Help the user find the right skill for their situation.
Ask the user what they're trying to do, then recommend skills based on their answer:
→ Start with: vibe-research-before-design, then vibe-production-mindset
→ During: vibe-quality-loop, vibe-scope-guard
→ After: vibe-reflect-and-compound, vibe-iteration-review
→ If 1-3 bugs: vibe-debugging-journal (after fixing)
→ If 10+ bugs: vibe-wave-based-remediation
→ Always: vibe-adversarial-test-generation (prevent recurrence)
→ Code review: vibe-devil-advocate-review
→ Spec review: vibe-spec-vs-code-audit, vibe-doc-quality-gate
→ Requirements: vibe-requirements-validator
→ Test planning: vibe-scenario-matrix
→ Coverage: vibe-coverage-enforcer
→ Edge cases: vibe-adversarial-test-generation
→ Parsers: vibe-fuzz-parser-inputs
→ Snapshots: vibe-golden-file-testing
→ Concurrent code: vibe-concurrent-test-safety
→ Pre-deploy: vibe-safe-deploy, vibe-pre-commit-audit
→ Risky change: vibe-rollback-plan
→ Health check: vibe-service-health-dashboard
→ Decompose: vibe-parallel-task-decomposition
→ Integrate: vibe-cherry-pick-integration
→ Async: vibe-async-task-queue
→ Before: vibe-research-before-design
→ Record: vibe-decision-journal
→ Challenge: vibe-devil-advocate-review
→ General: vibe-reflect-and-compound
→ Bug-specific: vibe-debugging-journal
→ Pattern: vibe-pattern-library
→ Handover: vibe-handover-doc
→ vibe-session-context-flush
→ Against criteria: vibe-acceptance-gate
→ Against spec: vibe-spec-vs-code-audit
→ Against shortcuts: vibe-anti-rationalization-check
→ Output format: vibe-structured-output
When routing, present:
/vibe-quality-loop)