ls-design-buildlisted

# L.S.Design Build Implement what was approved. The design decisions were already made and confirmed by a person; this step turns them into code without relitigating them. ## Decision order User and repository requirements come first, followed by product and brand truth, accessibility and function, this specialist's guidance, then aesthetic defaults. Within that order, the approved handoff outranks the agent's own design preference — a disagreement with the design goes back to the studio, not into the code. ## Start here Read `design/handoff/BRIEF.md` before anything else. It names the premise, the target stack, the approved screens, the token rules, which content is quarantined fixture data, and which build specialist to route through. Everything else in the handoff folder is frozen at the moment the gate passed, so it is safe to build against even if `design/` has since moved on. If there is no handoff folder, this skill does not apply. Route to `ls-design-contract` to establish a contract, or to the relevant build specialist to work from the live contract directly. ## Working method 1. **Read the brief and the contract.** `BRIEF.md`, then `DESIGN.md` for intent, then `screens.json` for what each approved screen covers. 2. **Scaffold the target stack** named in `target_stack.json`. Import `tailwind.theme.css`, which imports `tokens.css`. Do not start a parallel token system. 3. **Study each approved screen** as a pair: the PNG is the visual record, the HTML shows th