rlaope/oh-my-hermes / skills/omh-frontend
omh-frontend
Verified[omh] Building or polishing a web or terminal UI: prepare design-system-driven web and terminal (TUI) UI creation, redesign, polish, accessibility, performance, and visual QA handoffs. Use when the user says: frontend, front-end, front end, frontend skill, in the frontend, on the frontend, to the frontend, web ui.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.1 KB |
| references/chart-styling.md | markdown | 5.5 KB |
| references/component-registry-adoption.md | markdown | 8.7 KB |
| references/design-system-contract.md | markdown | 15.4 KB |
| references/editorial-layout.md | markdown | 6.5 KB |
| references/forms-and-input.md | markdown | 8.5 KB |
| references/mobile-density-gate.md | markdown | 6.5 KB |
| references/reference-token-extraction.md | markdown | 4.1 KB |
| references/rendered-scene-craft.md | markdown | 3.9 KB |
| references/screenshot-loop.md | markdown | 5.8 KB |
| references/scroll-motion-libraries.md | markdown | 7.0 KB |
| references/taste-foundations.md | markdown | 13.1 KB |
| references/tui-craft.md | markdown | 7.2 KB |
| references/web-vitals-budgets.md | markdown | 3.6 KB |
| toolkit/LICENSE.upstream | other | 1.3 KB |
| toolkit/README.md | markdown | 9.5 KB |
| toolkit/examples/phone-clean.html | other | 1012 B |
| toolkit/examples/phone-overflow.html | other | 891 B |
| toolkit/scripts/phone_check.py | script | 28.7 KB |
| toolkit/upstream-manifest.json | config | 3.1 KB |
references/editorial-layout.md
View on GitHub# Editorial Layout
Layout is the part of a page that is decided before colour and type: the
skeleton, the whitespace, the order of attention, where one section ends, and
where images sit. This reference covers those choices only. Palette and type
stay with `references/design-system-contract.md`; the direction itself is named
in `references/taste-foundations.md`.
## Hierarchy before boxes
Build the order of attention from whitespace and type-size contrast first.
Where the chosen direction does not make the box its own language, group
related items with space and thin rules, and keep a filled or bordered box for
an item the reader acts on as a separate object: a page where every group sits
in a box has no group that leads, because the boxes carry the same weight. In
a direction that boxes everything on purpose (`references/taste-foundations.md`
names such directions), hierarchy comes from size, weight and position, because
the boxes carry equal weight.
## The seven axes
Choose one value per axis and write one line of reason, taken from the subject:
what the page shows, how many images it has and at what ratio, and how much
text it carries. The values below are a vocabulary to start from, not a closed
list; a value that fits the subject and is not listed is allowed.
1. **Skeleton / grid** - single column, two-column split, left margin with a
pinned label, asymmetric twelve-column, stacked full-bleed bands, offset
columns.
2. **First screen** - oversized type alone, type beside one large image,
full-bleed image with a text panel, a product capture under one line, an
index of what the page contains.
3. **Section boundary** - thin rule, a change of ground, empty space only, a
label in the margin, a full-width image, a hard edge between bands.
4. **Image placement** - full-bleed, inset with a caption, split against the
text, overlapping a type block, a strip of small frames, one image per
section pinned while text moves.
5. **Signature moment** - one oversized figure, a pull quote, a single
product capture at true size, a timeline, a before and after pair, a large
closing line.
6. **Density** - sparse with one idea per screen, a steady reading column,
mixed with one dense block per section, dense and tabular throughout.
7. **Screen corners and navigation** - what sits at the edges of the screen:
one top bar, an identity label in one corner with the main action in the
opposite one, a floating bar, a side rail, a text-only index, navigation
folded into the first screen. Corner radius is not this axis; it belongs
to the contract's Shapes section.
State the seven values and their reasons in the plan before building. A value
with no reason from the subject is the unmade decision this list exists to
expose.
## Choosing against the familiar
Taking the most familiar value on every axis yields an average page, because
nothing on it came from the subject. As a judgement rule: pick at least two
axes from the less familiar candidates, and write what in the subject earns
each. This is a review prompt, not a quota; a stated reason that the familiar
value fits keeps it.
## Differ from the previous output
A user who receives pages that all share one composition has received one page
several times. Before choosing, read the record of the last few pages built for
this user, and change at least three of the seven axes from the most recent
one. When the user asks for "like last time", follow the record instead.
The record is one line per page with these fields: date, project, and the seven
axis values. Keep it in a file under the project; when there is no project,
keep it under the user's state directory. This reference names the fields and
leaves the path to the project's own conventions. Append the line when the page
is accepted, so a rejected draft does not count as history.
## One frame, varied interiors
Inside one site, pages share the frame: skeleton, navigation and what sits in
the screen corners, section boundary, and theme. They do not share the inner
composition, because a shared frame already makes them one site. Within a page,
consecutive sections of the same kind change composition. Candidates: a
timeline, a mirrored split, one large figure with one line, three small cases,
a step-by-step story. Three sections in a row built from the same card row read
as one section repeated.
## One mode per page
A light page stays light from the first screen to the footer, and a dark page
stays dark. A single section flipped to the other mode reads as a different
page pasted in, unless the flip marks the one signature moment and the plan
says so.
## Static first
Build the page with no motion, hover effect, scroll effect, or shader. Capture
it at the widths that matter and review the still. Add motion only after the
still layout holds on its own, and then sparingly, one effect for one reason.
Motion added early hides weak hierarchy behind movement, and a reviewer cannot
tell which of the two is carrying the page.
## Images
1. Use what exists first: images already in the project and real captures of
the product. Generate an image only when nothing exists for the slot.
2. Lay text over the image in HTML. Never bake text into the image file: baked
text cannot be translated, corrected, or read by a screen reader.
3. Compose the image with the text area left empty, so the overlay does not
fight the subject.
4. Generate at the aspect ratio of the slot. Cropping a generated image to fit
moves the subject out of the composition that was approved.
5. Make the dark variant an edit of the approved light image, changing lighting
and background only, not a new generation. The composition then stays put
when the theme flips.
6. Open each image and look at it before placing it. A file that exists is not
evidence that it shows the right thing.
## Phone width
Multi-column, margin, and split skeletons fold to one column. A label pinned in
a margin returns to the flow, above the content it names. After the fold, run
the mobile density gate in `references/mobile-density-gate.md`; the fold alone
does not show the page holds at phone width.
## Record the choice
Put one comment at the top of the page's stylesheet with the chosen axis
values, in the same order as the record line. The next person to edit the page,
and the next build for this user, can read the decision without reverse
engineering it from the CSS.
## Boundary
This reference shapes the prepared layout and the plan for it. It does not
substitute for observed rendered evidence: the visual-QA owner judges what
shipped, at each width, from a capture.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |