# Tips

1. Start with one audience and one primary action. A page needs a job before decoration.
2. Give the agent approved brand files. If absent, supply profile and banner screenshots and review the inferences.
3. Ask for three materially different mockups using the same copy. Select a named direction before code.
4. Save the research library. A summary without sources cannot support the next worker's decisions.
5. Reopen library files before each role. Send disagreements back to Researcher with claim IDs.
6. Choose the smallest stack that meets the actual interactions and publishing needs.
7. Make another page a data record and another brand a token set where the site permits it.
8. Compute contrast for actual text/background pairs. A vivid accent can still be unreadable.
9. Test the primary journey with keyboard, narrow viewport and reduced motion.
10. Keep embeds behind accessible click-to-play facades and verify the initial network requests.
11. Ask a different model family to challenge the fixed candidate. Reproduce findings before changing code.
12. Preserve receipts and a memory packet. Proposed memory is not a saved state.
13. Keep project work private and publish only the reviewed site artifact.
14. Treat unavailable tools honestly. A wireframe is planning; a visual mockup requires viewable pixels.

Next: [method](METHOD.md), [compatibility](COMPATIBILITY.md), [checklists](bundles/checklists.md).