Focused agent skills for creating useful, self-contained HTML artifacts, from low-fidelity wireframes to working interactive prototypes.
A fat artifact carries the working detail: structure, visuals, states, interactions, annotations, and evidence. Fat context gives the agent the source material it needs to understand the real problem: the brief, code, constraints, examples, and accepted decisions. The prompt and skills can stay thin because the context and the artifact do the work.
Note
You can use this repo without installing anything. Treat it as a reference first and an installable skill collection second. Read the patterns, borrow what fits, and ask your agent for the artifact directly. Install a skill only when you want a recurring workflow or shared defaults. Visit Effective HTML Website/Guide for more details.
svg_small.mp4
Render and annotate local HTML with Plannotator.
The repo includes six optional skills for pragmatic visual artifacts.
| Skill | Use it for |
|---|---|
html |
Broad HTML requests, mixed artifacts, reports, explainers, presentations, landing pages, tools, and routing to a specialist |
design-artifact |
Subject-specific creative direction for any HTML artifact without imposing a reusable house style |
html-wireframe |
Low-fidelity layout directions that test content, hierarchy, navigation, flows, and responsive structure |
html-prototype |
Working prototypes with realistic states, interaction, keyboard support, and responsive behavior |
html-plan |
Plans, roadmaps, rollouts, and implementation sequences that preserve source commitments |
html-diagram |
Architecture, sequence, process, state, hierarchy, timeline, and system diagrams |
Install the collection when you want these references available to your agent as reusable workflows:
npx skills add plannotator/effective-htmlList or install individual skills:
npx skills add plannotator/effective-html --list
npx skills add plannotator/effective-html --skill design-artifact
npx skills add plannotator/effective-html --skill html-wireframe
npx skills add plannotator/effective-html --skill html-prototypeInvoke a skill directly:
Use $html-wireframe to explore three responsive layouts for this checkout brief.
Use $html-prototype to make the checkout flow work, including validation, loading, failure, success, keyboard, and mobile states.
Use $design-artifact to follow this product's visual language and $html-diagram to turn the attached architecture brief into an interactive system map.
$html can route a broad request, while $design-artifact can supply creative direction across artifact types. Call a specialist directly when you know the artifact type. Each specialist remains independently usable when invoked directly.
/plugin marketplace add plannotator/effective-html
/plugin install plannotator-effective-html@effective-html
codex plugin marketplace add plannotator/effective-html
codex plugin add plannotator-effective-html@effective-htmlThe skills separate creative freedom from reliability:
- Visual direction comes from the conversation, project, audience, and subject.
design-artifactprovides a reusable design process without prescribing a reusable look.- Wireframes stay intentionally unfinished so reviewers focus on structure.
- Prototypes implement one credible flow and its relevant states.
- Plans preserve source commitments.
- Diagrams choose a visual model and rendering method that fit the relationship being explained.
- Every artifact is responsive, accessible, self-contained, and verified in a browser.
Detailed guidance lives only where it is needed. The broad html skill routes the work, design-artifact supplies optional creative direction, and specialist skills own fidelity and behavior. Each skill remains independently usable.
skills/
├── html/
│ ├── SKILL.md
│ ├── agents/openai.yaml
│ └── references/
├── design-artifact/
├── html-wireframe/
├── html-prototype/
├── html-plan/
└── html-diagram/
examples/
└── release-readiness/
├── brief.md
├── states.md
├── wireframe.html
├── prototype.html
└── screenshots/
site/
├── app/ # Next.js routes
├── content/docs/ # Fumadocs guide
└── public/ # Deployed catalog artifacts
The installable skills and their examples stay at the repository root. The
website is isolated under site/ and deployed from that directory.
This project was inspired by Thariq Shihipar's The unreasonable effectiveness of HTML.
Create a shareable link for an HTML file with tot.
