[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CYKEMCWAEAC9MX19PZ74FV":3,"skill-same:01M7CYKEMCWAEAC9MX19PZ74FV":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CYKEMCWAEAC9MX19PZ74FV","structure",null,"Plan and build the page architecture of an award-level site: the chapter or route map and its pacing, the hero archetype, navigation and menu overlay, preloader slot, pinned stacks, horizontal rails, galleries, archive lists, a designed footer and 404, as semantic HTML with keyboard paths and a responsive plan. Use when the user asks for page structure, sections, 'what sections should this have', wireframes, a landing-page or portfolio layout, a hero that 'needs to feel premium', a nav, menu, footer or 404, scrollytelling structure, or to turn a locked direction into markup. Not for dashboards, admin CRUD, forms-only pages or accessibility fixes without award framing.","BurgiSimon\u002Fawards","BurgiSimon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161694375?v=4","01M7CYH1WGV56EDYJSKHY1FD4G","01M7CYH1X4K1SENVBVXBKH0JHS",0,"MIT","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fstructure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: structure\ndescription: \"Plan and build the page architecture of an award-level site: the chapter or route map and its pacing, the hero archetype, navigation and menu overlay, preloader slot, pinned stacks, horizontal rails, galleries, archive lists, a designed footer and 404, as semantic HTML with keyboard paths and a responsive plan. Use when the user asks for page structure, sections, 'what sections should this have', wireframes, a landing-page or portfolio layout, a hero that 'needs to feel premium', a nav, menu, footer or 404, scrollytelling structure, or to turn a locked direction into markup. Not for dashboards, admin CRUD, forms-only pages or accessibility fixes without award framing.\"\nargument-hint: \"[page | route] [--from AWARDS.md] [--skeleton]\"\nallowed-tools: Bash(node ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002F*), Bash(node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002F*)\n---\n\n# awards:structure — page map and skeleton\n\nCodex: read [the runtime guidance](..\u002F..\u002Freferences\u002Fcodex.md) before following this skill; it maps plugin paths, tool names and handoffs to Codex.\n\nThis skill turns a locked direction into the architecture of the page: a page map with beats and pacing, one hero archetype, the components each chapter needs, a semantic DOM plan, a responsive strategy decided before any component exists, and the static skeleton itself, 404 included. Motion and WebGL come later and must survive on top of what this phase ships.\n\n## Pages are chaptered arguments\n\nWhy: the order hero → logos → features → testimonials → pricing is the first thing a juror recognises, and it recognises it because sections stack while chapters argue. The corpus builds pages as beats with one interruption and an authored close, and it treats pacing as craft: dense earns quiet, and a page that is loud everywhere has no loud moment (`[pattern:narrative-structures#pacing]`).\n\n- Every chapter has an entrance (the moment that arrives), a hold (the part that reads) and an exit (the hand-off).\n- Exactly one interruption per page, after the first content beat, and it changes the input, the scale or the register (`[pattern:narrative-structures#the-interruption]`).\n- The last screen is scored like the first: a designed footer, a conversion in the page's register, a 404 in the same world (`[pattern:narrative-structures#the-close]`).\n- The DOM is the story with CSS off; a Site of the Day's empty DOM cost it 6.60 on accessibility and 6.60 on semantics `[site:igloo]`, a ceiling survived, not a licence.\n\n## Setup\n\nWhy: the durable files are the memory of the build; a skill that starts without them re-asks what is already decided and drifts from the contract.\n\n1. Read `AWARDS.md` in the project root if it exists and resume from its `## Status` checklist; treat every locked block as decided.\n2. Read `DESIGN.md` in the project root if it exists; its tokens are the visual system and are not re-invented here.\n3. If impeccable's `PRODUCT.md` exists, read it for product truth (audience, purpose, voice, constraints) and never overwrite it.\n4. Detect the scope: a whole site, one component (a named element, file or selector), or a critique of existing work.\n5. Detect the stack from `package.json` and framework files (`vite.config.*`, `next.config.*`, `nuxt.config.*`, `astro.config.*`, `svelte.config.*`, a Webflow export); note the motion and GL libraries already installed.\n6. When the request is clearly a whole site and no direction contract exists yet, offer `\u002Fawards:craft` once — it drives every phase in order — then proceed with this skill if the user declines.\n\n## Read before you plan\n\nWhy: the page map, the hero and the components are chosen from pattern files that carry the corpus evidence and the refusals; the recipes carry the markup contracts the motion phase expects.\n\n- The contract's STORY, FIRST VIEWPORT, SIGNATURE, SCROLL MODEL and LOAD & CLOSE blocks, and `DESIGN.md` for the tokens and the type contract (`--from AWARDS.md` is the default whenever the file exists).\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fnarrative-structures.md` before the page map; `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fhero-archetypes.md` before the hero; `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fcomponents-catalog.md` before the component column.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fvisual-composition.md`: open hero, editorial, specification and footer desktop\u002Fmobile frames only where those roles occur in this page map; record chosen mobile order and crop decisions in Notes.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fresponsive-strategy.md` and `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Faccessibility-and-reduced-motion.md` before the DOM plan.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fcraft-floor.md`, the Structure and accessibility and Layout and responsive sections, for the audit rule ids the skeleton is measured against.\n- `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002F_shared\u002Fbase.css` as the base stylesheet the skeleton starts from, and the `index.html` of `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fnav-overlay-fullscreen\u002F`, `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fmarquee-raf-mask\u002F`, `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fsticky-stack-cards\u002F` and `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fhover-preview-list\u002F` for their markup contracts; where a recipe folder does not exist yet, the catalogue entry is the contract.\n- `.awards\u002Fredesign\u002Finventory.md` when `Mode:` reads `redesign`: every row marked keep or rewrite has a home in the page map, and a dropped row is not rebuilt.\n- `${CLAUDE_PLUGIN_ROOT}\u002Fassets\u002Ftemplates\u002F404.html` as the starting point for the 404, and `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Finner-pages.md` for every route behind the home page (case study, detail, article, about, contact, index, not found): its job, its structure and how the world carries in.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fi18n-and-commerce.md` when the brief has a second locale or a shop, and `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fconsent-and-banners.md` when the site sets non-essential cookies: the banner is placed in the page map, not left to a plugin.\n- When the project already has a stack, `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fstacks\u002F\u003Cstack>.md` for where routes and styles live.\n\n## Arguments\n\n- `page` or `route`: which route to structure; the home route by default. In a faceted world each route is its own run of this skill with a shared page map.\n- `--from AWARDS.md`: the default; with no contract, ask one question for the chapters the user already knows they need, then plan from `narrative-structures.md`.\n- `--skeleton`: build the markup from an existing page map without re-planning it.\n\n## Step 1 — the content inventory\n\nWhy: a structure planned for content that does not exist is planned twice; the holds are made of what is actually on hand.\n\nList from `## Brief` and the project: headings and paragraphs that exist; numbers with units; images with alt text; video with posters; 3D assets and their size; PDFs and downloads; what will be authored for the build (labelled synthetic in the brief); what is missing and therefore blocks a chapter. A chapter with nothing to read is cut from the map, not padded.\n\n## Step 2 — the page map\n\nWhy: `AWARDS.md ## Page map` is the one table every later skill reads: motion authors a moment per row, WebGL builds a scene per row that names one, ship checks every row rendered.\n\n- One row per chapter or route with the template's columns: `#`, `Chapter \u002F route`, `Beat (entrance · hold · exit)`, `Layout`, `Components (recipe id: keep · change · pair)`, `Notes`. The beat column comes from STORY; the concept phase may have left the skeleton rows.\n- Layout in the world's words, then its family, axis and image band from `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Flayout-and-composition.md` (`site-office noticeboard (Index rows · left · Accent)`), chosen with its \"Choosing a layout for a chapter\" steps; spans, measure and the phone line go in Notes. Adjacent rows never share a family, no three rows running share an axis or a containment, at least four families on a page of six or more chapters; a split header (wordmark left, links right) only when the thesis needs one, and a giant wordmark close only when the name is the thesis.\n- Rule of three inside a hold: three support points at most.\n- Place the signature in exactly one chapter and the interruption in exactly one, after the first content beat; write which row carries each.\n- Pacing: alternate spectacle and rest; after a scrubbed scene a block that only reads; at most one hero-scale moment per chapter and never in two adjacent chapters; a dense chapter (a spec table, a triptych) is followed by a single line at display scale.\n- Register per chapter in the Notes column (poetic or numeric); the switch only on a chapter boundary; on a big-ticket subject the numbers sit in the second half (`[pattern:narrative-structures#emotion-before-economics]`).\n- The close is a row: the designed footer with the conversion matched to the stakes (`[pattern:copy-and-content#conversion-matched-to-stakes]`). In a faceted world every route is a row authored to the same standard, the 404 included.\n- Notes also carry, per row: the responsive note (what the phone shows), the accessibility need (a key path, a live region, a mirror) and the still the static tier shows.\n\n## Step 3 — the hero archetype\n\nWhy: the hero is the entrance beat of chapter one and the screen the naming test runs on; the archetype follows the narrative model and the dosage the budget allows, never the other way round (`[pattern:hero-archetypes#choosing]`).\n\nChoose one of the thirteen in `[pattern:hero-archetypes#choosing]`: two-state typographic, role-casting boot sequence, poster or video hero, single object with inertia, collage of flat planes, spatial descent, print artefact with an acetate, headline as string, palette field bound to the product, generative line field, wordmark as a window, operable object, the work on screen one. Then:\n- Decide what the first three seconds must say (who, what, why now) and take the lowest dosage that says it; never stack archetypes.\n- Write the composition into row 1's Notes as the archetype's anatomy line describes it: what is where, at what scale, where the primary action sits, what moves once and for how long.\n- The six checks in `[pattern:hero-archetypes#the-first-viewport-test]` run on the rendered hero in Step 7's probe, not on this line.\n- Name the archetype's mobile line and its reduced-motion line in the same row; the archetype's own card signature (its device, object or colour) is the one thing not taken.\n\n## Step 4 — component selection\n\nWhy: a component earns its place by the job it does in the story, not by having been seen on a winning site; the catalogue lists role, anatomy, motion, accessibility, recipe and the literal version refused for each (`[pattern:components-catalog#how-to-read-an-entry]`).\n\nFor every chapter write the components into the `Components (recipe id: keep · change · pair)` column with an id from `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002FREADME.md` or the word `custom`, and the accessibility need in Notes. Available recipes by role:\n\n| Role in the story | Catalogue entries | Recipe ids |\n|---|---|---|\n| Arrival and chrome | authored preloader, fullscreen nav overlay, custom cursor, sound toggle, chapter jump rail, scrollspy index, theme switcher (`[pattern:components-catalog#arrival-and-chrome]`) | `preloader-counter-hold`, `nav-overlay-fullscreen`, `wordmark-header-handoff`, `cursor-two-speed`, `sound-toggle-opt-in`, `theme-swap-tokens`, `dither-cell-transition` when one curtain serves the arrival and every route |\n| Scroll set-pieces | scrubbed hero object or scene, pinned chapter, horizontal rail, sticky stack cards, scroll-drawn path, hold or drag to compare (`[pattern:components-catalog#scroll-set-pieces]`) | `scroll-pin-scrub`, `sticky-stages-rails`, `horizontal-rail`, `sticky-stack-cards`, `scroll-drawn-svg-path`, `compare-hold-drag`, `image-sequence-scrub`, `webcodecs-frame-scrub` |\n| Galleries and lists | draggable plane or arc gallery, hover-preview archive list, poster-scale case blocks, metadata rows, ticker (`[pattern:components-catalog#galleries-and-lists]`) | `gl-dom-tethered-planes`, `hover-preview-list`, `overprint-marker-index`, `marquee-raf-mask`, `split-text-masked-reveal` |\n| Evidence blocks | spec and metric blocks, map cards (`[pattern:components-catalog#evidence-blocks]`) | `product-specification` for product facts and care; otherwise `custom` (numbers as copy in a `\u003Cdl>` or table, never a count-up) |\n| The close | designed footer, designed 404, easter eggs, living-utility pages (`[pattern:components-catalog#the-close-and-beyond]`) | `magnetic-button` for the CTA, `footer-credits-hinge` for a held footer with credits under it, `theme-swap-tokens` when the footer is a theme, `gl-swarm-light-field`, `gl-grade-pass-scene-cuts` or `gl-video-dither-layers` when the close is a GL beat, `page-transitions` for routes, `next-case-handoff` when a case closes on the next |\n\nRules: every component has a job in a row or it is cut; at most two of the six staples (`preloader-counter-hold`, `nav-overlay-fullscreen`, `cursor-two-speed`, `magnetic-button`, `marquee-raf-mask`, `split-text-masked-reveal`) ship at their recipe-default shape, and any further one is reshaped to the world and the change noted in its `DESIGN.md ## Components` entry, since the full kit is what a juror names first; the catalogue's refuse line for each entry is binding (no counter jumps, badge sets, rotated indexes or chapter rails lifted with their values); a marquee is never the hero; a compare needs two conditions; hover previews also appear on focus. Add one entry per chosen component to `DESIGN.md ## Components` with its tokens, states, motion hook and accessibility notes.\n\n## Step 5 — the semantic DOM plan\n\nWhy: a screen reader, a crawler, find-in-page, translation and the `--no-webgl` capture all read the DOM, and the reduced-motion and keyboard paths the references skipped begin here (`[pattern:accessibility-and-reduced-motion#the-improvement-over-the-corpus]`).\n\n- Landmarks: `\u003Cheader>`, one `\u003Cmain>`, `\u003Cnav aria-label>` for each navigation, `\u003Cfooter>`; one `\u003Ch1>` carrying the final claim; an unbroken heading order; every chapter a `\u003Csection aria-labelledby>` with its own heading and real text, so the sequence reads as an article (A01, A03).\n- A skip link as the first focusable element, visible on focus, targeting `\u003Cmain>`; `lang` on `\u003Chtml>`, a viewport meta, `theme-color` and `color-scheme` from the tokens (A09, L03).\n- Real controls: links are `\u003Ca>`, actions are `\u003Cbutton>`; never a click handler on a `div` or `span` (A05); every pointer gesture named in the page map has a keyboard path and a skip (A11, `[pattern:accessibility-and-reduced-motion#keyboard-paths-for-gates]`).\n- The canvas-mirror rule: every canvas slot is `\u003Ccanvas aria-hidden=\"true\">` (or is created by the script) over real `\u003Cimg alt>` elements and real text; a headline that WebGL will draw exists as the real heading in the same place; the `--no-webgl` capture must read as a full page (A04, `[pattern:accessibility-and-reduced-motion#the-dom-mirror]`).\n- `inert`-ready overlay slots: one page wrapper (`\u003Cdiv id=\"page\">` around header, main and footer) so `inert` can be set on it in one attribute; the nav overlay and any dialog are siblings after it at the end of `\u003Cbody>`, as a `\u003Cdialog>` or a `role=\"dialog\"` element with `aria-modal`, hidden until opened; the toggle is a `\u003Cbutton aria-expanded aria-controls>` (`[pattern:accessibility-and-reduced-motion#overlays-and-focus]`).\n- A live region for the preloader: `\u003Cdiv role=\"status\" aria-live=\"polite\" hidden>` with a visible skip `\u003Cbutton>` inside, shown by the script only, so the content is never behind it without JavaScript and it leaves the accessibility tree afterwards (`[pattern:accessibility-and-reduced-motion#preloader-and-live-regions]`); one polite region per page.\n- Focus order equals reading order; `:focus-visible` from the tokens on both grounds; no `outline: none` without a replacement (A06, A07).\n- Lists are `\u003Cul>` or `\u003Col>`; specs and metadata are `\u003Cdl>` or tables; credits are tables; labels that carry meaning are text in the DOM, decorative slashes and rules live in `::before` (`[pattern:typography#labels-as-texture]`).\n- Media: `\u003Cimg>` with alt written as content, `width` and `height`, `loading` (A02, P01); `\u003Cvideo muted playsinline preload=\"metadata\" poster>` with a text alternative or `aria-hidden` when decorative (A10); the poster or the DOM is the largest contentful paint, never the canvas.\n\n## Step 6 — the responsive strategy, decided before build\n\nWhy: a scaling system chosen after the components exist means every measure is rewritten twice, and a phone that gets a shrunken desktop is where winners lose their usability points (`[pattern:responsive-strategy#decide-before-build]`).\n\n- Pick one scaling system and record it in `DESIGN.md ## Layout` and the page map Notes: vw-lock (every desktop measure a fraction of one artboard, fixed pixels below the handoff width) or a fluid `clamp()` from one baseline; never both on one surface; display type stays under 13 vw with a `clamp()` (T03, L01).\n- Apply the coarse-pointer swap list in full (`[pattern:responsive-strategy#coarse-pointer-swaps]`): custom cursor and magnetic pull off; hover previews become a thumbnail in the row or a tap; drag rails become native `overflow-x: auto` with scroll snap and an edge peek; hold gates keep the gate with a larger target; test `any-pointer` as well as `pointer`.\n- Decide dedicated mobile or graceful degrade (`[pattern:responsive-strategy#dedicated-mobile-versus-graceful-degrade]`): dedicated when the phone is the revenue surface or the loud moment can be rebuilt smaller; degrade when the page is a document under an experience layer. Either way the phone gets the same content, headings and links, and a designed still where a scene would be.\n- Never a reload at a breakpoint; scenes rebuild on resize, and breakpoint choreography lives in `gsap.matchMedia()` blocks written by the motion phase (`[pattern:responsive-strategy#never-reload-at-a-breakpoint]`).\n- A side index collapses under about 900 px into a visible nav; rails are native overflow on touch; the same wayfinding exists at both widths (`[pattern:responsive-strategy#navigation-and-rails-on-small-screens]`).\n- Plan for the checks the corpus never documents: 320 px with no horizontal scroll, 200 % zoom, 44 × 44 px targets, a landscape layout instead of a rotate prompt (`[pattern:responsive-strategy#checks]`).\n\n## Step 7 — build the static skeleton\n\nWhy: the skeleton is the layer everything else must survive without; build it as a document first, so the static tier, the crawler and the keyboard user all get the whole page before a single tween exists.\n\n- Files: one `index.html` per route (MPA routing unless the stack notes say otherwise); `src\u002Fstyles\u002Fbase.css` started from `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002F_shared\u002Fbase.css` and importing `src\u002Fstyles\u002Ftokens.css` from `awards:system`; `404.html` (or the stack's 404 route) started from `${CLAUDE_PLUGIN_ROOT}\u002Fassets\u002Ftemplates\u002F404.html` and rewritten in the world: same tokens, same type contract, one small echo of the signature, three routes out, links first in DOM order, lighter than the home page.\n- Every image, video or mesh placed is logged the same minute with `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fassets.mjs\" add --file \u003Cpath> --kind owned|licensed|generated|drawn|placeholder …` (`[pattern:imagery-and-assets#the-asset-log]`), and it follows WORLD's imagery strategy.\n- Content at full fidelity: real headings, numbers with units, alt text written as content; every invented figure, quote or image labelled synthetic in `## Brief`; no lorem, no emoji icons, no \"Get started\" (X01–X03).\n- No JavaScript in this phase beyond the hooks the motion score will read (`data-reveal`, `data-theme`, `data-cursor`, `data-motion`): the overlay ships closed, the preloader ships hidden, and what renders is the static tier.\n- Component markup adapted from the recipes' `index.html`, each with its `keep \u002F change \u002F pair` line in the Page map's Components cell (rename, re-token, drop the demo content) with their accessibility attributes kept; class names by role; every value through `var()` from the tokens; layout by grid and flow; no fixed width above 600 px, no `100vw` (L01, L02).\n- Hero probe first: build the hero on the real tokens and base stylesheet, then `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcapture.mjs\" \u003Cdir> --out .awards\u002Fcaptures\u002Fhero-probe --scroll 0` (a re-probe takes a fresh `hero-probe-2`, never overwrites). Open desktop and mobile `s00` and judge the image against the six first-viewport checks, the archetype's Blueprint in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fhero-archetypes.md` (write in Page map row 1 Notes where the hero departs from it and why), the headline budget in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fcopy-and-content.md#headline-budget` (count the lines at both widths), the `pictures` share in the probe manifest, the `judge` rows of `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fanti-patterns.md#the-slop-scan` a first screen can show, and the selected visual-composition hero frame; then answer the memory test (an object or a behaviour, never an atmosphere). At most one fix batch, recaptured once. A failing naming or memory test goes back to `awards:concept` (a same-seed re-roll is allowed), never to the copy. Record the manifest path in Page map row 1 Notes; with no browser, `hero probe unmeasured` and the reason.\n- Then: landmarks and headings → chapters with their holds → components → footer → 404.\n- Tick \"Page map and skeleton built (structure)\" in `AWARDS.md ## Status`.\n\n## Verify\n\nRead the HTML top to bottom with styles disabled (or as source): it must read as an article with headings, real paragraphs, lists and links, in the page map's order. Then walk it with the keyboard: Tab from the top reaches the skip link, then the nav, then every control in reading order; the overlay toggle and the preloader skip are buttons in the tree. Then run:\n- `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.mjs\" \u003Cdir> --scope a11y,layout,slop` — exit 0, or every finding recorded under `AWARDS.md ## Exceptions` with a reason.\n- `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcapture.mjs\" \u003Cdir> --out \"$capture_out\" --scroll 0,50,100` (fresh `capture_out` per `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fcapture-states.md`) — desktop and mobile captures show the same headings; open each once.\n\n- [ ] Readable with CSS off; keyboard navigation reaches every control in reading order.\n- [ ] Landmarks, one `\u003Ch1>`, unbroken heading order, skip link, `lang`, viewport meta; every chapter a `\u003Csection>` with a heading and real text.\n- [ ] The overlay slot is a dialog after the page wrapper, closed, with a `\u003Cbutton aria-expanded>` toggle; the preloader is a hidden `role=\"status\"` region with a skip button; one polite live region on the page.\n- [ ] Every canvas slot is `aria-hidden` over real `\u003Cimg alt>` and text; nothing exists only in a canvas.\n- [ ] No identical card grid, eyebrow labels, hero-metric row or numbered markers by habit (L04, L05, X07, X08); no template order.\n- [ ] The footer is designed with the conversion in the page's register; the 404 exists, reads in the world and has three routes out.\n- [ ] The responsive strategy is named; 320 px shows no horizontal scroll; the coarse-pointer swaps are planned per component.\n- [ ] Page map row 1 Notes name the hero-probe manifest (or `hero probe unmeasured`) and the probe's fix batch is in.\n- [ ] Every page map row has a beat, a Layout no adjacent row repeats (four or more distinct from six chapters), at least one component id or `custom`, an accessibility need and a static-tier still; the signature and the interruption each live in exactly one row.\n- [ ] `DESIGN.md ## Components` has an entry per chosen component.\n\n## Hand-off\n\nWhen no project boots yet (no `package.json`, or no Lenis + GSAP boot): Invoke the `awards:stack` skill now with the Skill tool, passing the brief and the AWARDS.md path; do not do its work inline. When the stack is already booted: once layout and media exist, run the static checkpoint in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fvisual-composition.md` and, outside quick mode, the first-viewport component jury `awards:craft` describes (`awards:jury \u003Cdir> --component \u003Cfirst-viewport selector>`), or reuse a current one, and record its evidence, or `unmeasured`, in Page map Notes. Then: Invoke the `awards:motion` skill now with the Skill tool, passing the brief and the AWARDS.md path; do not do its work inline. When the user asked only for structure, sections or a skeleton, stop after the verify step and offer the next step in one line. The artefacts the next skill needs are the filled `## Page map`, the skeleton files and `DESIGN.md ## Components`.\n\n## Refuse\n\n- The hero-metric template, eyebrow labels and pills over headings, meaningless section numbering, identical card grids and icon tiles, cards inside cards, repeated \"Not X. A Y.\" slogans, promise words and a dash in every sentence: the slop families the audit catches (L04, L05, X07, X08, X16–X18, X20) and a juror recognises first. The rest of the scan is in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fanti-patterns.md#the-slop-scan`.\n- The features → testimonials → pricing order unless the story earned it; a chapter that exists because the category always has one.\n- A modal by reflex; an overlay hidden with opacity that stays focusable; a menu with no `inert`, trap or Escape.\n- Two hero archetypes stacked; a hero that needs the paragraph to make sense; a card's signature as drawn.\n- A chapter with nothing to read; two interruptions; a gate in front of the content; a marquee as the hero.\n- Canvas-only text or images; a click handler on a `div`; hover-only previews; drag-only galleries.\n- Two scaling systems on one page; a reload at a breakpoint; a rotate-your-device prompt; a mobile version that drops headings, copy or links.\n- The host's default 404; a sitemap dump or a social-icon row as the ending.\n- Content that only appears once JavaScript runs; a preloader element that hides the page without a script.\n- Any card's section order or component lifted with its values, whatever the user's shorthand names.\n","# awards:structure — page map and skeleton\n\nCodex: read [the runtime guidance](..\u002F..\u002Freferences\u002Fcodex.md) before following this skill; it maps plugin paths, tool names and handoffs to Codex.\n\nThis skill turns a locked direction into the architecture of the page: a page map with beats and pacing, one hero archetype, the components each chapter needs, a semantic DOM plan, a responsive strategy decided before any component exists, and the static skeleton itself, 404 included. Motion and WebGL come later and must survive on top of what this phase ships.\n\n## Pages are chaptered arguments\n\nWhy: the order hero → logos → features → testimonials → pricing is the first thing a juror recognises, and it recognises it because sections stack while chapters argue. The corpus builds pages as beats with one interruption and an authored close, and it treats pacing as craft: dense earns quiet, and a page that is loud everywhere has no loud moment (`[pattern:narrative-structures#pacing]`).\n\n- Every chapter has an entrance (the moment that arrives), a hold (the part that reads) and an exit (the hand-off).\n- Exactly one interruption per page, after the first content beat, and it changes the input, the scale or the register (`[pattern:narrative-structures#the-interruption]`).\n- The last screen is scored like the first: a designed footer, a conversion in the page's register, a 404 in the same world (`[pattern:narrative-structures#the-close]`).\n- The DOM is the story with CSS off; a Site of the Day's empty DOM cost it 6.60 on accessibility and 6.60 on semantics `[site:igloo]`, a ceiling survived, not a licence.\n\n## Setup\n\nWhy: the durable files are the memory of the build; a skill that starts without them re-asks what is already decided and drifts from the contract.\n\n1. Read `AWARDS.md` in the project root if it exists and resume from its `## Status` checklist; treat every locked block as decided.\n2. Read `DESIGN.md` in the project root if it exists; its tokens are the visual system and are not re-invented here.\n3. If impeccable's `PRODUCT.md` exists, read it for product truth (audience, purpose, voice, constraints) and never overwrite it.\n4. Detect the scope: a whole site, one component (a named element, file or selector), or a critique of existing work.\n5. Detect the stack from `package.json` and framework files (`vite.config.*`, `next.config.*`, `nuxt.config.*`, `astro.config.*`, `svelte.config.*`, a Webflow export); note the motion and GL libraries already installed.\n6. When the request is clearly a whole site and no direction contract exists yet, offer `\u002Fawards:craft` once — it drives every phase in order — then proceed with this skill if the user declines.\n\n## Read before you plan\n\nWhy: the page map, the hero and the components are chosen from pattern files that carry the corpus evidence and the refusals; the recipes carry the markup contracts the motion phase expects.\n\n- The contract's STORY, FIRST VIEWPORT, SIGNATURE, SCROLL MODEL and LOAD & CLOSE blocks, and `DESIGN.md` for the tokens and the type contract (`--from AWARDS.md` is the default whenever the file exists).\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fnarrative-structures.md` before the page map; `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fhero-archetypes.md` before the hero; `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fcomponents-catalog.md` before the component column.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fvisual-composition.md`: open hero, editorial, specification and footer desktop\u002Fmobile frames only where those roles occur in this page map; record chosen mobile order and crop decisions in Notes.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fresponsive-strategy.md` and `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Faccessibility-and-reduced-motion.md` before the DOM plan.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fcraft-floor.md`, the Structure and accessibility and Layout and responsive sections, for the audit rule ids the skeleton is measured against.\n- `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002F_shared\u002Fbase.css` as the base stylesheet the skeleton starts from, and the `index.html` of `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fnav-overlay-fullscreen\u002F`, `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fmarquee-raf-mask\u002F`, `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fsticky-stack-cards\u002F` and `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002Fhover-preview-list\u002F` for their markup contracts; where a recipe folder does not exist yet, the catalogue entry is the contract.\n- `.awards\u002Fredesign\u002Finventory.md` when `Mode:` reads `redesign`: every row marked keep or rewrite has a home in the page map, and a dropped row is not rebuilt.\n- `${CLAUDE_PLUGIN_ROOT}\u002Fassets\u002Ftemplates\u002F404.html` as the starting point for the 404, and `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Finner-pages.md` for every route behind the home page (case study, detail, article, about, contact, index, not found): its job, its structure and how the world carries in.\n- `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fi18n-and-commerce.md` when the brief has a second locale or a shop, and `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fconsent-and-banners.md` when the site sets non-essential cookies: the banner is placed in the page map, not left to a plugin.\n- When the project already has a stack, `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fstacks\u002F\u003Cstack>.md` for where routes and styles live.\n\n## Arguments\n\n- `page` or `route`: which route to structure; the home route by default. In a faceted world each route is its own run of this skill with a shared page map.\n- `--from AWARDS.md`: the default; with no contract, ask one question for the chapters the user already knows they need, then plan from `narrative-structures.md`.\n- `--skeleton`: build the markup from an existing page map without re-planning it.\n\n## Step 1 — the content inventory\n\nWhy: a structure planned for content that does not exist is planned twice; the holds are made of what is actually on hand.\n\nList from `## Brief` and the project: headings and paragraphs that exist; numbers with units; images with alt text; video with posters; 3D assets and their size; PDFs and downloads; what will be authored for the build (labelled synthetic in the brief); what is missing and therefore blocks a chapter. A chapter with nothing to read is cut from the map, not padded.\n\n## Step 2 — the page map\n\nWhy: `AWARDS.md ## Page map` is the one table every later skill reads: motion authors a moment per row, WebGL builds a scene per row that names one, ship checks every row rendered.\n\n- One row per chapter or route with the template's columns: `#`, `Chapter \u002F route`, `Beat (entrance · hold · exit)`, `Layout`, `Components (recipe id: keep · change · pair)`, `Notes`. The beat column comes from STORY; the concept phase may have left the skeleton rows.\n- Layout in the world's words, then its family, axis and image band from `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Flayout-and-composition.md` (`site-office noticeboard (Index rows · left · Accent)`), chosen with its \"Choosing a layout for a chapter\" steps; spans, measure and the phone line go in Notes. Adjacent rows never share a family, no three rows running share an axis or a containment, at least four families on a page of six or more chapters; a split header (wordmark left, links right) only when the thesis needs one, and a giant wordmark close only when the name is the thesis.\n- Rule of three inside a hold: three support points at most.\n- Place the signature in exactly one chapter and the interruption in exactly one, after the first content beat; write which row carries each.\n- Pacing: alternate spectacle and rest; after a scrubbed scene a block that only reads; at most one hero-scale moment per chapter and never in two adjacent chapters; a dense chapter (a spec table, a triptych) is followed by a single line at display scale.\n- Register per chapter in the Notes column (poetic or numeric); the switch only on a chapter boundary; on a big-ticket subject the numbers sit in the second half (`[pattern:narrative-structures#emotion-before-economics]`).\n- The close is a row: the designed footer with the conversion matched to the stakes (`[pattern:copy-and-content#conversion-matched-to-stakes]`). In a faceted world every route is a row authored to the same standard, the 404 included.\n- Notes also carry, per row: the responsive note (what the phone shows), the accessibility need (a key path, a live region, a mirror) and the still the static tier shows.\n\n## Step 3 — the hero archetype\n\nWhy: the hero is the entrance beat of chapter one and the screen the naming test runs on; the archetype follows the narrative model and the dosage the budget allows, never the other way round (`[pattern:hero-archetypes#choosing]`).\n\nChoose one of the thirteen in `[pattern:hero-archetypes#choosing]`: two-state typographic, role-casting boot sequence, poster or video hero, single object with inertia, collage of flat planes, spatial descent, print artefact with an acetate, headline as string, palette field bound to the product, generative line field, wordmark as a window, operable object, the work on screen one. Then:\n- Decide what the first three seconds must say (who, what, why now) and take the lowest dosage that says it; never stack archetypes.\n- Write the composition into row 1's Notes as the archetype's anatomy line describes it: what is where, at what scale, where the primary action sits, what moves once and for how long.\n- The six checks in `[pattern:hero-archetypes#the-first-viewport-test]` run on the rendered hero in Step 7's probe, not on this line.\n- Name the archetype's mobile line and its reduced-motion line in the same row; the archetype's own card signature (its device, object or colour) is the one thing not taken.\n\n## Step 4 — component selection\n\nWhy: a component earns its place by the job it does in the story, not by having been seen on a winning site; the catalogue lists role, anatomy, motion, accessibility, recipe and the literal version refused for each (`[pattern:components-catalog#how-to-read-an-entry]`).\n\nFor every chapter write the components into the `Components (recipe id: keep · change · pair)` column with an id from `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002FREADME.md` or the word `custom`, and the accessibility need in Notes. Available recipes by role:\n\n| Role in the story | Catalogue entries | Recipe ids |\n|---|---|---|\n| Arrival and chrome | authored preloader, fullscreen nav overlay, custom cursor, sound toggle, chapter jump rail, scrollspy index, theme switcher (`[pattern:components-catalog#arrival-and-chrome]`) | `preloader-counter-hold`, `nav-overlay-fullscreen`, `wordmark-header-handoff`, `cursor-two-speed`, `sound-toggle-opt-in`, `theme-swap-tokens`, `dither-cell-transition` when one curtain serves the arrival and every route |\n| Scroll set-pieces | scrubbed hero object or scene, pinned chapter, horizontal rail, sticky stack cards, scroll-drawn path, hold or drag to compare (`[pattern:components-catalog#scroll-set-pieces]`) | `scroll-pin-scrub`, `sticky-stages-rails`, `horizontal-rail`, `sticky-stack-cards`, `scroll-drawn-svg-path`, `compare-hold-drag`, `image-sequence-scrub`, `webcodecs-frame-scrub` |\n| Galleries and lists | draggable plane or arc gallery, hover-preview archive list, poster-scale case blocks, metadata rows, ticker (`[pattern:components-catalog#galleries-and-lists]`) | `gl-dom-tethered-planes`, `hover-preview-list`, `overprint-marker-index`, `marquee-raf-mask`, `split-text-masked-reveal` |\n| Evidence blocks | spec and metric blocks, map cards (`[pattern:components-catalog#evidence-blocks]`) | `product-specification` for product facts and care; otherwise `custom` (numbers as copy in a `\u003Cdl>` or table, never a count-up) |\n| The close | designed footer, designed 404, easter eggs, living-utility pages (`[pattern:components-catalog#the-close-and-beyond]`) | `magnetic-button` for the CTA, `footer-credits-hinge` for a held footer with credits under it, `theme-swap-tokens` when the footer is a theme, `gl-swarm-light-field`, `gl-grade-pass-scene-cuts` or `gl-video-dither-layers` when the close is a GL beat, `page-transitions` for routes, `next-case-handoff` when a case closes on the next |\n\nRules: every component has a job in a row or it is cut; at most two of the six staples (`preloader-counter-hold`, `nav-overlay-fullscreen`, `cursor-two-speed`, `magnetic-button`, `marquee-raf-mask`, `split-text-masked-reveal`) ship at their recipe-default shape, and any further one is reshaped to the world and the change noted in its `DESIGN.md ## Components` entry, since the full kit is what a juror names first; the catalogue's refuse line for each entry is binding (no counter jumps, badge sets, rotated indexes or chapter rails lifted with their values); a marquee is never the hero; a compare needs two conditions; hover previews also appear on focus. Add one entry per chosen component to `DESIGN.md ## Components` with its tokens, states, motion hook and accessibility notes.\n\n## Step 5 — the semantic DOM plan\n\nWhy: a screen reader, a crawler, find-in-page, translation and the `--no-webgl` capture all read the DOM, and the reduced-motion and keyboard paths the references skipped begin here (`[pattern:accessibility-and-reduced-motion#the-improvement-over-the-corpus]`).\n\n- Landmarks: `\u003Cheader>`, one `\u003Cmain>`, `\u003Cnav aria-label>` for each navigation, `\u003Cfooter>`; one `\u003Ch1>` carrying the final claim; an unbroken heading order; every chapter a `\u003Csection aria-labelledby>` with its own heading and real text, so the sequence reads as an article (A01, A03).\n- A skip link as the first focusable element, visible on focus, targeting `\u003Cmain>`; `lang` on `\u003Chtml>`, a viewport meta, `theme-color` and `color-scheme` from the tokens (A09, L03).\n- Real controls: links are `\u003Ca>`, actions are `\u003Cbutton>`; never a click handler on a `div` or `span` (A05); every pointer gesture named in the page map has a keyboard path and a skip (A11, `[pattern:accessibility-and-reduced-motion#keyboard-paths-for-gates]`).\n- The canvas-mirror rule: every canvas slot is `\u003Ccanvas aria-hidden=\"true\">` (or is created by the script) over real `\u003Cimg alt>` elements and real text; a headline that WebGL will draw exists as the real heading in the same place; the `--no-webgl` capture must read as a full page (A04, `[pattern:accessibility-and-reduced-motion#the-dom-mirror]`).\n- `inert`-ready overlay slots: one page wrapper (`\u003Cdiv id=\"page\">` around header, main and footer) so `inert` can be set on it in one attribute; the nav overlay and any dialog are siblings after it at the end of `\u003Cbody>`, as a `\u003Cdialog>` or a `role=\"dialog\"` element with `aria-modal`, hidden until opened; the toggle is a `\u003Cbutton aria-expanded aria-controls>` (`[pattern:accessibility-and-reduced-motion#overlays-and-focus]`).\n- A live region for the preloader: `\u003Cdiv role=\"status\" aria-live=\"polite\" hidden>` with a visible skip `\u003Cbutton>` inside, shown by the script only, so the content is never behind it without JavaScript and it leaves the accessibility tree afterwards (`[pattern:accessibility-and-reduced-motion#preloader-and-live-regions]`); one polite region per page.\n- Focus order equals reading order; `:focus-visible` from the tokens on both grounds; no `outline: none` without a replacement (A06, A07).\n- Lists are `\u003Cul>` or `\u003Col>`; specs and metadata are `\u003Cdl>` or tables; credits are tables; labels that carry meaning are text in the DOM, decorative slashes and rules live in `::before` (`[pattern:typography#labels-as-texture]`).\n- Media: `\u003Cimg>` with alt written as content, `width` and `height`, `loading` (A02, P01); `\u003Cvideo muted playsinline preload=\"metadata\" poster>` with a text alternative or `aria-hidden` when decorative (A10); the poster or the DOM is the largest contentful paint, never the canvas.\n\n## Step 6 — the responsive strategy, decided before build\n\nWhy: a scaling system chosen after the components exist means every measure is rewritten twice, and a phone that gets a shrunken desktop is where winners lose their usability points (`[pattern:responsive-strategy#decide-before-build]`).\n\n- Pick one scaling system and record it in `DESIGN.md ## Layout` and the page map Notes: vw-lock (every desktop measure a fraction of one artboard, fixed pixels below the handoff width) or a fluid `clamp()` from one baseline; never both on one surface; display type stays under 13 vw with a `clamp()` (T03, L01).\n- Apply the coarse-pointer swap list in full (`[pattern:responsive-strategy#coarse-pointer-swaps]`): custom cursor and magnetic pull off; hover previews become a thumbnail in the row or a tap; drag rails become native `overflow-x: auto` with scroll snap and an edge peek; hold gates keep the gate with a larger target; test `any-pointer` as well as `pointer`.\n- Decide dedicated mobile or graceful degrade (`[pattern:responsive-strategy#dedicated-mobile-versus-graceful-degrade]`): dedicated when the phone is the revenue surface or the loud moment can be rebuilt smaller; degrade when the page is a document under an experience layer. Either way the phone gets the same content, headings and links, and a designed still where a scene would be.\n- Never a reload at a breakpoint; scenes rebuild on resize, and breakpoint choreography lives in `gsap.matchMedia()` blocks written by the motion phase (`[pattern:responsive-strategy#never-reload-at-a-breakpoint]`).\n- A side index collapses under about 900 px into a visible nav; rails are native overflow on touch; the same wayfinding exists at both widths (`[pattern:responsive-strategy#navigation-and-rails-on-small-screens]`).\n- Plan for the checks the corpus never documents: 320 px with no horizontal scroll, 200 % zoom, 44 × 44 px targets, a landscape layout instead of a rotate prompt (`[pattern:responsive-strategy#checks]`).\n\n## Step 7 — build the static skeleton\n\nWhy: the skeleton is the layer everything else must survive without; build it as a document first, so the static tier, the crawler and the keyboard user all get the whole page before a single tween exists.\n\n- Files: one `index.html` per route (MPA routing unless the stack notes say otherwise); `src\u002Fstyles\u002Fbase.css` started from `${CLAUDE_PLUGIN_ROOT}\u002Frecipes\u002F_shared\u002Fbase.css` and importing `src\u002Fstyles\u002Ftokens.css` from `awards:system`; `404.html` (or the stack's 404 route) started from `${CLAUDE_PLUGIN_ROOT}\u002Fassets\u002Ftemplates\u002F404.html` and rewritten in the world: same tokens, same type contract, one small echo of the signature, three routes out, links first in DOM order, lighter than the home page.\n- Every image, video or mesh placed is logged the same minute with `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fassets.mjs\" add --file \u003Cpath> --kind owned|licensed|generated|drawn|placeholder …` (`[pattern:imagery-and-assets#the-asset-log]`), and it follows WORLD's imagery strategy.\n- Content at full fidelity: real headings, numbers with units, alt text written as content; every invented figure, quote or image labelled synthetic in `## Brief`; no lorem, no emoji icons, no \"Get started\" (X01–X03).\n- No JavaScript in this phase beyond the hooks the motion score will read (`data-reveal`, `data-theme`, `data-cursor`, `data-motion`): the overlay ships closed, the preloader ships hidden, and what renders is the static tier.\n- Component markup adapted from the recipes' `index.html`, each with its `keep \u002F change \u002F pair` line in the Page map's Components cell (rename, re-token, drop the demo content) with their accessibility attributes kept; class names by role; every value through `var()` from the tokens; layout by grid and flow; no fixed width above 600 px, no `100vw` (L01, L02).\n- Hero probe first: build the hero on the real tokens and base stylesheet, then `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcapture.mjs\" \u003Cdir> --out .awards\u002Fcaptures\u002Fhero-probe --scroll 0` (a re-probe takes a fresh `hero-probe-2`, never overwrites). Open desktop and mobile `s00` and judge the image against the six first-viewport checks, the archetype's Blueprint in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fhero-archetypes.md` (write in Page map row 1 Notes where the hero departs from it and why), the headline budget in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fcopy-and-content.md#headline-budget` (count the lines at both widths), the `pictures` share in the probe manifest, the `judge` rows of `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fanti-patterns.md#the-slop-scan` a first screen can show, and the selected visual-composition hero frame; then answer the memory test (an object or a behaviour, never an atmosphere). At most one fix batch, recaptured once. A failing naming or memory test goes back to `awards:concept` (a same-seed re-roll is allowed), never to the copy. Record the manifest path in Page map row 1 Notes; with no browser, `hero probe unmeasured` and the reason.\n- Then: landmarks and headings → chapters with their holds → components → footer → 404.\n- Tick \"Page map and skeleton built (structure)\" in `AWARDS.md ## Status`.\n\n## Verify\n\nRead the HTML top to bottom with styles disabled (or as source): it must read as an article with headings, real paragraphs, lists and links, in the page map's order. Then walk it with the keyboard: Tab from the top reaches the skip link, then the nav, then every control in reading order; the overlay toggle and the preloader skip are buttons in the tree. Then run:\n- `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.mjs\" \u003Cdir> --scope a11y,layout,slop` — exit 0, or every finding recorded under `AWARDS.md ## Exceptions` with a reason.\n- `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcapture.mjs\" \u003Cdir> --out \"$capture_out\" --scroll 0,50,100` (fresh `capture_out` per `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fcapture-states.md`) — desktop and mobile captures show the same headings; open each once.\n\n- [ ] Readable with CSS off; keyboard navigation reaches every control in reading order.\n- [ ] Landmarks, one `\u003Ch1>`, unbroken heading order, skip link, `lang`, viewport meta; every chapter a `\u003Csection>` with a heading and real text.\n- [ ] The overlay slot is a dialog after the page wrapper, closed, with a `\u003Cbutton aria-expanded>` toggle; the preloader is a hidden `role=\"status\"` region with a skip button; one polite live region on the page.\n- [ ] Every canvas slot is `aria-hidden` over real `\u003Cimg alt>` and text; nothing exists only in a canvas.\n- [ ] No identical card grid, eyebrow labels, hero-metric row or numbered markers by habit (L04, L05, X07, X08); no template order.\n- [ ] The footer is designed with the conversion in the page's register; the 404 exists, reads in the world and has three routes out.\n- [ ] The responsive strategy is named; 320 px shows no horizontal scroll; the coarse-pointer swaps are planned per component.\n- [ ] Page map row 1 Notes name the hero-probe manifest (or `hero probe unmeasured`) and the probe's fix batch is in.\n- [ ] Every page map row has a beat, a Layout no adjacent row repeats (four or more distinct from six chapters), at least one component id or `custom`, an accessibility need and a static-tier still; the signature and the interruption each live in exactly one row.\n- [ ] `DESIGN.md ## Components` has an entry per chosen component.\n\n## Hand-off\n\nWhen no project boots yet (no `package.json`, or no Lenis + GSAP boot): Invoke the `awards:stack` skill now with the Skill tool, passing the brief and the AWARDS.md path; do not do its work inline. When the stack is already booted: once layout and media exist, run the static checkpoint in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fpatterns\u002Fvisual-composition.md` and, outside quick mode, the first-viewport component jury `awards:craft` describes (`awards:jury \u003Cdir> --component \u003Cfirst-viewport selector>`), or reuse a current one, and record its evidence, or `unmeasured`, in Page map Notes. Then: Invoke the `awards:motion` skill now with the Skill tool, passing the brief and the AWARDS.md path; do not do its work inline. When the user asked only for structure, sections or a skeleton, stop after the verify step and offer the next step in one line. The artefacts the next skill needs are the filled `## Page map`, the skeleton files and `DESIGN.md ## Components`.\n\n## Refuse\n\n- The hero-metric template, eyebrow labels and pills over headings, meaningless section numbering, identical card grids and icon tiles, cards inside cards, repeated \"Not X. A Y.\" slogans, promise words and a dash in every sentence: the slop families the audit catches (L04, L05, X07, X08, X16–X18, X20) and a juror recognises first. The rest of the scan is in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fanti-patterns.md#the-slop-scan`.\n- The features → testimonials → pricing order unless the story earned it; a chapter that exists because the category always has one.\n- A modal by reflex; an overlay hidden with opacity that stays focusable; a menu with no `inert`, trap or Escape.\n- Two hero archetypes stacked; a hero that needs the paragraph to make sense; a card's signature as drawn.\n- A chapter with nothing to read; two interruptions; a gate in front of the content; a marquee as the hero.\n- Canvas-only text or images; a click handler on a `div`; hover-only previews; drag-only galleries.\n- Two scaling systems on one page; a reload at a breakpoint; a rotate-your-device prompt; a mobile version that drops headings, copy or links.\n- The host's default 404; a sitemap dump or a social-icon row as the ending.\n- Content that only appears once JavaScript runs; a preloader element that hides the page without a script.\n- Any card's section order or component lifted with its values, whatever the user's shorthand names.\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash(node ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002F*), Bash(node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002F*)","[page | route] [--from AWARDS.md] [--skeleton]","main","846885b1e4423d1a014fe839b6e8683d3fb2817d","plugins\u002Fawards\u002Fskills\u002Fstructure","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards","https:\u002F\u002Fgithub.com\u002FBurgiSimon","Support me: https:\u002F\u002Fko-fi.com\u002Fchliburgi","2026-10-30 14:43:13",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add BurgiSimon\u002Fawards --skill structure",{"tool":38,"command":39},"bunx","bunx skills add BurgiSimon\u002Fawards --skill structure",{"tool":41,"command":42},"pnpm","pnpm dlx skills add BurgiSimon\u002Fawards --skill structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fstructure\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7CYKW4KZMC7WMWK119X495J","webgl","Build the WebGL layer of an award-level site with Three.js 0.186, OGL, React Three Fiber or Threlte: DOM-tethered image planes, fluid and distortion post-processing, depth-map parallax, scroll-driven camera rigs, render-to-texture transitions, one hero object, particles, the glTF + Draco + KTX2 pipeline, quality tiers, disposal, a DOM mirror and a no-GL fallback. Use when asked for 3D, WebGL, a Three.js or R3F scene, shaders or GLSL, particles, liquid, fluid or distortion effects, a 3D hero or scroll-scrubbed models, and when a canvas site is slow, drifts against the DOM or renders dark. Not for DOM-only motion (awards:motion), charts, or 'make it 3D' with no concept behind it.","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fwebgl\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7CYKNRA0EJSGDQCP3A6351C","system","Turn a direction into the visual system of an award-level site and write DESIGN.md plus tokens.css: a typeface contract, a fluid type scale locked to an artboard, two to four colour tokens under a named strategy, spacing, grid, radius and shadow policy, section themes, easing tokens and themed browser surfaces. Use when the user asks for design tokens, a palette, fonts or typography, 'pick fonts and colours for …', a design system, DESIGN.md, 'make the type feel premium', theme switching, or when an awards build has no DESIGN.md yet. Avoids the reflex faces and generated palettes. Not for Tailwind conversions, Figma hand-offs or styling without award framing.","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fsystem\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7CYK66V4E7PCWK1KQH8GJ7V","stack","Choose, scaffold and boot the technical foundation of a creative-developer site: Vite + vanilla by default, or Next.js, Nuxt, Astro, SvelteKit + Threlte or a Webflow shell. Wires Lenis and GSAP ScrollTrigger on one ticker, lazy-chunks Three.js, self-hosts fonts, picks the page-transition mechanism, the glTF\u002FDraco\u002FKTX2 pipeline, quality tiers and one reduced-motion switch. Use when asked to set up, scaffold or configure a project for smooth scroll, GSAP, Lenis, Three.js, WebGL or page transitions, which framework suits an award-style site, or to add these to an existing Next, Nuxt, Astro, Svelte or Webflow app. Not for CRUD or dashboard scaffolds, nor for authoring animations (awards:motion).","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fstack\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7CYJZ2FSJ69P0JH851PWM3E","ship","Takes an award-level site or component from 'it works' to 'it ships': applies the jury's fixes in one batch, runs the craft-floor audit until every finding is fixed or excepted, captures every viewport and state, checks the performance budgets (JS, GL chunk, images, fonts, LCP, CLS), meta, Open Graph, favicon and 404, and writes the ship report. Use when the user says ship, launch, finalize, polish, QA, 'production-ready', 'check performance or accessibility', 'run the audit', 'take screenshots', or after any awards build or jury round in a project with an AWARDS.md. Not a deploy tool, nor for app screens without award framing.","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7CYJQSS35Z8DMHJQR5QVVWT","research","Turns a reference website into a case-study card in the awards corpus format: concept, palette, type, components, motion parameters, stack evidence, weaknesses, principles and take \u002F don't take, every claim labelled by confidence. Captures with Playwright and inspects source when the site's owner allows it, and records recalled material honestly when not. Use when the user shares a site to learn from, asks 'what makes this site award-winning', 'analyse \u002F deconstruct \u002F break down this site', 'why did this win', 'add this to the references', or pastes a CSSDA, FWA or other award-gallery entry. Not for SEO or content audits, nor for downloading a site's assets.","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7CYJHGC7N9STSRXHJD6YD5Z","motion","Author the motion of an award-level site or component with GSAP 3.15 (ScrollTrigger, SplitText, Flip), Lenis, anime.js 4 or CSS: preloaders on a real load signal, masked reveals, scrubbed pins and sticky stages, velocity effects, cursors, magnetic targets, marquees, page transitions, one easing vocabulary and three reduced-motion tiers. Use when asked to animate, add motion or smooth scroll, build GSAP timelines or scrollytelling, text reveals, transitions, micro-interactions or cursor effects, make a page feel alive, premium or cinematic, or fix motion that feels generic, janky or fade-up-everything. Not for chart animation or the WebGL layer (awards:webgl).","https:\u002F\u002Fgithub.com\u002FBurgiSimon\u002Fawards\u002Fblob\u002Fmain\u002Fplugins\u002Fawards\u002Fskills\u002Fmotion\u002FSKILL.md",[],[]]