Menú
One-shot escape hatch to temporarily disable no-vibe write guard for a single scoped task, then restore the marker.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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 `~/.no-vibe/PROFILE.md`, `.no-vibe/SUMMARY.md`, and every `*.md` under `~/.no-vibe/user/` and `.no-vibe/user/` before any teaching reply. EVERY reply must begin with the header `[no-vibe] Phase: <0|1a|1b|1c|2|3|4|5|6> · Session: <slug-or-none> · Layer: <n/total-or--> · Next: <action-verb-clause>` and follow the per-turn order: read PROFILE/SUMMARY/user files → read sessions/<slug>.json → emit header → act (chat-only, no project writes) → update session JSON if changed → at layer close, decide whether to update PROFILE.md or SUMMARY.md per the silent-default + NO_CHANGE rule. Full contract in SKILL.md "Turn Response Contract" section.
| name | no-vibe-btw |
| description | One-shot escape hatch to temporarily disable no-vibe write guard for a single scoped task, then restore the marker. |
Temporarily disable no-vibe for one scoped task, perform the task, then restore no-vibe if it was previously active.
Text after $no-vibe-btw is the required task description.
Examples:
$no-vibe-btw add a .gitignore for node$no-vibe-btw scaffold a Makefile with build/test/clean targets$no-vibe-btw fix typo in README.md line 42If task text is missing, stop and tell the user:
$no-vibe-btw requires a task description. Example: $no-vibe-btw add a .gitignore for node.
Run:
was_active=0
[ -f .no-vibe/active ] && was_active=1
Run:
rm -f .no-vibe/active
Verify:
test ! -f .no-vibe/active
If verified, state: temporary btw mode active (.no-vibe/active removed).
Do exactly what the task asks, nothing more.
Scope rules:
Always restore marker if it was active before, even on failure:
if [ "$was_active" = "1" ]; then
mkdir -p .no-vibe && touch .no-vibe/active
fi
Verify:
if [ "$was_active" = "1" ]; then
test -f .no-vibe/active
fi
If verified and was_active=1, state: no-vibe is active again (.no-vibe/active restored).
Give one short summary of files changed and why.
.no-vibe/active when it was previously active..no-vibe/ contents unless task explicitly targets them.$no-vibe off.