feel-the-plan
Answer "how does this work", "what's the plan" or "what did you change" with one offline HTML page (lanes x steps, icons, hover cards, blue questions with a suggested pick) instead of long prose. Use whenever the user asks to diagram, map, sketch, visualise or explain a flow, a feature, an architecture or a build plan, and before building anything multi-step when the user wants to agree the plan first. Built for people who lose the thread in walls of text (ADHD-friendly).
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/byzabay--feel-the-plan)HTML
<a href="/listings/byzabay--feel-the-plan"><img src="/api/listings/byzabay--feel-the-plan/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
git clone https://github.com/byzabay/feel-the-plan ~/.claude/skills/feel-the-plan
Then in Claude Code just ask: "diagram how sign-up works", "map the plan before you build", "show me this as a picture".
Try the example:
python3 ~/.claude/skills/feel-the-plan/examples/build_example.py && open ~/.claude/skills/feel-the-plan/examples/example.html
To save edits from the browser back into the file, run the helper in the folder that holds your pages:
python3 ~/.claude/skills/feel-the-plan/scripts/save_server.py --root .
Without it, Cmd+S downloads an edited copy instead.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 97 lines
- ---
- name: feel-the-plan
- description: Answer "how does this work", "what's the plan" or "what did you change" with one offline HTML page (lanes x steps, icons, hover cards, blue questions with a suggested pick) instead of long prose. Use whenever the user asks to diagram, map, sketch, visualise or explain a flow, a feature, an architecture or a build plan, and before building anything multi-step when the user wants to agree the plan first. Built for people who lose the thread in walls of text (ADHD-friendly).
- ---
- # Feel the plan
- Make one self-contained `.html` page the user opens from disk. The point: the whole shape is visible at a glance, detail appears only on hover, and every decision is small.
- No server, CDN, remote font or network request. Pure Python 3 standard library.
- ## When to use
- - The user asks how something works, what you plan to build, or what changed.
- - A reply would run past about 15 lines, or explains more than 3 steps.
- - Before a multi-step build: draw the plan, get a yes, then write code. A diagram is a proposal until the user approves it.
- ## The layout (always the same, so it's learned once)
- - **Lanes (rows)** = who or what does the work. Each lane has a colour, a big icon tile, a bold name and a five-word line ("API server · runs in the cloud").
- - **Columns** = the steps, left to right: a black numbered header, then a yellow strip with one short made-up example.
- - **Boxes** = an icon, a bold plain-English title, one short line, and status tags. Nothing longer on the box face.
- - **Arrows** = right angles only, no crossings. A short label only where it helps ("on error").
- - **Hover cards** = the detail. Hover a box (tap on a phone) to see its card: facts table, longer text, code paths, a mini flow. Click keeps it open; Esc closes.
- - **Around it**: a legend at the top, a one-line "short answer" box above the diagram, a "How to read it" box under it.
- - **Complex step**: give it its own tab with its own diagram, and link to it from the box's card.
- ## Words
- - Short sentences. Plain English. Define any jargon in five words.
- - No code names on the box face. Put file paths in the hover card ("Code: `api/signup.py`, the 3 checks").
- - **Blue boxes** = open questions. Each has your pick and one line of why. End the page with an "All questions" tab so the user can answer in one line ("1 yes, 2 no, 3 your pick").
- - **Yellow notes** = examples and space for the user's notes. Mark made-up data as made up.
- - **Red text** = what changed since the last version. Never overwrite: save `-v2`, `-v3` and keep the old file.
- ## Status tags
- Use the same four everywhere, so status reads without reading:
- - `live` green tick: working today
- - `off` amber pause: built but switched off
- - `next` red clock: in the next release
- - `idea` grey dashed bulb: not built
- Colour only where it means a status. Everything else is a neutral grey chip ("cloud:Hosted", "device:Your laptop", "app:Admin page").
- ## How to build it
- ```python
- import sys; sys.path.insert(0, "<skill>/scripts")
- import lanes, page, pageedit
- spec = {
- "id": "signup", "title": "What happens when someone signs up",
- "lanes": [{"k": "you", "name": "You", "sub": "the developer", "tone": "you", "icon": "user"}, ...],
- "cols": [{"k": "c1", "lv": "1", "name": "Form sent", "ex": "Sam types an email"}, ...],
- "nodes": [{"id": "form", "lane": "web", "col": "c1", "n": "1", "icon": "file-text",
- "t": "Sign-up form", "b": "Checks the email looks real", "tags": ["live"],
- "detail": page.facts([("What it does", "..."), ("Status", "live")])}, ...],
- "edges": [{"f": "form", "t": "api", "k": "flow", "lbl": "POST"}, ...],
- "opts": {"gut": 150, "tries": 12},
- }
- diagram_html, d = lanes.render(spec) # d.crossings should be 0
- html = page.page(title, comment, stamp, header, legend, nav, sections_html, footer, look="v4")
- pageedit.write_page("plan-v1.html", html)
- ```
- - Worked example: `examples/build_example.py` (a made-up sign-up flow with a sub-flow tab).
- - **Tones**: person, you, ai, app, db, cloud, tools, store, plain, mail, chat, code, code2.
- - **Node kinds**: fix, ai, human, store, sys, gap, todo, note, q, hub, accent, done.
- - **Edge kinds**: flow, email, login, data, move, loop, dash.
- - **Page helpers**: `tabs_nav`, `section` (pass `textonly=True` for list-only tabs), `what` (user story first), `qbox` (blue question), `note_box` (yellow), `facts`, `miniflow`, `go` (link to a sub-flow tab), `prompt_block` (show a prompt formatted, never raw markdown).
- - **Icons**: lucide line icons, names in `page.ICON_NAMES`. Use what the thing is (user, monitor, cloud, brain, database, wrench), never brand logos. Add an icon with `scripts/build_sprite.py`.
- - If a label doesn't fit or a crossing remains: widen `opts.gut` (e.g. 150) or drop the label. Keep `row_gap` at 40 or more.
- ## Look rules
- - Text at least 20px. Weights 400, 500 and 600 only.
- - Sentence case. No uppercase labels, no emoji or text symbols as icons.
- - One accent colour. Three text greys. A 4px spacing grid.
- - Light/dark toggle on every page.
- - Motion names what moves, one easing curve, respects reduced-motion.
- - Every tab leads with a diagram, except list-only tabs (questions).
- ## Edit in place
- Every v4 page has an "Edit page" button. The user clicks any text to change or delete it; Cmd+S saves into the file and keeps `<file>.bak`. Saving needs `python3 scripts/save_server.py --root <folder>` running; without it the page downloads an edited copy.
- `pageedit.write_page()` refuses to overwrite a page the user edited in the browser. Read their edits first (diff the file), fold them into your spec, then rebuild with `FORCE=1`.
- ## Check it mechanically, then hand over
- Run `python3 scripts/verify.py <file>`. It checks: balanced HTML and SVG, unique IDs, every arrow's ends exist, no box overlaps or crossings, the 20px floor, no network calls, every tab has a diagram.
- Don't open a browser or take screenshots to judge the look unless the user says so. Whether it looks right is their call.
- Hand over with: the file path, what changed (and what's red), and the questions the user needs to answer.
README.md · README · 81 lines
- # feel-the-plan
- A Claude Code skill that turns "explain this to me" into **one picture you can take in at a glance**, instead of a wall of text.
- Built for people with ADHD (and anyone else) who build software with Claude and lose the thread in long replies.
- **[See a live example](https://byzabay.github.io/feel-the-plan/)**: a made-up "user signs up" flow. Hover or tap any box.
- ## The problem it solves
- You ask Claude how a feature works, or what it plans to build. You get 60 lines of prose. By line 20 you've lost where you were. You skim, approve something you didn't fully read, and the build drifts.
- This skill makes Claude answer with a single offline HTML page instead:
- - **Lanes (rows)** = who or what does the work: you, the browser, the API, the database, the AI model.
- - **Columns** = the steps, left to right, each with one short example.
- - **Boxes** = one bold title and one short line. Detail hides in a card you see on hover (or tap on a phone).
- - **Status at a glance**: icons and colours for live, built but off, next, and just an idea.
- - **Questions in blue boxes**, each with Claude's suggested answer, so you decide in seconds.
- - **Yellow notes** for examples. **Red text** marks what changed since the last version.
- - **Edit in place**: click "Edit page", type over anything, Cmd+S saves it back into the file.
- One page. One glance for the shape. Hover only where you care.
- ## Why this helps an ADHD brain
- - **Less to hold in your head.** The whole flow is on screen at once, so working memory isn't doing the layout.
- - **Detail on demand.** Nothing competes for attention until you point at it.
- - **Same layout every time.** Lanes, then steps, then boxes. You learn to read it once.
- - **Decisions are small.** Each question already has a pick; you say yes or change it.
- - **Spot the change fast.** Version 2 shows edits in red, so you don't reread everything.
- It is a working style, not medical advice.
- ## What's in the box
- ```
- SKILL.md the instructions Claude follows
- scripts/lanes.py lanes × steps diagram with right-angle arrows that never cross
- scripts/page.py page chrome: tabs, legend, notes, hover cards, light/dark toggle
- scripts/pageedit.py "Edit page" mode and Cmd+S save
- scripts/save_server.py tiny local helper that saves edits back into the file (optional)
- scripts/verify.py mechanical checks: valid HTML, no crossings, 20px text floor, no network calls
- scripts/build_sprite.py rebuilds the icon set from lucide
- examples/build_example.py a made-up "user signs up" flow
- ```
- Pure Python 3 standard library. No server, CDN, font download or network call in the pages. Open them straight from disk.
- ## Install
- ```bash
- git clone https://github.com/byzabay/feel-the-plan ~/.claude/skills/feel-the-plan
- ```
- Then in Claude Code just ask: "diagram how sign-up works", "map the plan before you build", "show me this as a picture".
- Try the example:
- ```bash
- python3 ~/.claude/skills/feel-the-plan/examples/build_example.py && open ~/.claude/skills/feel-the-plan/examples/example.html
- ```
- To save edits from the browser back into the file, run the helper in the folder that holds your pages:
- ```bash
- python3 ~/.claude/skills/feel-the-plan/scripts/save_server.py --root .
- ```
- Without it, Cmd+S downloads an edited copy instead.
- ## Tips for working with Claude this way
- - Ask for the picture **before** the build: "diagram the plan first, don't write code until I say go".
- - Answer the blue questions in one line: "1 yes, 2 no, 3 your pick".
- - Ask for "v2" when you change your mind. The old version stays; changes show in red.
- - Keep the hover cards for detail. If a box needs a paragraph on its face, the step is too big: split it.
- ## Licence
- MIT, see [LICENSE](LICENSE). Icons are from [Lucide](https://lucide.dev) (ISC), see [NOTICE](NOTICE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.