Loading
Create or redesign self-contained single-file HTML artifacts with a visual direction shaped by the user's brief, project, and subject. Use when HTML is the deliverable for a report, explainer, landing
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add plannotator/effective-html --skill html -a cursor -y
Create or redesign self-contained single-file HTML artifacts with a visual direction shaped by the user's brief, project, and subject. Use when HTML is the deliverable for a report, explainer, landing page, presentation, tool, mixed artifact, or broad request. This is the collection's only implicit router. Route clear wireframe, prototype, mockup, plan, or diagram requests to the matching direct-invocation specialist when available. Do not use for ordinary application implementation when a standalone HTML file is not the deliverable.
Create or redesign self-contained single-file HTML artifacts with a visual direction shaped by the user's brief, project, and subject. Use when HTML is the deliverable for a report, explainer, landing page, presentation, tool, mixed artifact, or broad request. This is the collection's only implicit router. Route clear wireframe, prototype, mockup, plan, or diagram requests to the matching direct-invocation specialist when available. Do not use for ordinary application implementation when a standalone HTML file is not the deliverable.
Build one self-contained HTML file that makes the subject clearer, easier to use, or easier to understand. The standard is consistent care, not a consistent look. Do not reproduce a house palette, typography stack, card system, or layout from prior runs.
Use the narrowest skill that owns the main review question:
design-artifact with the
chosen workflow when palette, type, composition, theming, or overall visual
register remain open. It provides creative direction; it does not replace the
specialist that owns fidelity, structure, or behavior.html-wireframe when structure, information hierarchy, navigation, or task flow is still unsettled. It should remain visibly low fidelity and may compare two or three layout directions.html-prototype when the user needs a polished mockup or a working interactive flow. A mockup is the static fidelity mode inside that skill.html-plan when the artifact is primarily a plan, roadmap, implementation sequence, or rollout document whose source commitments must remain easy to verify.html-diagram when relationships, sequence, topology, state, hierarchy, or system behavior are the main content.html for reports, explainers, presentations, landing pages, data stories, tools, and mixed artifacts that do not have a clearer owner.These sibling links are the nesting mechanism when the collection is installed together. If a specialized skill is unavailable, continue here and load the closest reference below. Do not make the user install another skill before completing the request.
Inspect the user's request and any material they supplied. When working in a repository, look for its design language in AGENTS.md, CLAUDE.md, design-system documentation, tokens, existing components, and nearby artifacts.
Authority runs in this order:
Before coding, settle five things in working notes:
If the project already answers the visual questions, follow it. Otherwise read
and compose design-artifact when it is
available. If the collection was installed without that sibling skill, read
references/creative-direction.md before
choosing the palette, type, composition, or motion.
references/documents-and-presentations.md.references/interfaces.md.references/diagrams.md.references/charts-and-data.md.Requests can span forms. Read every reference that materially applies, then give the artifact one coherent direction.
.html file with its essential CSS and JavaScript inline. It should work when opened directly, without a build step. Do not require a network connection unless the user permits external dependencies.Write the file to the requested location, or choose a clear filename in the current workspace. When browser tooling is available, open it and inspect a wide and narrow viewport. Exercise its controls, check the console, and fix clipping, overlap, illegible text, broken states, and accidental overflow.
Before delivery, run one originality check: if the subject were swapped for a neighboring topic, would the same visual concept still make just as much sense? If yes, the direction is too generic; revise the composition, type, color, imagery, or interaction so it belongs to this subject.
Return the absolute path and a short description of the artifact's visual and interaction choices.