World-Class Web Release
World-class is a release property, not a styling adjective. A surface passes only
when its language, composition, type, imagery, motion, engineering, and production
evidence tell one coherent story.
Required Sequence
- Reconstruct context. Read the repository contract, brand pack, existing
surface, source material, prior decisions, and known constraints. Name the
recipient, their knowledge state, the job of the surface, and the consequence.
- Capture current truth. For a redesign, capture the existing desktop and
mobile states. For a greenfield route, capture the host site's desktop and
mobile context. Gather real workflows, artifacts, quotations, results, and
authorized imagery. Stop when a referenced existing surface cannot be captured.
- Write the experience thesis. State one recipient, job, promise, primary
action, signature proof, and intended feeling.
- Compare exactly three directions. Each must materially differ in
composition, typography, imagery, interaction, and motion posture. Select one
before implementation.
- Build the static composition. Resolve hierarchy, pacing, typography, proof,
responsive behavior, and conversion before motion.
- Pass editorial articulation. Use
skills/editorial-articulation/SKILL.md.
Read every sentence aloud. Reject name-swappable or taxonomy-led copy.
- Earn motion. Use
skills/motion-and-interaction/SKILL.md. Motion must
orient, explain, confirm, reveal causality, or create one brand memory.
- Compare and verify. Capture desktop, mobile, interactions, and reduced
motion. Test accessibility, reflow, loading, performance, links, claims,
privacy, analytics, and failure states as applicable.
- Separate responsibility. Maker, verifier, and approver are distinct for
public flagship releases.
- Prove production. Record commit, checks, preview, production URL,
post-deploy verification, the paths covered by the evidence, and exact rollback
in the release manifest. Generate this receipt after deployment. Keep the
manifest outside the production commit—such as a CI artifact or a later
receipts commit—because a commit cannot contain its own SHA. Store blocking
evidence beside the manifest and
content-address every artifact with SHA-256, byte size, MIME type, and
dimensions when applicable. Shipped motion requires decoded, ordered PNG frame
sequences with distinct initial, active, and resting states, exact CSS
viewport/DPR metadata, at least 0.1% decoded-pixel change between adjacent
frames, and a separately sampled reduced-motion stability sequence; a filename,
URL, or unchecked media container is not proof.
Font-file checks establish only the container
signature. Computed-font reports and responsive specimens establish that the
intended family and weights actually rendered. Remote URLs are references, not
release evidence.
The manifest must validate against
schemas/web-release-evidence.schema.json. It records three distinct direction
artifacts, item-level scores, reviewed-copy hash, selected font and computed-font
proof, required engineering reports, production commit, and rollback evidence.
Validate it:
npm run validate:release -- path/to/release-evidence.json --repo-root /path/to/owning-repo
Hard Stops
Do not build, merge, or promote when an applicable condition is true:
- an existing URL has no current desktop and mobile capture;
- recipient evidence is invented, inferred as fact, or copied from generic language;
- a named partner surface lacks privacy and consent classification;
- the first viewport hides the person, product, workflow, or offer;
- typography has no role, specimen, source, license, or mobile proof;
- motion has no named job or reduced-motion behavior;
- proof consists only of claims, repository names, frameworks, or diagrams;
- mobile is merely stacked desktop;
- the same identity made, verified, and approved the release;
- production cannot be inspected or rolled back.
- the production receipt is embedded in the production commit it claims to prove.
Output
Return the experience thesis, selected direction, working preview, changed
artifacts, editorial/visual/type/motion/accessibility/performance/privacy/
engineering evidence, independent verdict, production proof, and rollback.
Do not substitute a plan, score, CI result, or attractive screenshot for the
complete release.
1---2name: world-class-web-release3description: Use for any high-value website, landing page, homepage, partner page, product surface, brand experience, or redesign where language, typography, imagery, motion, implementation, and production proof must feel distinctive and human. Also use when upgrading a web-design quality system or release gate.4---56# World-Class Web Release78World-class is a release property, not a styling adjective. A surface passes only9when its language, composition, type, imagery, motion, engineering, and production10evidence tell one coherent story.1112## Required Sequence13141. **Reconstruct context.** Read the repository contract, brand pack, existing15 surface, source material, prior decisions, and known constraints. Name the16 recipient, their knowledge state, the job of the surface, and the consequence.172. **Capture current truth.** For a redesign, capture the existing desktop and18 mobile states. For a greenfield route, capture the host site's desktop and19 mobile context. Gather real workflows, artifacts, quotations, results, and20 authorized imagery. Stop when a referenced existing surface cannot be captured.213. **Write the experience thesis.** State one recipient, job, promise, primary22 action, signature proof, and intended feeling.234. **Compare exactly three directions.** Each must materially differ in24 composition, typography, imagery, interaction, and motion posture. Select one25 before implementation.265. **Build the static composition.** Resolve hierarchy, pacing, typography, proof,27 responsive behavior, and conversion before motion.286. **Pass editorial articulation.** Use `skills/editorial-articulation/SKILL.md`.29 Read every sentence aloud. Reject name-swappable or taxonomy-led copy.307. **Earn motion.** Use `skills/motion-and-interaction/SKILL.md`. Motion must31 orient, explain, confirm, reveal causality, or create one brand memory.328. **Compare and verify.** Capture desktop, mobile, interactions, and reduced33 motion. Test accessibility, reflow, loading, performance, links, claims,34 privacy, analytics, and failure states as applicable.359. **Separate responsibility.** Maker, verifier, and approver are distinct for36 public flagship releases.3710. **Prove production.** Record commit, checks, preview, production URL,38 post-deploy verification, the paths covered by the evidence, and exact rollback39 in the release manifest. Generate this receipt after deployment. Keep the40 manifest outside the production commit—such as a CI artifact or a later41 receipts commit—because a commit cannot contain its own SHA. Store blocking42 evidence beside the manifest and43 content-address every artifact with SHA-256, byte size, MIME type, and44 dimensions when applicable. Shipped motion requires decoded, ordered PNG frame45 sequences with distinct initial, active, and resting states, exact CSS46 viewport/DPR metadata, at least 0.1% decoded-pixel change between adjacent47 frames, and a separately sampled reduced-motion stability sequence; a filename,48 URL, or unchecked media container is not proof.49 Font-file checks establish only the container50 signature. Computed-font reports and responsive specimens establish that the51 intended family and weights actually rendered. Remote URLs are references, not52 release evidence.5354The manifest must validate against55`schemas/web-release-evidence.schema.json`. It records three distinct direction56artifacts, item-level scores, reviewed-copy hash, selected font and computed-font57proof, required engineering reports, production commit, and rollback evidence.5859Validate it:6061```bash62npm run validate:release -- path/to/release-evidence.json --repo-root /path/to/owning-repo63```6465## Hard Stops6667Do not build, merge, or promote when an applicable condition is true:6869- an existing URL has no current desktop and mobile capture;70- recipient evidence is invented, inferred as fact, or copied from generic language;71- a named partner surface lacks privacy and consent classification;72- the first viewport hides the person, product, workflow, or offer;73- typography has no role, specimen, source, license, or mobile proof;74- motion has no named job or reduced-motion behavior;75- proof consists only of claims, repository names, frameworks, or diagrams;76- mobile is merely stacked desktop;77- the same identity made, verified, and approved the release;78- production cannot be inspected or rolled back.79- the production receipt is embedded in the production commit it claims to prove.8081## Output8283Return the experience thesis, selected direction, working preview, changed84artifacts, editorial/visual/type/motion/accessibility/performance/privacy/85engineering evidence, independent verdict, production proof, and rollback.8687Do not substitute a plan, score, CI result, or attractive screenshot for the88complete release.
frankxai