HTML

HTML

HTML is structure only. Semantic. Static. Pre-defined.

Only these elements are allowed

82 elements. Anything not on this list is forbidden.

Document: html, head, body, title, meta, link, script, noscript, template, slot

Layout regions: header, nav, main, aside, footer, article, section, hgroup, address, search

Headings and text: h1, h2, h3, h4, h5, h6, p

Lists: ul, ol, li, dl, dt, dd

Tables: table, thead, tbody, tfoot, tr, th, td, caption, colgroup, col

Forms: form, fieldset, legend, label, input, select, option, optgroup, textarea, output

Media: figure, figcaption, picture, source, img, video, audio, track

Interactive: details, summary, dialog, menu, a

Inline semantic: time, mark, abbr, cite, code, pre, blockquote, q, strong, em, small, sub, sup, br, hr, wbr

Custom elements: Any name containing a hyphen (e.g., app-container, app-logo, app-user, app-legal, app-version, app-banner).

div and span are forbidden

Always. The architecture is div-less and span-less.

Use the semantic element whose main semantic purpose matches the intent. A semantic element is never repurposed for a meaning it does not own. (No <address> standing in for "any contact-shaped block." No <aside> standing in for "anything off to the side.")

If no semantic element's main purpose fits, the design is flawed. Stop. Go to the parent element. Re-engineer the design until a semantic element fits its main purpose. The architecture does not bend. A better design must be found or engineered. This forces quality engineering over quick or convenient fixes and preserves clean, consistent styling for the entire SDLC.

Custom elements are not an escape hatch for "no semantic fits." Custom elements exist in exactly two finite categories:

1. AutoCSS standard layout elements — the curated set authored by AutoCSS: <app-container>, <app-logo>, <app-user>, <app-legal>, <app-version>, <app-banner>. Finite. Part of the architecture's canonical shell. Not extended by ad-hoc additions.
2. Data-table row elements — generated at runtime from JSON keys via toTagName(). Used inside <ul> / <li> for list-rendered tabular content. See the data-flow skill.

Anything outside those two categories is forbidden. If a new shape genuinely needs accommodation, surface it to the user before adding — never invent a new custom element to paper over a design problem.

Only these attributes are permitted on markup elements

• The native attributes defined for that element by the HTML specification (href, src, type, name, value, for, action, method, alt, lang, etc.)
• ARIA attributes (role, aria-*)
• Native state attributes (open, hidden, disabled, required, checked, selected)

Forbidden attributes: class, id, data-*, every on*= event handler attribute (including onclick, oninput, onchange, onsubmit, onkeydown, onkeyup, onmousedown, onmouseup, onmouseover).

There is no JavaScript in HTML markup. Ever. The oninput event used for the CRUD lifecycle is wired in assets/js/oninput.js, not in markup.

style attributes are forbidden. <style> tags are forbidden. CSS lives in .css files only.

The interactive-element pattern

Interactive elements that are not intrinsically interactive (like <button>) use a hidden input inside a <label>. CSS reads the input's checked state via :has() and :checked.

Form actions use checkboxes:

<label role="button" aria-label="Save">
  Save
  <input type="checkbox" aria-hidden="true" />
</label>

Navigation uses radios inside <nav>:

<nav>
  <label>
    <input type="radio" name="nav" aria-hidden="true" />
  </label>
</nav>

The aria-hidden="true" keeps the input out of the accessibility tree; the label carries the accessible name and role. CSS hides the input visually via [aria-hidden="true"] { display: none; }. See references/state-machines.md.

<button> may be used where its native semantics fit. Never substitute a button for the label/input pattern.

Disabled state

Disabled state on interactive elements is conveyed with aria-disabled (assistive-tech aware) and styled by CSS via [aria-disabled="true"]. The native disabled attribute is used only on form controls where the browser-supplied disabled semantic exactly matches the intent.

<label role="button" aria-disabled="true" aria-label="Save">
  Save
  <input type="checkbox" aria-hidden="true" />
</label>

CSS reads via [aria-disabled="true"] and applies the disabled appearance.

The canonical shell

A single index.html at project root. The shell is the same on every page; only the data inside changes.

<app-container>
  <app-banner></app-banner>
  <header>
    <app-logo></app-logo>
    <app-user></app-user>
  </header>
  <nav>
    <label><input type="radio" name="nav" aria-hidden="true"></label>
  </nav>
  <main>
    <article>
      <h1></h1>
      <section></section>
    </article>
  </main>
  <aside></aside>
  <footer>
    <app-legal></app-legal>
    <app-version></app-version>
  </footer>
  <app-banner></app-banner>
</app-container>
<script type="module" src="assets/js/app.js"></script>

<script type="module"> is one tag, outside <app-container>, immediately before </body>.

No layout wrappers. CSS Grid handles every region — see the css skill.

Forms

Forms wrap fields in <fieldset> with a <legend>. Schema and rules come from JSON, not from HTML. See the data-flow skill.

Card pattern

Cards exist only in plural as ul / li. Cards are not identity-bearing on their own. Use <article> only when a card has independent identity (a standalone post, a single product detail page) — not for repeated rows.

Scrollable containers

Only <section>, <ul>, and <ol> are scrollable containers. No other element receives overflow: auto or overflow: scroll.

Custom elements

Custom elements must contain a hyphen (HTML spec requirement). They carry no behavior on their own — they are semantic anchors for layout regions and content slots. JavaScript does not extend them. CSS targets them like any other element.

Generated custom elements (from JSON content) follow the naming rule in the naming skill: toTagName() produces a valid hyphenated tag from a JSON key.

What HTML never does

• No JavaScript anywhere in markup
• No styling decisions
• No state storage outside native attributes (checked, open, selected)
• No layout via wrapper elements
• No content that should come from JSON

Baseline & support

Checked against MDN as of 2026-07-16.

• <search> — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/search
• <dialog> — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/dialog
• <details> / <summary> — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/details
• <output> — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/output
• <slot> — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/slot
• <template> — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/template
• Custom elements (autonomous) — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements
• :has() — Baseline Widely available — https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/:has

Canonical rules: https://github.com/Autocss-com/ai/blob/main/AGENTS.md

References

• references/state-machines.md — checkbox and radio patterns inside labels
• references/shell-layout.md — full Holy Grail markup with regions
• references/forms.md — fieldset, legend, label patterns
• references/custom-elements.md — naming, semantics, no-behavior rule
• HTML element index: https://developer.mozilla.org/en-US/docs/Web/HTML/Element
• ARIA roles: https://www.w3.org/TR/wai-aria-1.2/
• Custom elements: https://html.spec.whatwg.org/multipage/custom-elements.html