no-vibe

Guide developers to write project code through Socratic, prediction-gated instruction.

36|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/rizukirr/no-vibe --skill no-vibe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-vibe
Source: https://github.com/rizukirr/no-vibe/tree/main/plugins/no-vibe/skills/no-vibe
Command: npx skills add https://github.com/rizukirr/no-vibe --skill no-vibe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It solves the gap between getting fast answers from an AI and actually building engineering understanding by forcing a learn-by-writing workflow that emphasizes decision-making, prediction, and verification.

Core Features & Use Cases

  • Socratic tutoring with graded help: guides the user toward the right shape of solution using hints and structured escalation instead of dumping completed code.
  • Prediction-gated learning loops: requires the user to name edge cases or expected intermediate values before running, turning execution into self-testing.
  • Reference-grounded teaching: when a reference repo is attached, the skill anchors conceptual examples to real file:line citations to avoid hallucinated APIs.
  • Hard safety boundary for project writes: prevents the assistant from writing into the user’s project files; the user types everything.

Quick Start

Activate no-vibe by creating the .no-vibe/active marker at your project root and then invoke /no-vibe to start a gated, layer-by-layer tutoring session.

Frequently Asked Questions about no-vibe

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

FAQPage Schema
How does Socratic tutoring help with learning to code instead of just generating it?

Socratic tutoring guides developers through hints and structured help escalation, forcing a learn-by-writing workflow that emphasizes decision-making, prediction, and verification rather than dumping completed code.

Can I use reference grounding to prevent hallucinated APIs during code review?

Yes, reference grounding anchors conceptual examples to real file:line citations from an attached reference repo, preventing hallucinated APIs and ensuring accurate, context-driven code review and tutoring sessions.

How do I start a prediction-gated learning session for stepwise feature implementation?

Start prediction-gated learning by creating the .no-vibe/active marker at your project root and invoking /no-vibe, which initiates a gated, layer-by-layer tutoring session requiring you to name edge cases before running code.

Does this learning method enforce a hard safety boundary for project writes?

Yes, a hard safety boundary prevents the assistant from writing into your project files, requiring the user to type everything manually to enforce active learning and retain full control over code implementation.

What's the best way to debug code using Socratic learning loops?

Debugging with Socratic learning loops requires you to predict expected intermediate values and name edge cases before execution, turning runtime into self-testing while the assistant provides graded help escalation.

Do I need external dependencies to use reference-grounded teaching?

No external dependencies are required, but attaching a reference repo enables the skill to anchor conceptual examples to real file:line citations, avoiding hallucinated APIs during stepwise feature implementation and debugging.