Claude Code already writes good HTML: implementation plans, specs and PRDs, migration reports and release notes. The hard part is what happens next. A file on your laptop doesn't open properly on a phone, and feedback ends up in a chat thread that Claude Code never sees.
tossithere fixes that. Claude Code runs one command, and the HTML is live at a private link that opens anywhere. People comment on the exact element or sentence they mean, and Claude Code reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in the terminal.
- Install the CLI and sign in:
npm install -g tossithere
toss login- Install the tossithere skill. Ask Claude Code:
Install the tossithere skill from https://tossithere.com/skill.md and use it whenever you make HTML for me.
Prefer to keep it in the repository? Copy the instructions from this page instead. Paste the instructions into CLAUDE.md at the root of your project, or into ~/.claude/CLAUDE.md to have them in every project. If you use skills, save them as .claude/skills/tossithere/SKILL.md instead, and Claude Code loads them only when it publishes.
That's it. Claude Code now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Claude Code for something you'd normally get as a wall of text:
Write me a plan for moving our app to yearly pricing, as an HTML page.
Claude Code writes the HTML and publishes it:
toss docs:push plan.html --json
# -> https://tossithere.com/d/plan-8fa2The page is private to you. Open it on your laptop or your phone.
Share it and collect comments
When someone else should see it, ask Claude Code to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push plan.html --team <slug>Reading needs no account. Commenting takes a Google sign-in, so every comment has a name on it. Reviewers click any element or highlight any text and type.
Let Claude Code fix it
Tell Claude Code: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push plan.html --id <docId> --note "what changed"Every comment arrives with the exact markup it points at, so Claude Code edits the right line instead of guessing. The new version goes to the same link, and older versions stay readable with their own comments.
Tips for Claude Code
- Plan mode and tossithere work well together: ask Claude Code to publish the plan before it writes any code, comment on the steps you disagree with, then let it start.
- Claude Code can publish a folder as well as a file. Point it at a directory with an
index.htmland the CSS, images and data files next to it, and relative links keep working. - If you run several sessions at once, ask each one to publish its result. You get one link per session instead of five terminal tabs to scroll through.
