AGENT SKILL

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.

License 许可
MIT
所属仓库
BurgiSimon/awards
最近更新
2026-10-30
Stars
★ 0
Forks
0

01 前言 Front Matter

name
ship
description
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.
allowed-tools
Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/*), Bash(node "${CLAUDE_PLUGIN_ROOT}/scripts/*), Bash(npm run build), Bash(gzip -c *), Bash(git diff*), Bash(git status*)
argument-hint
[path | url] [--fix] [--report-only] [--states <json-file>]

03 SKILL.md 正文

awards:ship — fix, prove, report

Codex: read the runtime guidance before following this skill; it maps plugin paths, tool names and handoffs to Codex.

The jury judges; this skill fixes and proves. A ship pass ends with evidence a stranger could check: an audit at zero, manifest-derived valid captures, measured budgets and a report. It never redesigns, because a fix that needs a new idea is a concept problem and goes back to awards:craft.

Arguments: $ARGUMENTS

  • a path (the project directory or its built dist/) or a URL; with nothing given, the project root and its build output
  • --fix — apply the jury's fix batch and the audit fixes (the default whenever a jury report exists)
  • --report-only — prove without changing site source: audit, captures, budgets, checks, report; throughout this skill, list fixes without applying them
  • --states <json-file> — interaction plan to replay; otherwise reuse the recorded plan or .awards/capture-states.json when present

Setup

Read AWARDS.md and DESIGN.md in the project root when they exist; ## Status in AWARDS.md says which phases are done, so resume from there instead of restarting. Read impeccable's PRODUCT.md for product truth when it exists and never overwrite it. Detect the scope (a whole site, one component named by file or selector, or a critique of something that already exists) and the stack (framework, animation and 3D libraries, build tool) from package.json, lockfiles and the entry files. When the request is clearly a whole site and no direction contract exists yet, offer /awards:craft once, then proceed with this skill.

Also read ${CLAUDE_PLUGIN_ROOT}/references/craft-floor.md before touching any file: it is the list of what a Developer Award jury checks in the first minute, and every rule id below points into it. When the request is "ship" or "finalize" and no .awards/jury/<date>.md exists yet, the fix list is missing: invoke the awards:jury skill now with the Skill tool, passing the brief, AWARDS.md path, and exact recorded captures directory and manifest path when available; do not do its work inline. When the request is only the audit, run section 2 once and report findings without edits. When it is only screenshots, run section 3 and report the capture paths/errors without fixes or a jury round. Only a full ship/finalize request runs all sections.

Before a build or browser capture, run node "${CLAUDE_PLUGIN_ROOT}/scripts/doctor.mjs" <project-dir> --json if this environment has not been checked since setup changed. Follow ${CLAUDE_PLUGIN_ROOT}/references/capture-states.md for failures; a static-audit-only request needs no browser preflight.

How a pass runs

  1. Fix batch from the jury list (section 1), applied once.
  2. Audit until clean or excepted (section 2).
  3. Build, capture, open every frame (section 3).
  4. Budgets measured from the build (section 4).
  5. Accessibility and usability verified against the build (section 5).
  6. Meta, chrome and browser surfaces (sections 6 and 7).
  7. Cleanup (section 8), then the report and the hand-off (section 9).

1. The fix batch

Why: fixes applied one at a time, each followed by a capture, turn a ship pass into a week; fixes invented here, outside the jury list, drift the build away from its contract. The batch comes strictly from the latest jury report, is classified so each fix lands at the right level, and is applied once before a single recapture.

Read both lists under ## Material fixes (floor and craft) and ## Keep from the latest .awards/jury/<date>.md. The Keep line is a constraint on every fix: nothing in the batch may dilute what it names. Classify each fix before touching code:

Class What it means Where the fix goes
token the wrong value lives in tokens.css or DESIGN.md: a contrast pair, a display size, a spacing step at the token, never per instance, so it propagates
one-off one element in one file: a missing alt, a hover-only affordance, a stray second accent on one section that element
conceptual resolving it would change the THESIS, the SIGNATURE or the WORLD not a ship fix; record it as deferred — conceptual and hand it back through awards:craft
local a component's internal states or motion: a focus trap, arrow keys on a rail, the reduced-motion tier of one moment inside the component and its tokens
  • Apply every token, one-off and local fix in one batch, floor list first, then the craft list, each in the jury's order. A craft fix stays inside the contract; one that needs a new idea is conceptual.
  • Keep each change as small as the fix demands; the jury named a location and a change, not a rewrite.
  • Recapture once after the batch (section 3), not after each fix.
  • A fix that turns out to need a decision the jury did not make (a new colour, a new moment) stops the batch for that item: reclassify it as conceptual and move on.
  • Log every fix in the report’s table with its location, change, expected visible result, viewport/state, before/after evidence and resolved | partial | unresolved; retain its class. A failed contract block absent from the jury batch remains unresolved, so the site cannot be marked shipped.

With --report-only, list the fixes and their classes in the report without applying them.

2. The deterministic audit

Why: the audit measures the part of the craft floor that a script can measure, so the jury can spend its attention on what a script cannot. It is repeatable, which is what makes "the audit is clean" a claim rather than a mood.

node "${CLAUDE_PLUGIN_ROOT}/scripts/audit.mjs" <dir> --json
  • Run it against the project directory. It is static and needs source; add --render whenever Playwright is available, because stuck entrances (L06), line length (L07), text touching the phone edge (L08), blank viewports (L09), lopsided tablet and phone sections (L10), flat hierarchy (T08), nested cards (X20) and layout shift during load (P08) exist only in a rendered page; with a build output present it renders that, not the source. Without a browser, write rendered checks: unmeasured in the report.
  • The slop rules (X01–X21, with L04, L05, T07 and C04) have earned versions, listed in ## The slop scan of ${CLAUDE_PLUGIN_ROOT}/references/anti-patterns.md. A finding that matches its earned version is excepted with that reason, such as X13 — the logo squashes because it is a character. A habit is fixed. Exit 2 means P0 or P1 findings remain; exit 0 means none. The findings land in .awards/audit.json with rule, severity, file, line, message and fix.
  • Every finding is either fixed or recorded. A recorded finding is one line under AWARDS.md ## Exceptions, scoped to where it is earned (RULE@path or RULE@viewport matches findings whose file or viewport label contains it; a bare id accepts the rule everywhere, so scope C01, A16 and L06 always), or an inline comment next to the code: audit-ignore-next-line for one line, audit-ignore for the whole file:
## Exceptions
C02 — pure black is diegetic: the whole site is a night-vision console
C01@src/sections/credits.html — the end credits are set at 3:1 over the film still, read once and skipped
L10@mobile — the specimen column keeps to the left edge on a phone, as the printed specimen does

<!-- audit-ignore-next-line: L01 the poster frame is a fixed 1200px print artefact by design -->
  • The reason is one a juror would accept; C02 — looks better is not a reason.
  • P0 findings (M01, no reduced-motion branch; L03, no viewport meta) are never excepted. P3 surface findings (S01–S06) are fixed rather than excepted, because they are cheap and jurors notice them.
  • Run node "${CLAUDE_PLUGIN_ROOT}/scripts/assets.mjs" check dist (or the project when there is no build): every shipped image, video and mesh has an entry in .awards/assets.json with its source and licence or its generation record, and no placeholder ships unlabelled (references/patterns/imagery-and-assets.md). Licences that ask for credit get a visible credit (assets.mjs credits).
  • Re-run until the exit code is 0 and every remaining P2 or P3 is fixed or excepted. Name the rules by id in the report, with counts per severity and the exception count.
  • The PostToolUse hook already reported quick findings while files were edited; this full run is the one that counts, because it sees the whole project and the build output.

3. Captures and their validity

Why: the jury and the user judge from these frames, and a stale or broken capture proves nothing. Capture the built output when a build exists, because preloads, hashed chunks and budgets only exist there.

npm run build
capture_out=".awards/captures/$(date -u +%Y%m%dT%H%M%S)-ship"
node "${CLAUDE_PLUGIN_ROOT}/scripts/capture.mjs" dist --out "$capture_out" --scroll 0,50,100 --mobile --reduced-motion --walk --json

Use a fresh timestamp-plus-stage directory for every pass, including verdict/component/fallback recaptures, as in ${CLAUDE_PLUGIN_ROOT}/references/capture-states.md; if the name exists, allocate again. A recapture after a fix batch adds --baseline <the jury round's capture_out>, so the manifest's diff[] shows which frames the batch changed. Add scroll positions for uncovered Page map chapters; gaps stay unmeasured until a fresh capture covers them. For static HTML with no build script, capture the source directory directly. For a component, add --selector "<selector>" --hover "<selector>". Add --states <json-file> for the recorded interaction plan; use ${CLAUDE_PLUGIN_ROOT}/references/capture-states.md to create one for required menu, focus, drag or persistence states. Inspect each named frame and its manifest entry; a failed action is missing evidence, even when baseline frames passed. When the target is a URL with no local source, capture the URL and use audit.mjs <url> --render for rendered checks. Mark the static-source audit and build budgets unmeasured unless the served assets were actually fetched and inspected.

Then open each required manifest-listed image with an image-viewing tool and check:

  • Every applicable Page map chapter has a manifest-listed frame at the relevant desktop/mobile positions, including mobile middle and close; reduced-motion sections and required named states are covered. Open each applicable frame; the familiar s00/s50/s100 names still count where present. None is blank, flat or stuck, and distinct scroll states differ.
  • Every required reduced-motion frame is fully readable at rest: no line left translated, masked or at opacity 0.
  • Mobile opening, middle and close show a designed phone layout with reachable navigation, not a shrunken desktop; the tablet frames (834 × 1194) show a layout chosen for that width, not a stretched phone or a squeezed desktop.
  • <viewport>-aria.yml names every landmark, heading and control the frames show; a canvas chapter whose words are missing from it has no DOM mirror.
  • The recorded $capture_out/manifest.json: consoleErrors, pageErrors and failedRequests are empty; metrics carries the CLS number for section 4, says whether WebGL initialised, and reports lcpColdSynthetic, which is not a field LCP — see the performance table.

An invalid capture is a bug to fix now, followed by a recapture; the report never lists a capture that was not opened.

4. Performance budgets

Why: a 100 % canvas Site of the Day shipped its whole 3D app at under half a megabyte gzipped [site:igloo], and the developer jury docks every heavy asset it can see in the network panel. INP and CLS, the two field metrics the motion layer decides, have their causes and fixes in ${CLAUDE_PLUGIN_ROOT}/references/patterns/performance-cwv.md. Budgets are measured from the build output, gzipped, never from source sizes; the full table with its sources is in ${CLAUDE_PLUGIN_ROOT}/references/patterns/asset-pipeline.md#budgets, to read when a number is disputed.

Check Budget How to measure or fix
LCP ≤ 2.5 s on a throttled 4G profile In order of preference: a trace through the Chrome DevTools MCP when it is connected (emulate with cpuThrottlingRate: 4 and networkConditions: "Slow 4G", then performance_start_trace with reload: true), labelled trace; otherwise capture.mjs dist --only mobile --scroll 0 --throttle --out "$capture_out-throttled", whose phone pass runs at 4× CPU, 150 ms RTT and 1.6 Mbps and records lcpColdSynthetic, blockingMs and cls for that pass, labelled throttled capture; for a deployed site with traffic, node "${CLAUDE_PLUGIN_ROOT}/scripts/crux.mjs" <url> (needs CRUX_API_KEY) gives the field p75, labelled field p75. An unthrottled manifest's lcpColdSynthetic is not an LCP measurement — headless, cold cache, software GL, and observed to differ by two orders of magnitude between viewports of one run — so never record it as this row's value; write not measured when none of the three ran. LCP comes from a poster or DOM text, never from the canvas
CLS and blocking CLS ≤ 0.1 during load (P08 under audit.mjs --render); blockingMs under 300 in the throttled phone pass the audit's rendered pass and the throttled manifest; the desktop inpLab is the slowest of the capture's own keyboard steps, a lab figure, never field INP
Entry JS ≤ 200 KB gz (P04 fails at 300) the bundler's gzip column, or gzip -c dist/assets/<entry>.js | wc -c
GL chunk lazy, ≤ 500 KB gz Three, OGL or R3F behind a dynamic import() in its own chunk, loaded after the first paint
Textures compressed, ≤ 700 KB per scene KTX2 for GL, AVIF or WebP for DOM rasters; no PNG photographs
Meshes Draco or Meshopt (P03), hero mesh ≤ 300 KB the loader has the decoder wired
Fonts ≤ 4 files, ≤ 400 KB (P05), subset, woff2, font-display (T05), size-adjust fallback (T06) <link rel="preload" as="font" crossorigin> for the faces used above the fold
<img> width and height, loading="lazy" below the fold, decoding="async", srcset and sizes for large rasters (P01, P02) every raster under 1 MB
<video> muted, playsinline, poster, preload="metadata" (A10) autoplay only with all four
Preloader exit CLS ≈ 0 the page is laid out beneath the overlay before it leaves; nothing reflows on exit
Off-screen chapters content-visibility: auto with contain-intrinsic-size long pages only; never on the chapter that holds a pinned stage
Renderer DPR capped at 2 (P06), dispose() on route change (P07) one ticker shared with the animation library

Measure sizes from the build, not from memory:

npm run build
for f in dist/assets/*.js; do printf '%s %s KB gz\n' "$f" $(( $(gzip -c "$f" | wc -c) / 1024 )); done
find dist -name '*.woff2' -o -name '*.woff' | xargs -r du -ch | tail -1
find dist \( -name '*.png' -o -name '*.jpg' -o -name '*.jpeg' -o -name '*.webp' -o -name '*.avif' \) -size +500k

The entry chunk is the one index.html loads with type="module"; the GL chunk is the one the dynamic import() produces. Write both numbers into the report even when they are inside budget, so the next pass can see drift.

5. Accessibility and usability

Why: usability is the lowest axis on 27 of the 31 corpus entries awarded since 2021 [verified per card; counted by scripts/calibration.mjs --since 2021, 2026-10-22], and a jury that finds a keyboard dead end at the first gesture stops looking for the good parts. Verify each item from the captures and the source; when a reduced-motion tier needs rework, read ${CLAUDE_PLUGIN_ROOT}/references/patterns/accessibility-and-reduced-motion.md for the three tiers and the keyboard paths.

  • Landmarks with one <main> and one <h1>, an unbroken heading order, lang on <html> (A01, A03, A09).
  • A skip link first in the tab order, landing on <main> (A13).
  • Visible :focus-visible styles in the world's own register, never outline: none without a replacement (A06, A07).
  • Reduced-motion tiers verified, not assumed: desktop-rm-s00 readable, state changes preserved (the menu opens, the theme swaps, the slider compares), loops static or paused, no global kill (M01, M02).
  • Keyboard walk: Tab through the whole page; the fullscreen menu traps focus, closes on Escape, returns focus and sets the page inert. Start from walk.json (--walk above): every finding it lists is resolved or recorded as an exception with its reason before Shipped is ticked.
  • Walk in this order and stop at the first dead end: skip link → header links → menu trigger and the open menu → every gesture in page order (hold gates, drags, compare sliders, rails) → forms → footer → the 404's way out.
  • Every drag, hold or draw gesture has a key path (A11); a virtual scroll still moves on Space, PageDown and arrows.
  • Coarse pointer: custom cursor and magnetic effects off under (hover: none), (pointer: coarse) (A08); nothing hover-only; touch targets at least 44 px; rails become native overflow.
  • Body contrast at least 4.5:1 (C01); the theme-color and selection pair keep contrast in both themes.
  • Every canvas aria-hidden with its text and images mirrored in the DOM, or carrying an accessible name (A04).
  • Live regions: preloader progress in an aria-live="polite" element; route changes announce the new title.
  • Sound strictly opt-in, with the toggle reachable by keyboard and persisted.

6. Meta and chrome

Why: the tab, the link preview and the error page are the first and last things a juror sees, and they are the cheapest places to look unfinished. The head per route, structured data, robots, the outline and the text behind a canvas are in ${CLAUDE_PLUGIN_ROOT}/references/patterns/seo-and-semantics.md; a consent banner's placement, keyboard path and cost in ${CLAUDE_PLUGIN_ROOT}/references/patterns/consent-and-banners.md. Every value below comes from the tokens and the type contract, so the chrome belongs to the world.

Item Ships when
<title> authored per route, never "Home" or the framework default
<meta name="description"> authored, specific, one sentence in the site's register
canonical present per route
Open Graph and Twitter card title, description and an image designed in the world at 1200 × 630 (S06); the preview checked once
favicon SVG with a PNG fallback and an apple-touch-icon, drawn from the tokens (S05)
theme-color per theme via media, from the tokens (S03)
color-scheme declared on <html> or in a meta (S04)
404 an authored moment with a way out; start from ${CLAUDE_PLUGIN_ROOT}/assets/templates/404.html when none exists, keep the same tokens, wire it to the host (a root 404.html on static hosts, the framework's not-found route otherwise)
robots.txt, sitemap.xml present and truthful; no noindex left over from staging
lang set on <html> (A09)

7. Browser surfaces

Why: default blue selection, a grey system scrollbar or a black focus ring on a warm dark ground announces that nobody looked. Read DESIGN.md ## Browser surfaces for the decided values and verify each exists in the shipped CSS.

  • ::selection (S01), caret-color, accent-color for native controls, -webkit-tap-highlight-color on touch.
  • Scrollbar styled through scrollbar-color and scrollbar-width, with the ::-webkit-scrollbar fallback (S02); never hidden on a page that scrolls.
  • Focus ring in the world's accent with an offset; overscroll-behavior where a full-screen stage would rubber-band.

8. Cleanup

Why: a shipped debug panel or a console full of logs costs the code-quality sub-score and tells the jury the site was never opened in a clean profile.

  • Debug flags off: query-string switches, stats.js, GUI panels, ScrollTrigger markers, wireframe toggles.
  • No console.log in the shipped bundle; no console.error from the page in a clean profile (the manifest shows zero).
  • Unused dependencies removed from package.json (npx depcheck when available, otherwise grep the imports); lockfile updated.
  • .awards/captures/, .awards/research/, .awards/neighbours/, .awards/capture.lock and .awards/audit.json in .gitignore; reports under .awards/jury/ and .awards/ship/ stay tracked.
  • Synthetic content labels in AWARDS.md ## Brief still true; no lorem or placeholder images (X02).

Component mode

Why: a single component ships inside a world that already shipped, so the pass narrows to what the component owns. Run the batch, the audit and the captures with --selector and --hover, measure only the budgets the component touches (its chunk, its assets, its fonts), verify its states (rest, hover, focus-visible, active, open and closed, reduced motion, coarse pointer, keyboard), and skip sections 6 and 7 unless the component changed a token they use.

9. The ship report

Why: awards:craft and the user need one document that says what changed, what was measured and what remains, so the state of the build is never in someone's memory.

  • Fill a copy of ${CLAUDE_PLUGIN_ROOT}/assets/templates/ship-report.md and write it to .awards/ship/<date>.md (date +%F; suffix -2 when taken): the fix table with classes, the audit counts and exceptions, the exact manifest path and coverage line, the performance table with measured values against budgets, the walk items, meta and chrome, browser surfaces, cleanup, and the status.
  • Append one line under AWARDS.md ## Ship log (node "${CLAUDE_PLUGIN_ROOT}/scripts/awards-log.mjs" AWARDS.md --append "Ship log" --line "<line>"):
- <date> · audit P0 n / P1 n / P2 n / P3 n · exceptions n · captures <n> valid from <manifest-path> · entry x KB gz · GL y KB gz · LCP z s (trace | throttled capture | field p75 | not measured) · CLS c · .awards/ship/<date>.md
  • In the report, one line from node "${CLAUDE_PLUGIN_ROOT}/scripts/design-md.mjs" diff DESIGN.md: the tokens that moved since the last jury snapshot (or unmeasured). A token that moved without a jury fix asking for it is named.
  • A material fix is any change that alters what a capture shows: layout, motion, colour, type, copy, a state. Meta, cleanup, exceptions and gitignore changes are not material.
  • Set ## Status (awards-log.mjs AWARDS.md --status "Shipped" --tick): tick Shipped (ship) only when no material fix was applied, the audit is clean, every contract row is kept or resolved, no fix remains partial/unresolved, and the recorded manifest covers all required chapters, viewports and states with valid frames. After a verdict of ship, "no fix remains" means no floor row: craft rows, whether the verdict lists them new or carries one as partial, do not hold the box, because applying one is material and needs another round, and a ship disposition already says the floor is clear; record each in the report as open — after ship with its evidence, and tick when the rest holds. Otherwise leave the box unticked; record unresolved contract/evidence gaps in the report, or back to awards:jury --verdict after a valid material fix batch until its verdict is ship.
  • Remind the user that headless captures prove correctness, not frame rate: WebGL work needs one pass on a real phone before launch.
  • When the host offers a tool that publishes a private page (an artifact or page tool), offer once to publish the ship report and the latest jury report with their first-viewport, mobile and reduced-motion frames, for the user to share. Publish only on a yes, keep it private, and never include .awards/research/ or .awards/neighbours/ captures: those are other people's sites.

Verify

  • .awards/audit.json is fresh, exits 0, and every remaining finding has a reason under ## Exceptions or inline.
  • All applicable manifest-listed frames (or the component set), including mobile middle/close, reduced-motion sections and named states, were opened and are valid; the manifest shows zero console errors, page errors and failed requests.
  • Every row of the performance table carries a measured value, gzipped where it is a size, with the trace, throttled-capture, field-p75 or not-measured label on LCP; an unthrottled manifest's lcpColdSynthetic is never that value.
  • The keyboard walk and the reduced-motion check were done against the build, not assumed from the source.
  • Title, description, OG image, favicon, theme-color, color-scheme, 404, robots and sitemap exist and were authored, not generated.
  • .awards/ship/<date>.md exists, ## Ship log has its line, ## Status reflects the outcome, and no jury fix was skipped without a deferred — conceptual entry.

Hand-off

When any material fix was applied and the recorded manifest has complete valid coverage, invoke the awards:jury skill now with the Skill tool, passing the brief, AWARDS.md path, --verdict, target, --captures <recorded-directory>, and that directory's exact manifest.json path; do not do its work inline. Missing or invalid evidence requires a fresh recapture before this handoff; if unavailable, return the unmeasured gap with the report. Deferred conceptual fixes go back to awards:craft with the report path. With no material fix, return a shipped result only when the audit is clean, every contract row is kept or resolved, no fix remains partial/unresolved, and the recorded manifest has complete valid coverage; otherwise return the report path and remaining blockers without a finished claim.

Refuse

  • A reduced-motion branch that kills everything (* { animation: none !important } or a global 0.01 ms duration); tier the motion instead (M02).
  • Removing the signature to pass a budget; tier it, lazy-load it or lower its resolution.
  • A preloader that runs longer than 2.5 s on a repeat visit, or one not tied to a real load signal.
  • Excepting a P0 finding, or any finding without a reason a juror would accept.
  • Redesigning during the fix batch, or adding fixes the jury did not list.
  • Writing "shipped" with the audit red, a capture unopened or a budget unmeasured.

04 同仓库更多 Skills

BurgiSimon
BurgiSimon/awards

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.

★ 0
BurgiSimon
BurgiSimon/awards

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.

★ 0
BurgiSimon
BurgiSimon/awards

structure

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.

★ 0
BurgiSimon
BurgiSimon/awards

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/Draco/KTX2 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).

★ 0
BurgiSimon
BurgiSimon/awards

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 / 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 / deconstruct / 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.

★ 0
BurgiSimon
BurgiSimon/awards

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).

★ 0