Skip to content

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

Python

fix: simplify checkpoint cards and remove padding rows

Noah Kimb10804eeb744
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 5649197..9a9f842 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "vibe-wise",
- "version": "0.1.27",
+ "version": "0.1.28",
"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 9317abf..d8e9804 100644
--- a/README.md
+++ b/README.md
@@ -36,9 +36,17 @@ implementation steps are illustrative; intervening design discussions are omitte
**Claude:**
-| ✦ Build checkpoint: Deleting a shared note |
-| :--- |
-| <br>"Trip ideas" is in both Travel and Summer. Deleting it removes it from both.<br><br>**When someone deletes Travel, what should happen to that note in Summer?**<br><br> |
+```text
+╭────────────────────────────────────────────────────────────────────╮
+│ ✦ Build checkpoint: Deleting a shared note │
+├────────────────────────────────────────────────────────────────────┤
+│ "Trip ideas" is in both Travel and Summer. Deleting it removes it │
+│ from both. │
+├────────────────────────────────────────────────────────────────────┤
+│ When someone deletes Travel, what should happen to that note in │
+│ Summer? │
+╰────────────────────────────────────────────────────────────────────╯
+```
**You:**
@@ -48,9 +56,14 @@ implementation steps are illustrative; intervening design discussions are omitte
That separates deleting a folder from deleting a note.
-| ✦ Build checkpoint: Connecting notes and folders |
-| :--- |
-| <br>**How would you represent which folders a note belongs to, without copying the note?**<br><br> |
+```text
+╭────────────────────────────────────────────────────────────────────╮
+│ ✦ Build checkpoint: Connecting notes and folders │
+├────────────────────────────────────────────────────────────────────┤
+│ How would you represent which folders a note belongs to, without │
+│ copying the note? │
+╰────────────────────────────────────────────────────────────────────╯
+```
**You:**
diff --git a/docs/demos/notion-dupe.md b/docs/demos/notion-dupe.md
index c0781ed..9db783d 100644
--- a/docs/demos/notion-dupe.md
+++ b/docs/demos/notion-dupe.md
@@ -143,9 +143,14 @@ shows Build, Decision, and Implementation checkpoints together.
**Claude:**
-| ✦ Build checkpoint: Password storage |
-| :--- |
-| <br>**What would you store so we can check someone's password when they sign in?**<br><br> |
+```text
+╭────────────────────────────────────────────────────────────────────╮
+│ ✦ Build checkpoint: Password storage │
+├────────────────────────────────────────────────────────────────────┤
+│ What would you store so we can check someone's password when they │
+│ sign in? │
+╰────────────────────────────────────────────────────────────────────╯
+```
**You:**
diff --git a/docs/development.md b/docs/development.md
index 26a0764..62d0345 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -92,8 +92,7 @@ projects and keeps generated conversations outside the repository.
stay explicit; diagrams before reasoning must not silently decide the solution.
Build Checkpoints use a one-column Markdown table: the named title is the header,
context is an optional body row, and the bold question has its own row. Render
- the table directly, not in a code fence, with empty table rows above and below
- the content for spacing. Questions may be detailed; don't force
+ 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 in sentence case, followed by a colon, without emojis
diff --git a/skills/learn/behavior.md b/skills/learn/behavior.md
index 32c6d2d..859a7e4 100644
--- a/skills/learn/behavior.md
+++ b/skills/learn/behavior.md
@@ -85,13 +85,9 @@ a body row, and the bold question in its own row:
| ✦ Build checkpoint: <description> |
| :--- |
-| |
| <Context, when needed> |
| **<Reasoning question>** |
-| |
-Use empty table rows above and below the content for spacing, not blank lines
-that would break the table.
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