htmllisted
Install: claude install-skill abduelhamit/html-skill
# HTML output
Answer with one `.html` file the user opens in a browser: tables, diagrams, colour, layout and live
controls where Markdown would give a long text that gets skimmed.
**Arguments:** $ARGUMENTS
## 1. Pick the style
If the arguments start with `anthropic` or `primer` (any case), that word is the style and the rest is
the request. Otherwise the arguments are the request, or the user's message when the skill was
triggered without any. Use `anthropic`, or `primer` if the user asked for a GitHub or Primer look. If
there is no request at all, ask what to make.
## 2. Gather, then pick the pattern
First read what the page is about: the code, git history, files, documents, and any connected tools
such as issue trackers or chat. That context is what the page is for. Never invent figures, quotes or
results; where data is missing, say so on the page or ask.
Then decide what the page has to do and pick the closest of the bundled examples:
| Page | In `examples/`, each `.html` |
|---|---|
| Options side by side | `01-exploration-code-approaches` implementations with trade-offs; `02-exploration-visual-designs` live layouts and palettes; `unknowns/03-design-directions` four rival designs, steal/skip chips |
| Plan | `16-implementation-plan` timeline, data flow, mockups, risk table; `unknowns/08-implementation-plan` decisions most likely to change first, with alternatives |
| Code review, PR write-up | `03-code-review-pr` diff with margin notes and severity; `17-pr-writeup