shape your siteStart with the task
Describe what a visitor needs to accomplish, not only the style you want. “Help a freelancer compare three service packages and request a quote” gives a builder something concrete to organize. Add the audience, the required content, and the primary action. These constraints should survive every visual iteration.
Choose a small set of references
Three references with distinct roles are easier to interpret than twenty unexplained screenshots. Use one for content hierarchy, another for typography, and a third for an interaction pattern. Explain the relevant quality in your own words. Avoid asking a tool to reproduce a whole brand or combine every visible detail.
Define the non-negotiables
Write down a few rules: readable body text, visible keyboard focus, a mobile navigation that works, and honest loading or error states. Specify your palette and explain where accent colors belong. If the design needs motion, describe its purpose and provide a reduced-motion alternative. Constraints make the result easier to review.
Review in layers
First check the content and main task. Next inspect layout and hierarchy. Then refine typography, spacing, and surface details. Finally test the interactions. Changing all of these at once makes it difficult to know whether an iteration is better. A short, specific correction gives the next generation a clearer target.
Own the final decision
Generated output is a starting point. Review its claims, images, dependencies, and behavior before publication. If a payment or form is only a mockup, connect and test the real service before presenting it as operational. A convincing interface is not evidence that the system behind it works. The finished site should reflect your judgment, not the tool’s defaults.