Continue already writes good HTML: code explanations, review summaries, onboarding guides and change reports. 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 Continue never sees.
tossithere fixes that. Continue 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 Continue reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in VS Code and JetBrains.
- Install the CLI and sign in:
npm install -g tossithere
toss login
- Install the tossithere skill. Ask Continue:
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 rule file in .continue/rules/, for example .continue/rules/tossithere.md. Continue's agent mode loads the rules in that folder.
That's it. Continue now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Continue for something you'd normally get as a wall of text:
Explain how our caching layer works as an HTML page with diagrams, and publish it for new hires.
Continue writes the HTML and publishes it:
toss docs:push caching-explained.html --json
# -> https://tossithere.com/d/caching-explained-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 Continue to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push caching-explained.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 Continue fix it
Tell Continue: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push caching-explained.html --id <docId> --note "what changed"
Every comment arrives with the exact markup it points at, so Continue 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 Continue
- Continue's agent mode can use the terminal tool, which is all tossithere needs.
- Commit the rule so everyone using Continue on the project publishes the same way.
- Works with whichever models you configure.