Skip to content

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

Python

style: remove emojis from checkpoint headings

Noah Kim617d45ea6f24
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 07a8cbe..eea6158 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "vibe-wise",
- "version": "0.1.24",
+ "version": "0.1.25",
"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.md
index 11e1c44..f61f8a6 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ You:
Build a reading list I can share with friends, but only I can edit.
Claude:
- | ✦ 🧠 BUILD CHECKPOINT - Who can change a shared list |
+ | ✦ BUILD CHECKPOINT - Who can change a shared list |
| :--- |
| Friends need to read the list without being able to change it. |
| **How would you make sure only the owner can edit?** |
@@ -48,7 +48,7 @@ Claude:
────────────────────────────────────────────────────────────
- ✦ πŸ’¬ DECISION CHECKPOINT - Who can change a shared list
+ ✦ DECISION CHECKPOINT - Who can change a shared list
Proposed: check ownership on the server before allowing a change. This keeps
friends' viewing access separate from editing. Edits must pass through the server.
diff --git a/docs/development.md b/docs/development.md
index 58b176a..068d95e 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -87,7 +87,7 @@ Launch with `claude --plugin-dir /absolute/path/to/vibe-wise`.
the table directly, not in a code fence. Questions may be detailed; don't force
a short length or fixed width. Keep diagrams outside the card. Other callouts
retain the divider, bold title, and spacing. Every title keeps one leading `✦`
- and its full label/icon. Use native pickers for choices, with no trailing
+ and its full label, without emojis. Use native pickers for choices, with no trailing
paragraphs obscuring the point where the learner should respond.
9. **Clarification without steering:** Ask about an unfamiliar concept mid-decision.
Claude should clarify it, correct any misleading framing, and return to one
diff --git a/skills/learn/behavior.md b/skills/learn/behavior.md
index 75b9d08..0ddf328 100644
--- a/skills/learn/behavior.md
+++ b/skills/learn/behavior.md
@@ -72,7 +72,7 @@ Build Checkpoints use a one-column Markdown table as a card, rendered directly
without a code fence. Put the named heading in the header, any needed context in
a body row, and the bold question in its own row:
-| ✦ 🧠 BUILD CHECKPOINT - <description> |
+| ✦ BUILD CHECKPOINT - <description> |
| :--- |
| <Context, when needed> |
| **<Reasoning question>** |
@@ -81,9 +81,9 @@ The question can be as detailed as needed; don't shorten it to fit a fixed width
or word count. Keep diagrams outside the table so they stay readable.
Other callouts use a divider, bold heading, and spacing. Use native AskUserQuestion
for choices (text fallback if unavailable). Reports need no question.
-Headings use `✦ <icon> <TYPE> - <description>` with exact labels:
-`🧠 BUILD CHECKPOINT`, `πŸ’¬ DECISION CHECKPOINT`, `πŸ”Ž SYSTEM CHECK`,
-`πŸ’‘ WHY THIS MATTERS`, `πŸ’‘ IMPLEMENTATION REPORT`.
+Headings use `✦ <TYPE> - <description>` with exact labels:
+`BUILD CHECKPOINT`, `DECISION CHECKPOINT`, `SYSTEM CHECK`,
+`WHY THIS MATTERS`, `IMPLEMENTATION REPORT`.
Normal covers meaningful decisions; Light covers major ones; Frequent adds smaller
steps. Never trigger by time or tool counts. Respect explicit requests for help,