Skip to content

A Claude Code / Codex plugin that helps you learn how to build while AI writes the code.

Python

fix: preserve product requirements through platform choices

Noah Kime9039ecc5175
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 88b905f..cb1dfea 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "sensible-vibes",
- "version": "0.1.2",
+ "version": "0.1.3",
"description": "You build. AI writes. Learn how to build software while Claude writes the code.",
"author": { "name": "Noah Kim" },
"repository": "https://github.com/nykooi1/sensible-vibes",
diff --git a/docs/development.md b/docs/development.md
index 531fe84..9c3355f 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -51,7 +51,8 @@ Launch with `claude --plugin-dir /absolute/path/to/sensible-vibes`.
the map, and mastered concepts survive without repeated onboarding. Pause
learning, restart, and confirm it stays paused; invoke Learn to resume.
6. **Guided foundations:** With a beginner profile and a new project, check that
- stack, storage, and deployment remain visible open decisions. Ask what an
+ essential capabilities are established and preserved when selecting a platform;
+ stack, storage, and deployment must remain visible open decisions. Ask what an
unfamiliar term means while answering a checkpoint. Claude should explain it
and return to a manageable reasoning step, not bundle new architecture choices
into an implementation approval. Use different projects to avoid overfitting.
diff --git a/skills/learn/behavior.md b/skills/learn/behavior.md
index 39761b0..5815cf3 100644
--- a/skills/learn/behavior.md
+++ b/skills/learn/behavior.md
@@ -10,7 +10,10 @@ Choose a meaningful engineering decision from the actual project. Match its scop
and difficulty to the learner. Skip routine edits and concepts they've demonstrated;
never schedule checkpoints by time, tool calls, or file counts.
-For a new project, show a short path through its open foundational decisions:
+For a new project, first establish its essential capabilities and data needs.
+Preserve those requirements: a broad platform label doesn't settle architecture
+or justify reducing functionality. Adapt the teaching to the learner, not the
+product's capabilities. Then show a short path through open foundational decisions:
stack, data storage, and deployment. Use requirements to work through these in
dependency order, one learning loop at a time. Don't silently choose a stack or
storage model, or treat a feature requirement as a settled technical decision.