How to apply

Order of work

1. Load the general skills for the stack — production-quality component/layout mechanics, polish, motion, and a check that web patterns aren’t stale before any HTML/CSS/client-JS.
2. Find the nearest known-good reference before generating — an existing component, a sibling app or page, or a grep of the repo. Adapt the closest complete match instead of inventing structure.
3. Preserve what already works; enhance progressively rather than rewriting.
4. Build the smallest durable change.
5. Add motion last, and ship a reduced-motion path.
6. Verify in a real browser at desktop and mobile before calling it done.
7. Only if the task touches WordPress / Nectarblocks, consult the WordPress / Nectar lessons for block-validity rules and gotchas; otherwise the principles suffice.

Completion standard

Meet the general production-quality bar, plus Sam’s verification habit:

• The page or component renders (or returns 200 if server-rendered) with no console errors.
• Desktop and mobile both checked — no clipped controls, horizontal overflow, or dark-on-dark text.
• Images and media load, and crops keep their subject.
• Any motion keeps content visible and respects reduced motion.
• Report what changed and any remaining risk.