Roo Code already writes good HTML: architect-mode plans, documentation, review reports and test summaries. 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 Roo Code never sees.
tossithere fixes that. Roo 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 Roo Code reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in VS Code.
- Install the CLI and sign in:
npm install -g tossithere
toss login
- Install the tossithere skill. Ask Roo 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 a file in .roo/rules/, for example .roo/rules/tossithere.md. Roo Code loads them for every mode.
That's it. Roo Code now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Roo Code for something you'd normally get as a wall of text:
In Architect mode, design the notifications service and publish the design as a page.
Roo Code writes the HTML and publishes it:
toss docs:push notifications-design.html --json
# -> https://tossithere.com/d/notifications-design-8fa2
The 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 Roo Code to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push notifications-design.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 Roo Code fix it
Tell Roo Code: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push notifications-design.html --id <docId> --note "what changed"
Every comment arrives with the exact markup it points at, so Roo 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 Roo Code
- Architect mode produces plans. Publish them, collect comments, then hand off to Code mode.
- Custom modes can include the publishing step, so a mode always ends with a link.
- Auto-approve
tosscommands if you publish often.