SShogo Learn
← Library

One-prompt build · 2026-10-29

Tool Tax

Paste this into a new Shogo project and watch it build.

Prompt
Build a single-page "tool tax" view for an AI agent's tool list. Dark UI (#0B0B0F background, orange #FB8C00
accent, Inter for text and JetBrains Mono for every number), designed for a 432px-wide phone screen first:
big numbers, one idea per block, no dense tables, no page scrolling — it must fit one phone screen.

The page plays itself once on load, in real time, over about 26 seconds, and then rests on the decision card.
No buttons to press, no input needed, no keyboard. A viewer must be able to watch it start to finish with
their hands off the device.

The story it tells, in four beats:

1. **0–4s — the paste.** A block of real JSON tool schemas types itself in, monospace, ~5 tools, each with a
   name, a description and a parameters object. Header above it: `tools: 5`. Subtitle line at the bottom of
   the frame: "every tool you give an agent is *schemas*", with the word `schemas` in orange.
2. **4–11s — the tax.** The schemas collapse into one big number: the token count of that serialized JSON,
   labelled `tokens per turn`. Then, underneath, the same number multiplied by 40 turns: `tokens per day`.
   Subtitle: "you pay it on *every* turn", with `every` in orange. Label the counter `estimated · JSON
   schemas serialised` so it is clear what is being counted.
3. **11–19s — the same job, one command.** A terminal block types in one line — a single command plus a
   skill file name — and under it the same job's cost: a much smaller `tokens per turn`. Subtitle: "the same
   job, one command and one *skill*", with `skill` in orange.
4. **19–26s — the decision card.** One card, the only thing on screen: the two numbers side by side with
   their ratio ("N× cheaper per turn"), one line of verdict — "Measure the tool list before you declare it
   dead." — and a footer: `5 tools · 2 numbers · 1 turn`.

Count the tokens for real, in the browser, from the schemas actually on screen. Use a real tokenizer bundled
into the page (for example `gpt-tokenizer`'s `encode`), not a hand-typed number: the number on screen must be
the output of that function on that JSON string. Compute both sides the same way so the ratio is honest.

Rules: no invented numbers — every number on screen is computed from the strings on screen; no URLs or
localhost anywhere on screen; no fake browser chrome, no window title bar; no logo; no gradients on text; no
third-party product names or logos anywhere; the only words are the ones described above.
Want it as a guided course with a coach?Agent Team Playbook