ash1794/vibe-engineering Skills

Validate completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.

Generate edge case and failure mode test cases after happy-path tests are written. Covers boundary values, nil inputs, concurrency, resource exhaustion, and malformed data.

Detect and prevent shortcut rationalization — when Claude is about to skip a step, simplify a requirement, or optimize away a constraint. Use proactively when you notice rationalization patterns.

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 integrate commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.

Audit tests for concurrency safety -- race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.

Enforce tiered test coverage standards — critical paths >=90%, business logic >=80%, general code >=70%. Use before claiming code is complete.

Record resolved bugs in a persistent journal — symptom, root cause, difficulty, fix, prevention. Organized by category for future reference.

Record architectural and technology decisions in ADR format for cross-session persistence. Use after making any significant design choice.

Challenge recommendations, designs, or synthesis by adversarial review across 5 dimensions. Use before shipping any significant recommendation or design document.

Fast 6-point quality check for technical documents (specs, design docs, READMEs). Use after editing any specification or design document.

Generate fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input). Seeds corpus from existing fixtures and runs initial pass.

Implement snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots.

Generate a session continuity document at the end of a long session or when switching context on a multi-session project. Enables seamless resumption.

End-of-iteration review with quality grading, metrics, and trend analysis. Use at the end of each development iteration or sprint.

Analyze large tasks for independent subtasks that can be safely parallelized. Produces a DAG-based dispatch plan with dependency ordering and maximum parallelism.

Detect recurring implementation patterns and record them for reuse. When the same code pattern appears 3+ times, it belongs in the pattern library.

Scan staged changes for secrets, debug statements, TODOs without references, and other common commit mistakes. Use before creating any commit.

Set quality expectations for implementation — "imagine this serves 1 million users." Checks for observability, error handling, input validation, graceful degradation.

Enforce the Implement→Review→Test→Fix→Loop cycle until work is clean. Use after any non-trivial implementation to prevent "good enough" exits.