sheleg-design

SHELEG Design

Overview

A page feels cinematic not from many animations, but from a single source of truth (measured scroll position) driving many cheap, layered, independently-degradable responses. Centralize scroll into one store; layers read it per frame and react in their own language. Nothing crossfades — things redeploy. Every layer degrades to a calm static state.

READ FIRST, BEFORE ANY OF THE CRAFT BELOW: CREATIVE_DIRECTOR.md — the decision layer: what the surface is for and what would prove it failed; the lane and the mode (a redesign starts by measuring what it replaces, an update changes a token); which tools to cast, measured with npx sshlg-skills pack design --lane <lane>; when to fork into two variations with disjoint casts, the rubric written first; alignment and measurable quality as two separate questions; and the director record all of it lands in. The failure mode of an agent doing design is not ugliness, it is plausibility, and that document is what refuses it.

REQUIRED REFERENCE — for the cinematic path: read SHELEG_DESIGN.md before implementing a scroll-driven page — architecture, morph math, the DOM↔WebGL bridge, the build recipe (§11), the file map. Product-UI work does not owe this read; the one rule it would owe is repeated here: where a pack's motion tokens differ from the SHELEG defaults, the pack wins.

REQUIRED BEFORE ANY ANIMATION: read MOTION_DOCTRINE.md. SHELEG_DESIGN.md says how motion is built; the doctrine says whether to build it — the frequency table that kills animation on high-repetition paths, the easing tree and the ease-in ban, the duration ceiling, the forbidden forms, and the reduced-motion contract.

REQUIRED BEFORE ANY ACCESSIBILITY CLAIM: read ACCESSIBILITY_EVIDENCE.md — which bar a claim is held to (a WCAG criterion with number/version/level/units/exceptions, or a platform heuristic), what a screenshot can and cannot prove about the DOM and assistive technology, and the verdict contract: an absent tool is NOT_RUN, never PASS, and no check installs a scanner to complete itself. The connection is scoped, not routed: the craft gate's contrast row and the render critique consume these verdicts at the claim they are making — an existing capability, no new router, no new entry point. And a quality receipt keeps two kinds of row apart: visual judgment (how the render reads) and WCAG conformance (a computed, scoped check naming its criterion) — and a render fixed on the critique is judged on the SAME before/after matrix inside a bounded budget (CREATIVE_DIRECTOR.md), where an unresolved observation stays unresolved rather than being renamed shipped. A glance cannot produce a conformance row — a receipt where it did is refused, because "looked accessible" is a screenshot claim wearing a criterion's name.