Cursor already writes good HTML: design reviews, UI prototypes, refactor plans and weekly metrics pages. 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 Cursor never sees.
tossithere fixes that. Cursor 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 Cursor reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in the editor and the Cursor CLI.
- Install the CLI and sign in:
npm install -g tossithere
toss login
- Install the tossithere skill. Ask Cursor:
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. Create a project rule in .cursor/rules/tossithere.mdc and paste the instructions into it. Cursor also reads AGENTS.md at the root of the repository, so that works too.
That's it. Cursor now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Cursor for something you'd normally get as a wall of text:
Prototype the new onboarding screens as a single HTML page and publish it for review.
Cursor writes the HTML and publishes it:
toss docs:push onboarding-prototype.html --json
# -> https://tossithere.com/d/onboarding-prototype-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 Cursor to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push onboarding-prototype.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 Cursor fix it
Tell Cursor: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push onboarding-prototype.html --id <docId> --note "what changed"
Every comment arrives with the exact markup it points at, so Cursor 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 Cursor
- Prototypes are where comments pay off most. Reviewers click the exact button or heading they mean, and Cursor gets the markup with the comment.
- Cursor's agent asks before running terminal commands unless you allow them. Add
tossto your allowed commands to publish without a prompt. - Background agents can publish too, so a long task ends with a link instead of a diff to read.