What is bloom-visual-planning?

A visual planning method for Bloom, a tool where live React interfaces appear as editable canvas frames. Plans are shown as interactive diagrams or decision tables instead of prose documents.

Use it to compare options, explain how something works, map trade-offs, and iterate on feature or interface decisions in Bloom.

It helps teams see and adjust a plan directly, while exposing unclear choices before design or implementation begins.

bloom-visual-planning — Skill for Claude Code by BloomLabsInc

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add BloomLabsInc/agent-skills --skill bloom-visual-planning

Clone the repo

git clone --depth 1 https://github.com/BloomLabsInc/agent-skills

Made for: Claude Code.

Or install bloom-agent-skills, the plugin that ships this one along with the rest of its 3 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bloomlabsinc/agent-skills/bloom-visual-planning/github.svg)](https://agentmods.dev/skills/bloomlabsinc/agent-skills/bloom-visual-planning)

Your own site

<a href="https://agentmods.dev/skills/bloomlabsinc/agent-skills/bloom-visual-planning"><img src="https://agentmods.dev/badge/skills/bloomlabsinc/agent-skills/bloom-visual-planning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bloomlabsinc/agent-skills/bloom-visual-planning"><img src="https://agentmods.dev/badge/skills/bloomlabsinc/agent-skills/bloom-visual-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 790 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00059	$0.00790
Opus 5.5	$0.00024	$0.00316
Sonnet 5.5	$0.00012	$0.00158
Haiku 4.5	$0.00006	$0.00079

Measured 2mo ago against content hash 3bf5c7a02f84, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bloom-visual-planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/bloom-visual-planning/SKILL.md · 37 lines

How it starts

The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Visual planning — a plan is a frame

The move: don't hand the user a wall of prose — build the plan as a frame. A plan is a TSX live fragment on the Bloom canvas — the same React the app runs — so it can hold a decision matrix with live axes, an animated concept explainer, or a draggable trade-off space. The canvas is the plan editor; there is no second tool and no plan DSL. The user reads by looking, and edits by direct manipulation.

This is a living skill — the archetypes and examples will grow. Treat the examples as starting points, not a fixed menu.

Steps

Align before you draw. Get the decision sharp enough to be worth a frame: what is being chosen, what the options are, what axes actually decide it. If it's fuzzy, interview first (a grilling pass) — a plan frame built on a vague question just renders the vagueness prettily. Done when: you can name the options and the 2–4 axes that separate them.
Pick the archetype that fits the decision, then read its pattern + example in references/visual-planning-patterns.md:
- comparing discrete options → decision matrix (assets/examples/decision-matrix-frame.tsx)
- explaining how something works / a sequence → concept explainer (assets/examples/concept-explainer-frame.tsx)
- exploring a design space with knobs → trade-off space (pattern doc)
Seed the frame. Adapt an example into a new canvas frame with write_files (a @bloom-frame/_new_<name> placeholder — see bloom-mcp). Populate it with the real options and axes, not lorem. Prefer live data (a Convex query via the Bloom SDK) over numbers you typed once and will forget to update. Done when: the frame renders the actual decision, and every option/axis is real.
Iterate visually with the user. Hand them the frame, not a paragraph. Let them re-rank, drag a slider, swap a variant — the frame recomputes, and those edits are the canonical record of the decision. Adjust the frame with edit_files as the conversation moves. Done when: the user has converged on the frame, and it reflects the choice they made.

Read the full file on GitHub · 37 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 37 lines · 59 tokens per session scan A 3bf5c7a02f84

Subscribe to this mod's changes

bloom-visual-planning is a skill published in the GitHub repository BloomLabsInc/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 790 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Design and UX Planning

bloom-visual-planning next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
bloom-visual-planningBloomLabsInc/agent-skills	Skill	2	1mo ago	MIT	A	59	Claude Code
webgl-holographic-foilnexu-io/open-design	Skill	106k	today	Apache-2.0	A	41	Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-design	Skill	106k	today	Apache-2.0	A	53	Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-design	Skill	106k	today	Apache-2.0	A	78	Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codex	Skill	34k	today	MIT	A	52	Codex
glance-canonical-layoutsandroid/skills	Skill	10k	2d ago	Apache-2.0	A	56	Claude Code
accessibilitymicrosoft/hve-core	Skill	1.6k	today	MIT	A	47	Claude Code