Claude Design — Design one-off HTML artifacts (landing, deck, prototype)
Claude Design — Design one-off HTML artifacts (landing, deck, prototype)
Start with meaning, then move to detail.
This lesson explains Claude Design — Design one-off HTML artifacts (landing, deck, prototype) as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When To Use This Skill vs popular-web-designs vs design-md, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Claude Design — Design one-off HTML artifacts (landing, deck, prototype) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Design one-off HTML artifacts (landing, deck, prototype)
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When To Use This Skill vs popular-web-designs vs design-md
Read this after the foundation, then connect it to the previous step.
- 04Runtime Mode
Read this after the foundation, then connect it to the previous step.
- 05Core Identity
Read this after the foundation, then connect it to the previous step.
- 06When To Use
Read this after the foundation, then connect it to the previous step.
- 07Design Principle: Start From Context, Not Vibes
Read this after the foundation, then connect it to the previous step.
- 08Asking Questions
Read this after the foundation, then connect it to the previous step.
- 09Surface-First: Commit to a Composition Before Touching Tokens
Read this after the foundation, then connect it to the previous step.
- 10Workflow
Finish here to verify the result and special cases.
Copy only after you understand the effect.
Created: /path/to/Prototype.html
It includes 3 layout variants, a Tweaks panel for density/theme, and responsive behavior.
Verified: file exists and opened cleanly in browser, no console errors.
Next: pick the strongest direction and I’ll tighten copy + motion.You are running in CLI/API mode, not hosted Claude Design. Ignore references to hosted-only tools or preview panes. Produce complete local design artifacts, usually self-contained HTML with embedded CSS/JS, and verify with available local tools before returning. Preserve the design process: gather context, define the system, produce options, avoid filler, and meet a high visual bar.Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.