No Vibe

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.

mkdir -p ~/.claude/skills/no-vibe
curl -L https://claudskills.com/skills/no-vibe/SKILL.md \
  -o ~/.claude/skills/no-vibe/SKILL.md

@misc{no-vibe-2026,
  author    = {rizukirr},
  title     = {No Vibe [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/no-vibe/}
}