Writing tools · model-cost literacy

HeroChí

Sharpen every word

Give writers immediate text feedback and make token-budget assumptions visible.

  • Source private
  • Live

My role: Product design, browser-based analyzers, interface, and operation.

  • Live product
  • Client-side
  • AI token analytics

At a glance

Problem
Writers and prompt authors need instant text analysis, and nobody wants to paste draft copy into someone else's server.
My contribution
I designed and built twelve local writing tools, including readability analysis and prompt budgeting with explicit token-count assumptions.
Outcome
A live product I operate end to end, with separate input/output budgets and clearly labeled historical cost estimates.
HeroChí homepage: instant, private text analysis tools running entirely in the browser
Product interface. Features on a live deployment can differ from the latest source revision.

Engineering decisions

  1. 01decision

    Keep draft text local

    Readability, word statistics, keyword density, and token analysis run in the browser. These tools do not need a text-processing backend.

  2. 02decision

    Distinguish tokens from words

    Supported OpenAI entries use the explicitly named o200k_base encoder, including whitespace and literal token spellings. Other providers are labeled unvalidated ratio estimates, with no invented accuracy band.

    TradeoffNaming one real encoder and labeling the rest as estimates is less impressive than a universal counter and does not pretend to an accuracy the tool cannot check.

  3. 03decision

    Expose the cost assumptions

    Pasted text, other input context, and an output reservation form a visible budget. Overages remain visible beyond 100%. Costs use an explicitly unverified April 2026 project snapshot; a derived-only report carries the assumptions without exporting the prompt.

What you can verify

Source and release links checked .

Scope and limits

Readability formulas are indicators, not an assessment of a writer's ability. Token and cost estimates have model-specific limits and do not replace a provider's billed usage.

A short walkthrough

  1. 01

    Paste a short draft and inspect its readability and word statistics.

  2. 02

    Compare prose, code, and non-English text in the token counter.

  3. 03

    Reserve other input and output tokens, inspect the context limit, and copy the budget report with its assumptions.

Curious how this is built? Look under the desk.

pocket terminal · ~/desk

A small terminal for this site. It prints only what is on the site; type help for commands.

The prompt needs JavaScript. Every destination is also in the navigation above.

ls work

7 products · * featured

Your turn: try open skillcheck, coffee, or help.

Loading terminal commands…

Type a command and press Enter. Try help, ls, open followed by a project name, why followed by a project name, inspect, trail, cat about, notes, contact, resume, coffee, whoami, or clear. Tab completes; the up and down arrows recall earlier commands. Escape closes the terminal.