vibe

Switch Claude Code projects to vibe phase and block test file creation.

Updated Feb 1, 2026

Search Tags:#workflow #vibe #exploration #claude-code #feature-development #phase-switch #testing-gates

Ready to run

npx skills add https://github.com/mathonsunday/phase-workflow --skill vibe-mathonsunday

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe
Source: https://github.com/mathonsunday/phase-workflow/tree/main/scaffold/.claude/skills/vibe
Command: npx skills add https://github.com/mathonsunday/phase-workflow --skill vibe-mathonsunday

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exploration and experimentation in Claude Code projects without automatic test enforcement, enabling rapid idea prototyping.

Core Features & Use Cases

Lets you switch the project into vibe mode to relax quality gates and focus on feature discovery.
Supports rapid iteration on new ideas without test scaffolding, while keeping existing safety constraints visible.
Use case: a team prototyping a new feature where speed matters and test coverage is deferred.

Quick Start

Write the vibe command to update the phase and verify by reading the phase file.

Frequently Asked Questions about vibe

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

FAQPage Schema

How do I disable test enforcement in Claude Code for rapid prototyping?▼

To disable test enforcement in Claude Code for rapid prototyping, switch your project to the vibe phase. This updates the .claude/phase file and blocks new test file creation, allowing you to focus on rapid feature discovery without test scaffolding.

What is the vibe phase used for in feature development?▼

The vibe phase is used for early feature exploration and experimentation in Claude Code projects. It relaxes quality gates and disables automatic test file creation to prioritize rapid iteration and idea prototyping over immediate test coverage.

How do I switch to exploratory development mode without writing tests?▼

You can switch to exploratory development mode by writing the vibe command. This enforces phase-switch semantics, updates the project phase configuration, and blocks test file creation during your prototyping session.

Can I prototype new features in Claude Code without adding test coverage?▼

Yes, you can prototype new features without test coverage by switching to the vibe phase. This mode explicitly blocks test file creation, making it suitable for teams where speed matters and test scaffolding is deferred.

When should I avoid using the vibe phase for feature exploration?▼

You should avoid using the vibe phase for feature exploration when your project requires strict quality gates or immediate test coverage. The vibe phase blocks test file creation, making it unsuitable for production-ready development phases.