Kiro already writes good HTML: specs, design documents, task lists and requirements reviews. 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 Kiro never sees.
tossithere fixes that. Kiro 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 Kiro reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in Kiro's agent and specs.
- Install the CLI and sign in:
npm install -g tossithere
toss login
- Install the tossithere skill. Ask Kiro:
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 steering file at .kiro/steering/tossithere.md and paste the instructions into it. Kiro includes steering files in its agent's context.
That's it. Kiro now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask Kiro for something you'd normally get as a wall of text:
Publish the requirements and design for the export feature as a page so the team can review them.
Kiro writes the HTML and publishes it:
toss docs:push export-spec.html --json
# -> https://tossithere.com/d/export-spec-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 Kiro to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push export-spec.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 Kiro fix it
Tell Kiro: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push export-spec.html --id <docId> --note "what changed"
Every comment arrives with the exact markup it points at, so Kiro 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 Kiro
- Kiro's specs are made for review. Publishing them gives people outside the IDE a way to comment on each requirement.
- Agent hooks can publish automatically, for example whenever a spec changes.
- Use the same doc id for a spec so every revision lives on one link.