no-vibe
01Plugin Claude Code
Forces you to write code yourself. AI shows and reviews, never writes to your files.
Plugin Claude Code
Forces you to write code yourself. AI shows and reviews, never writes to your files.
Plugin Claude Code
Tutor mode for AI coding assistants. AI shows code in chat and reviews your work, but never writes to your project files.
Command
One-shot escape hatch — let AI write code to project files for a single task, then restore no-vibe mode.
Command
Get a coding challenge based on your project or current no-vibe session.
Command
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
Instructions file CodexOpenCode
Instructions for rizukirr/no-vibe, covering agents, repo purpose, architecture (high-signal files), verification commands and conventions that are easy to miss.
Instructions file
Instructions for rizukirr/no-vibe, covering claude.md, repo purpose, verification, architecture — parallel surfaces, one behavior and two data layers (easy to confuse).
Instructions file Gemini CLI
Instructions for rizukirr/no-vibe, covering no-vibe — gemini cli context, adaptation iron law (binding when .no-vibe/active exists), activation marker, session start status and turn response contract (binding for every reply while on).
Skill Claude CodeCodex
One-shot escape hatch to temporarily disable no-vibe write guard for a single scoped task, then restore the marker.
Skill Claude CodeCodex
Generate a one-shot coding challenge based on current no-vibe session or project context. User writes all code; AI only gives constraints, hints, and review.
Skill Claude CodeCodex
Use ONLY when .no-vibe/active marker exists at the project root, or the user has just invoked /no-vibe / /no-vibe on. Do NOT trigger merely because the user wants to learn or type code themselves without those signals — the marker or explicit command is the required gate. Once active, you MUST read…