A Claude Code / Codex plugin that helps you learn how to build while AI writes the code.
Python
fix: simplify reasoning guidance to open-ended chat
Noah Kimd9ea00811e8f
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex 156cd10..e184468 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "vibe-wise",- "version": "0.1.37",+ "version": "0.1.38","description": "You build. AI writes. Learn how to build software while Claude writes the code.","author": { "name": "Noah Kim" },"repository": "https://github.com/nykooi1/vibe-wise",diff --git a/README.md b/README.mdindex e9abeec..a3eafb2 100644--- a/README.md+++ b/README.md@@ -189,7 +189,7 @@ are with the stack. Checkpoint frequency—Light, Normal, or Frequent—is separ- “Use fewer checkpoints.”- “Focus on backend architecture.”-- “Show me options, then ask me to explain my choice.”+- “Use multiple-choice questions.”- “Just implement this one.”- “Pause learning.” Resume with `/vibe-wise:learn`.diff --git a/docs/development.md b/docs/development.mdindex 9d98839..1e30517 100644--- a/docs/development.md+++ b/docs/development.md@@ -98,12 +98,7 @@ For a manual walkthrough based on the playground notes app, see theand its full label in sentence case, followed by a colon, without emojis(for example, `✦ Build checkpoint: <description>`). Use native pickers foronboarding and confirmations, with no trailing paragraphs obscuring the response point.- With Open-ended preferences, have the learner propose two approaches: after- comparing them, Claude should ask for the learner's choice and reasoning in chat,- not a picker or its notes field. With requested options or a saved Multiple- choice/Mixed preference, options appear in chat and Claude asks for an explanation- in the learner's own words. A bare option selection shouldn't count as reasoning;- confirmation buttons come after discussion of the approach and rationale.+ Reasoning questions should be open-ended in chat, not in a picker or its notes field.9. **Clarification without steering:** Ask about an unfamiliar concept mid-decision.Claude should clarify it, correct any misleading framing, and return to onequestion about the project's requirements or constraints. It should not replacediff --git a/skills/learn/behavior.md b/skills/learn/behavior.mdindex 04891e0..8a6ea09 100644--- a/skills/learn/behavior.md+++ b/skills/learn/behavior.md@@ -89,15 +89,9 @@ All checkpoints and other callouts use a divider, a bold named heading, and blanlines around the content. Render directly as Markdown, without cards, table borders,or code fences. Keep questions as normal paragraphs; don't shorten them to fit afixed width or word count. Reserve tables for comparisons and proposed additions.-Reasoning belongs in ordinary chat: ask the learner to articulate their approach-and rationale in their own words, then wait. This includes choosing between approaches-they've proposed. A bare option selection or agreement isn't a reasoning answer;-invite their explanation without turning it into an exam. Never collect reasoning-through a picker or its notes field. If requested or preferred, present options in-chat as support, then ask the learner to explain their choice.-Use native AskUserQuestion only for onboarding choices and Design or Implementation-confirmations (text fallback if unavailable). Choosing an approach is still reasoning,-not confirmation; the confirmation buttons come after that discussion.+Ask open-ended reasoning questions in chat and wait for the learner's reply.+Use native AskUserQuestion for onboarding choices and Design or Implementation+confirmations, not reasoning questions (text fallback if unavailable).Reports need no question.Headings use `✦ <Type>: <description>` with exact labels:`Build checkpoint`, `Design checkpoint`, `Implementation checkpoint`, `System check`,diff --git a/skills/learn/onboarding.md b/skills/learn/onboarding.mdindex 2ccfc0d..dfa9a65 100644--- a/skills/learn/onboarding.md+++ b/skills/learn/onboarding.md@@ -53,9 +53,7 @@ Defaults means Normal checkpoints and open-ended reasoning; finish setup immediaCustomize asks frequency (Light / Normal /Frequent), reasoning style (Open-ended / Multiple choice / Mixed), and codingpreference (AI writes / A mix / More hands-on), each in a separate picker. Reasoning-style changes how questions are framed, not how reasoning is collected: even with-options, learners explain their choice in chat. It doesn't change setup pickers.-A longer-term capability goal is optional;+style doesn't change setup pickers. A longer-term capability goal is optional;don't add a separate question if their goal already covers it.If they want to skip setup, use defaults, mark unknown answers Not specified, and