AI Prompts for a Static Website Workflow You Can Review
Turn a broad website request into small, verifiable changes with clear context, useful examples, and a repeatable review process.
The field guide / Prompt patterns
Useful website prompts name a concrete task, give the material needed to complete it, and define what a successful result looks like. Use separate prompts for architecture, implementation, and review so each output can be checked against a clear purpose.

State the page’s audience and job, then describe the delivery format. Provide the exact headings and content when they are known. Identify decisions the assistant may make, such as spacing, and decisions it must preserve, such as the domain and email address.
Create a responsive guide page for designers learning static sites.
Use HTML5, compiled CSS, and a small navigation script.
Use directory index pages and internal links ending in a slash.
Use the supplied copy. Include no forms or account controls.
Keep the main content readable without JavaScript.The example defines an output boundary without prescribing every visual detail. Add your actual brand and content before using it.
Describe the observed problem instead of asking for a vague improvement. Name the page, viewport, or control involved. Ask for the smallest coherent change and a description of how it was checked.
At narrow mobile widths, the article title clips its container.
Inspect the heading, surrounding grid, and text wrapping rules.
Fix the overflow while preserving the desktop type hierarchy.
Check the page at 320, 390, and 768 pixels wide.A concrete failure gives the review a clear endpoint. It also reduces the chance that unrelated components will change.
Ask for evidence against the brief: missing files, internal link targets, image dimensions, article length, metadata uniqueness, and keyboard behavior. Distinguish a completed check from a check that could not be run.
Follow the LLM context guide when the project grows. The AI prompting article expands these patterns, while the launch checklist covers the published artifact.
Include the requirements that affect the current task and a concise project context. Separate unrelated work into reviewable steps so omissions are easier to spot.
Compare the result with observable acceptance criteria. Check the actual files and behavior, then revise the prompt around a concrete gap.
Primary reference: Anthropic: writing clear instructions.