Keep the visual decisions in the finished site
The details that make a composition work—type scale, measure, image treatment, spacing, and alignment—need to survive implementation. Give the agent the actual content, assets, and reference states you want to preserve. Inspect the rendered page rather than judging only a source diff.
Test the full range of ordinary states: hover, focus, loading, empty, and error. A polished first screenshot does not compensate for unreadable menus or a mobile layout that clips important text.
Use templates as material, not a finished identity
Browse portfolios, agencies, editorial sites, and other landing page categories. Each entry gives you a preview and a complete build prompt so you can understand how the design was constructed. Change the content, composition, and interaction to fit the work you are presenting.
Keep image and font credits with the files. Replace illustrative sample assets when they do not represent your project, and check the supplied licenses before redistributing them.
Make the live version part of the review
Publish the site and review its actual URL on a phone and laptop. Confirm that routes, fonts, forms, and media work from the deployed files. Send the same project back to your agent for corrections, then redeploy it rather than creating another address for each revision.
Static sites are available for self-service publishing. If your design needs an executable build, a backend, or a custom deployment command, check the account’s permitted capabilities first.