starlight-web-productionlisted

# Starlight Web Production Treat distinctive quality as a release property. A framework, component library, screenshot, or animation technique is evidence or material—not the design direction. ## Authority Read the owning repository's constitution, `AGENTS.md`, `taste.md`, `design.md` or `DESIGN.md`, tokens, components, analytics, and prior decision receipts. The order of authority is: 1. product truth and brand constitution; 2. repository-local design contract; 3. approved taste/reference records; 4. a locked primary reference and bounded secondary references; 5. live research; 6. model defaults. Never let Aceternity, GSAP, Refero, shadcn, a template, or a trend become the brand. ## Operating sequence 1. Capture the current desktop and mobile truth. For greenfield work, capture the host context and gather real product states, proof, media, and copy. 2. State one recipient, one job, one promise, one action, one signature proof, and the intended feeling/understanding. 3. Research before composition. Prefer Refero styles/screens/flows when available; otherwise use current public, attributable sources. Record URL, owner, date, rights, observed principle, bounded use, and anti-reference. 4. For consequential visual work, produce exactly three materially different directions using the same real content. Resolve composition, type, imagery, interaction, motion posture, feasibility, and mobile behavior. 5. Record the selected direction. When the user explicitly delegates direc