Academy → Using HermesOfficial documentation · clear explanation

Sketch — Throwaway HTML mockups: 2-3 design variants to compare

Sketch — Throwaway HTML mockups: 2-3 design variants to compare

Beginner12 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Sketch — Throwaway HTML mockups: 2-3 design variants to compare as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

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 hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When NOT to use this, then verify failure modes and version compatibility.

What do you need first?

No prior experience is required; follow the steps on a safe test setup first.

What will you know?

A clear outcome before you read.

  • Understand Sketch — Throwaway HTML mockups: 2-3 design variants to compare 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.
Lesson terms

Short definitions before the details.

Skill
An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Official page description

Throwaway HTML mockups: 2-3 design variants to compare

Topic map

What does the source say, and in what order?

  1. 01
    Skill metadata

    Start here to understand the core idea or structure.

  2. 02
    Reference: full SKILL.md

    Read this after the foundation, then connect it to the previous step.

  3. 03
    When NOT to use this

    Read this after the foundation, then connect it to the previous step.

  4. 04
    If the user has the full GSD system installed

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Core method

    Read this after the foundation, then connect it to the previous step.

  6. 06
    1. Intake (skip if the user already gave you enough)

    Read this after the foundation, then connect it to the previous step.

  7. 07
    2. Variants (2-3, never 1, rarely 4+)

    Read this after the foundation, then connect it to the previous step.

  8. 08
    3. Make them real HTML

    Read this after the foundation, then connect it to the previous step.

  9. 09
    4. Variant README

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Variant: stance name

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

intake → variants → head-to-head → pick winner (or iterate)
sketches/ ├── 001-calm-editorial/ │ ├── index.html │ └── README.md ├── 001-utilitarian-dense/ │ ├── index.html │ └── README.md └── 001-playful-split/ ├── index.html └── README.md
browser_navigate(url="file:///absolute/path/to/sketches/001-calm-editorial/index.html") browser_vision(question="Does this layout look clean and readable? Any visible bugs (overlapping text, unstyled elements, broken images)?")
Try it now

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.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Sketch — Throwaway HTML mockups: 2-3 design variants to compare” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?