Skip to main content
skill CX Codex

html-design-examples — Claude Code skill: examples and setup

The html-design-examples skill uses a gallery of single-file HTML references to shape plans, reports, prototypes, and other materials meant to be read in a browser.

Apache-2.0 ★ 173 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sammcj/agentic-coding --skill html-design-examples -a claude-code
Open on GitHub

What html-design-examples does

The gallery covers different jobs: comparing implementation options, explaining unfamiliar code, laying out a design system, building prototypes, and writing reports. The skill’s workflow is simple: choose a reference that fits the task, read the whole file, then adapt its structure and visual style to the real content. Interactive examples should give users a way to copy their result as JSON or a prompt.

Each reference is a standalone HTML file with its styles and scripts inside, ready to open in a browser without a build step. That format has a trade-off: HTML diffs are noisy, so the README recommends Markdown for documents that need long-term, line-by-line review in a repository. The gallery’s Birchline branding and fixture data are fictional; they should not carry over into a project.

What it helps with

  • compare implementation options on one page
  • map a delivery plan onto a timeline
  • annotate a code review with severity labels and jump links
  • prototype an interaction across linked screens
  • present a status update or incident timeline

Example prompts for the agent

  • Create a single-file HTML implementation plan with milestones, a data-flow diagram, and a risk table.
  • Build a browser-ready project status report showing shipped work, slipped items, and a small chart.
  • Make an interactive feature-flag editor with dependency warnings and a button to copy changed keys.

How to install html-design-examples

1Skills CLI (Vercel)

npx skills add sammcj/agentic-coding --skill html-design-examples -a claude-code

2Manually: put the files in place

~/.claude/skills/html-design-examples/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/html-design-examples/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about html-design-examples

How do I install html-design-examples in Claude Code?

Run npx skills add sammcj/agentic-coding --skill html-design-examples -a claude-code. The skill file is at ~/.claude/skills/html-design-examples/SKILL.md.

What does html-design-examples do?

It provides a gallery of single-file HTML references for tasks such as planning, code review, prototyping, and reporting. The agent can study a relevant example and adapt its structure and styling to the requested deliverable.

When should I use Markdown instead of HTML?

Use Markdown for documents that will stay in a repository and receive line-by-line review over time, since HTML diffs are noisy. Interactive HTML examples include an export action to return the result as JSON or a prompt.

Source text

SKILL.md · Apache-2.0
---
name: html-design-examples
description: Reference gallery of polished single-file HTML artifacts demonstrating effective ways to communicate ideas through HTML. Use when the user wants to explain, showcase, demo, plan, review, or present an idea within an HTML file.
metadata:
  source: Adapted from https://x.com/trq212/status/2052809885763747935
---

# HTML Design Examples

A library of self-contained `.html` files showing how a static HTML artifact can carry more signal than the same content as markdown. Use them as visual and structural references when building an HTML deliverable for a similar task.

## Why HTML, not markdown

The bottleneck is human attention, not what the agent can produce. A 500-line markdown plan goes unread; the same content as one HTML page with diagrams, tables and inline controls gets engaged with. HTML carries tables, SVG, CSS layout, scripts and spatial composition in a single file, opens in any browser, and shares as a URL rather than an attachment. The token and latency cost is real, and worth it for any artifact that needs to be read by a human.

Prefer HTML for human-facing, ephemeral artifacts (specs, plans, reports, writeups, prototypes, throwaway editors). Stay with markdown or source for things that need durable, line-by-line review in a repo (RFCs, ADRs, runbooks) - HTML diffs are noisy.

## How to use this skill

1. Pick the example that most closely matches the user's intent (catalogue below).
2. Read that file in full before writing your own. The reference's style, density, and structure are the point.
3. Match the shared conventions (see "Conventions").
4. Adapt to the user's real content. The examples use a fictional "Birchline" brand and fixture data - do not carry that across.
5. If the artifact is an editor or any interactive surface, end it with a "copy as JSON" or "copy as prompt" button so the user's work flows back into the agent loop.

## Resource catalogue

Files live in `resources/`. Open `resources/index.html` for the rendered gallery with thumbnails.

### Exploration & Planning
- `01-exploration-code-approaches.html` - side-by-side comparison of three implementation approaches with trade-offs called out inline.
- `02-exploration-visual-designs.html` - layout and palette options rendered live for visual comparison.
- `16-implementation-plan.html` - milestones on a timeline, data-flow diagram, inline mockups, risky code, risk table.

### Code Review & Understanding
- `03-code-review-pr.html` - annotated diff with margin notes, severity tags, jump links.
- `17-pr-writeup.html` - author-side PR description with motivation, before/after, file-by-file tour.
- `04-code-understanding.html` - unfamiliar package drawn as boxes and arrows with the hot path highlighted.

### Design
- `05-design-system.html` - colours, type scale, and spacing tokens rendered as copyable swatches.
- `06-component-variants.html` - every size, state, and intent of one component on a single contact sheet.

### Prototyping
- `07-prototype-animation.html` - a transition in isolation with sliders for duration and easing.
- `08-prototype-interaction.html` - four linked screens, enough fidelity to feel the interaction.

### Illustrations & Diagrams
- `10-svg-illustrations.html` - inline SVG figure sheet suitable for a blog post.
- `13-flowchart-diagram.html` - annotated flowchart with click-to-reveal step detail.

### Decks
- `09-slide-deck.html` - arrow-key navigable slides as one HTML file, no build step.

### Research & Learning
- `14-research-feature-explainer.html` - TL;DR, collapsible request-path steps, tabbed config snippets, FAQ.
- `15-research-concept-explainer.html` - interactive demo, comparison table, hover-linked glossary.

### Reports
- `11-status-report.html` - weekly status: what shipped, what slipped, small chart.
- `12-incident-report.html` - post-mortem with minute-by-minute timeline, log excerpts, follow-up checklist.

### Custom Editing Interfaces
- `18-editor-triage-board.html` - drag tickets across Now / Next / Later / Cut, then export the ordering as markdown.
- `19-editor-feature-flags.html` - grouped toggles with dependency warnings and a copy-diff button for changed keys.
- `20-editor-prompt-tuner.html` - editable template with highlighted variable slots; three sample inputs re-render live as you type.

## Conventions across all examples

- One `.html` file, opens directly in a browser. No build, no npm, no CDN scripts, no external stylesheets.
- CSS custom properties at `:root` for the colour palette and font stacks.
- Serif display headings paired with a sans-serif body is the recurring typographic pattern.
- Any interactivity is vanilla JS in a single `<script>` tag.
- Calm, editorial aesthetic: paper tones, restrained accent colour, generous whitespace (But not a narrow column of information. Use the available screen real estate wisely).
- Interactive surfaces export their state - a "copy as JSON" or "copy as prompt" button is the closing affordance.

## Aesthetic consistency

When the user has an existing project with its own design language, generate or reference a single design-system HTML file (see `05-design-system.html` for the shape) and use it as the style anchor for subsequent artifacts. Defer to the project's own brand and tokens rather than copying the gallery's editorial palette wholesale.

## Gotchas

- HTML diffs are noisy. If the artifact will live in a repo and be reviewed line-by-line over time, write markdown instead.
- An editor without an export button is half a tool. Always finish interactive artifacts with a way to get the result back into text.
- If the user wants an arrow-key slide deck specifically, the `html-slides` skill is purpose-built. If they want a configurable explorer with a copy-as-prompt button, the `playground` skill is purpose-built. This skill is for the broader case of any single-file HTML deliverable.

© sammcj · Apache-2.0 · sammcj/agentic-coding

Similar skills

All skills for Frontend and UI →

From the same set73

The whole set →
markedit-tools markedit-tools manages the MarkEdit markdown editor on macOS: installs updates, handles extensions, and edits settings via Claude Code. CX Codex +1 ★ 173repo stars raspberry-pi-pico2 Get guidance on building and debugging Raspberry Pi Pico 2 projects with the Pi Debug Probe. Useful for RP2350, SDK configuration, OpenOCD, and GDB. CX Codex +1 ★ 173repo stars prompt-enhancer prompt-enhancer transforms vague or basic prompts into the form a domain specialist would use. Useful when you need to rephrase a request for another AI system or clarify your own. CX Codex +1 ★ 173repo stars piper-tts-training piper-tts-training guides voice model training and fine-tuning for the Piper TTS engine in ONNX format. Useful for local speech synthesis on Raspberry Pi or Home Assistant. CX Codex +1 ★ 173repo stars step-back step-back — a subagent that checks if your current approach is over-engineered. Analyzes code or design and returns one verdict: continue, simplify, or restart. CX Codex ★ 173repo stars reframe-voice reframe-voice guides long-form thought-leadership writing with an evidence-based perspective. Activates when you explicitly need a deep essay without marketing hype. CX Codex +1 ★ 173repo stars excalidraw-diagrams Builds and edits Excalidraw diagrams using MCP previews or standalone Python generation scripts. CX Codex +1 ★ 173repo stars idrive-backup Inspect and manage iDrive Backup settings on macOS, from exclusion rules to backup paths. The bundled tool saves configuration copies before making changes. CX Codex +1 ★ 173repo stars

Project sponsors

Companies that keep this analytics open