Decide what the page should accomplish
Define the audience, the main task and the primary action. A product landing page might explain a service and collect enquiries. A portfolio should help a visitor understand the work and make contact. These choices determine content and layout before you pick an animation or color palette.
Gather original copy, assets you have rights to use, and actual product details. If you do not have customer quotes, ratings or usage figures, leave them out. A template’s fictional figures must not become claims about your business.
Pick a workflow that fits your stack
Browse the design and development collections. A design-oriented skill may help with layout and typography. A testing skill can guide verification of a real browser interface. Check whether the workflow assumes a framework or build tool that your project actually uses.
Install the complete package in your agent. Work in a dedicated project and commit working states to version control. Ask the agent to inspect the existing structure before changing a site that already exists.
Give a concrete brief
For example: “Build a responsive one-page portfolio for a ceramic studio. Use our supplied photos and five project descriptions. Include a gallery, about section and working contact link. Use a quiet editorial layout, show keyboard focus, and support narrow mobile screens. Do not add fictitious testimonials.”
Specify whether you want a prototype or a deployable site. A prototype can demonstrate a visual idea; production work also needs functioning links, real form handling, metadata, error states and a reproducible build.
Verify the page in a browser
Run the project and inspect more than the first screen. Check narrow, tablet and desktop widths. Use the keyboard to navigate links, controls and menus. Look for clipped text, overflow, unreadable contrast and images that change the layout as they load.
Test every primary action. A button should download a real file, navigate to a valid destination or complete an actual interaction. A form needs server-side validation and abuse protection; a styled submit button alone is not an email service.
Check search essentials before publishing
Each public page needs a clear title, description, heading and readable body. Use a consistent canonical URL and link related pages. Add a sitemap, a useful not-found page and appropriate robots rules. Avoid exposing preview copies as competing production pages.
After deployment, test the actual domain, HTTPS and redirects. Connect a search reporting tool to observe indexing and queries over time. Technical SEO creates a sound foundation; it cannot guarantee that a new page will rank for a competitive term.