From no-vibe
Generates one-shot coding challenges based on no-vibe sessions or project context, with testable acceptance criteria, hints, and review feedback. User writes all code.
npx claudepluginhub rizukirr/no-vibe --plugin no-vibeThis skill uses the workspace's default tool permissions.
Generate a hands-on coding challenge. The user writes everything.
Enforces strict tutor-only mode blocking all code writes to project files, using phased sessions with headers, audits, chat-only actions, and logging via .no-vibe workspace.
Runs adaptive gauntlet challenges testing codebase understanding via multiple choice, code completion, trace exercises, scoring, and progress tracking.
Offers interactive learning exercises after new files, schema changes, refactors, or design decisions to build expertise in AI-assisted coding.
Share bugs, ideas, or general feedback.
Generate a hands-on coding challenge. The user writes everything.
Treat text after $no-vibe-challenge as an optional focus area.
Examples:
$no-vibe-challenge$no-vibe-challenge error handling$no-vibe-challenge recursionRun:
mkdir -p .no-vibe/notes .no-vibe/refs .no-vibe/data/sessions && touch .no-vibe/active
Verify:
test -f .no-vibe/active
If verified, state: no-vibe is active (.no-vibe/active exists).
Check for in-progress sessions:
grep -rl '"status": "in_progress"' .no-vibe/data/sessions/ 2>/dev/null
If present, read:
~/.no-vibe/profile.md — global learner meta-model (cross-project skill levels, recurring teaching gaps, preferences). See skills/no-vibe/DATA-SCHEMA.md for the contract; ~/.no-vibe/.synth-state.json is bookkeeping only and must NOT be loaded..no-vibe/data/mistakes.json — project-local teaching gapsCalibrate challenge difficulty:
struggling or new: smaller scope, tighter acceptance criteriacomfortable or strong: broader scope, less hand-holdingUse this structure:
Challenge: {title}
{1-3 sentence description}
Acceptance criteria:
- {specific, testable criterion}
- {specific, testable criterion}
Run command:
{exact command to test}Ready? Start coding. Ask for hints anytime, or say "review" when done.
Rules:
After presenting:
.no-vibe/data/sessions/challenge-<slug>.json with mode "skill".When challenge flow is finished:
rm -f .no-vibe/active
Verify:
test ! -f .no-vibe/active
If verified, state: no-vibe is off (.no-vibe/active removed).
.no-vibe/** is the only write-allowed area.