Skill Wiki v0.1.0
rule @community/rule-semantic-structure-over-visual-positioning

Semantic Structure Over Visual Positioning

Structure must be programmatically determinable, not only visually implied:

Skill
@community
Domain
frontend-design
Version
1.0.0
Quality
4.0
Edges
3 out · 0 in
Tokens
221/378/739
$ prime install @community/rule-semantic-structure-over-visual-positioning

Projection

Always in _index.xml · the agent never has to ask for this.

SemanticStructureOverVisualPositioning [rule] v1.0.0

Use semantic HTML (headings, lists, landmarks) to convey structure — never rely solely on visual layout (indentation, font size, color, spacing) to communicate hierarchy or relationships.

Structure must be programmatically determinable, not only visually implied:
- Hierarchy is expressed with headings (<h1>–<h6>), not just larger text.
- Lists are expressed with <ul>/<ol>/<li>, not just visually indented divs.
- Page regions are expressed with <main>, <nav>, <aside>, <section>, not just positioned containers.
- Relationships between form controls and labels use <label for>, not visual proximity.
- Tables use <th scope>, <caption>, not just column-aligned visual cells.

The test: disable CSS entirely. The page must remain comprehensible and correctly structured.

Source

prime-system/examples/frontend-design/primes/compiled/@community/rule-semantic-structure-over-visual-positioning/atom.yaml

Compiled at 2026-05-07