vibe

Enforce TDD red/green/refactor cycles for small code changes.

92|9|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Ovid/paad --skill vibe-ovid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe
Source: https://github.com/Ovid/paad/tree/main/plugins/paad/skills/vibe
Command: npx skills add https://github.com/Ovid/paad --skill vibe-ovid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safe vibe coding introduces guardrails to ensure small fixes are implemented with a disciplined approach, preventing reckless changes during rapid iterations.

Core Features & Use Cases

  • Mandatory TDD: enforce red/green/refactor cycles before any change is accepted.
  • Architecture awareness: checks for potential architectural issues in small tasks.
  • Reusable components: detects existing utilities to minimize duplication.
  • Test infrastructure checks: ensures tests exist and pass before integration.

Quick Start

Describe the task to fix and I will apply guardrails to ensure a safe, fast change.

Frequently Asked Questions about vibe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TDD guardrails for rapid bug fixes and small code changes?

To enforce TDD guardrails for small code changes, describe the task to apply mandatory red/green/refactor cycles, ensuring tests exist and pass before integration proceeds.

What is safe vibe coding and how does it prevent reckless changes during rapid iterations?

Safe vibe coding introduces TDD guardrails and architecture awareness to prevent reckless changes, ensuring rapid iterations remain disciplined by checking for reusable components and test infrastructure.

How do I check for reusable components and test infrastructure before a small refactor?

To check for reusable components and test infrastructure before a refactor, apply guardrails that detect existing utilities and ensure tests exist and pass before integration.

When should I not use TDD guardrails for small code tweaks?

You should avoid TDD guardrails for small code tweaks when your rapid iteration requires bypassing architecture checks, reusable component detection, and mandatory test infrastructure validation.

What's the best way to apply architecture awareness to quick tweaks across my codebase?

The best way to apply architecture awareness to quick tweaks is to use guardrails that check for potential architectural issues and reusable components, enforcing a mandatory TDD cycle before changes proceed.