START HERE

What you will learn

  • Translate brand intentions into usable layout, typography and writing rules.
  • Write prompts that preserve evidence and avoid invented claims.
  • Evaluate a page against the brief before extending the design.

Before you start: Approved brand material or a decision-maker who can define it, plus a draft of one real page. Any design or AI tool can be used.

Reference edition: Fictional website walkthrough; providers are examples, not required services. Sources checked 2026-11-13.

Define a design philosophy people can apply

“Modern and professional” does not resolve a layout decision. A useful philosophy might be “make the next step obvious, put evidence beside claims and use restraint so important information stands out.” Explain what this means for headings, spacing, imagery, navigation and calls to action.

Start with the reader’s situation. Someone comparing options needs clear differences and evidence; someone trying to contact the business needs a short, understandable path. A stakeholder should be able to judge these outcomes without knowing the design software.

Separate brand rules from page content

Record typography, colour roles, spacing, image treatment, component states and writing tone. Give colours jobs such as text, surface, accent, success and error instead of choosing a new colour per section. Define which heading sizes and page widths belong together. Use only fonts and images you are entitled to publish.

Keep factual material separate: approved service descriptions, evidence, contact details and restrictions on claims. A design prompt may reorganise approved facts, but it must not invent testimonials, results, accreditations or customer logos to fill a layout. Missing evidence is a question to resolve, not an invitation to generate proof.

Prompt for a decision, then for an implementation

First ask for a proposed page hierarchy and the reason for it. Review that against the visitor task before asking for code. Then request one representative page using the agreed rules and actual copy. This reduces the chance that attractive imagery conceals a confusing content structure.

Give the tool the audience, purpose, approved facts, design rules, constraints and expected output. Name the viewport behaviours, keyboard interactions and empty/error states you need to see. Ask it to identify unknowns and explain departures from the brief. Keep the wording model-agnostic; the brief should remain useful if the assistant changes.

Review one page as a system

Check whether the first screen explains the offer, the page supplies relevant evidence and the next step is clear. Try the layout at narrow widths and with long headings, missing images and real article titles. Test contrast, focus visibility, text resizing and form labels rather than relying on a screenshot that looks accessible.

Approve the reusable pattern, not just the picture. Record intentional exceptions and the reason for them. When asking for an iteration, reference the rule and observed problem: “The enquiry button becomes difficult to find after the service details; keep one clear action after that section.” This is more actionable than “make it pop.”

Technical examples

A model-agnostic design brief prompt

Replace the bracketed fields with approved information. Use the same brief with a designer, an assistant or a frontend implementer. Do not paste private customer records into a general design tool.

Context: We are creating an enquiry-led website for [audience].
Visitor task: Understand [offer], compare [relevant options] and [next action].
Approved facts: [service descriptions, evidence and contact details].
Design philosophy: Make the next step obvious; keep evidence beside claims; use a consistent visual hierarchy.
Brand rules: [typefaces and licences, colour roles, spacing, imagery and writing tone].
Constraints: No invented testimonials or results. Use semantic headings, labelled controls, visible focus states and responsive layouts.
First output: Propose the page hierarchy and explain how it serves the visitor task. List unknowns.
After approval: Build one representative page and show mobile, keyboard, loading and error behaviour.
Acceptance: [specific checks for clarity, content accuracy and usability].

Step-by-step process

  1. Gather approved inputs

    Bring the current logo, licensed fonts, image rights, factual copy and two examples of the tone you want. Mark anything unconfirmed.

  2. Write five or fewer design principles

    Make each principle guide a decision. For example, require a clear page purpose and place supporting evidence near the claim it supports.

  3. Create a small token and component sheet

    Name colour roles, text styles, spacing and the reusable button, card and form patterns. Define their interaction states.

  4. Review a single real page

    Use real draft content, test the narrow layout and agree the structure before expanding the site.

  5. Record feedback as a rule or exception

    Save the accepted version and the reason for any departure from the system so the next editor can preserve the intent.

FOLLOW ONE EXAMPLE

Worked scenario

Three stakeholders describe three different websites

A fictional business owner asks for bold design, an operations stakeholder wants clarity and a technical stakeholder wants maintainability.

  1. They translate those preferences into shared rules: a distinctive first impression, plain service explanations and reusable page sections.
  2. The first prompt requests a hierarchy and a rationale rather than a complete site. The stakeholders agree where evidence and the enquiry action belong.
  3. They test one page with a long service title and a narrow viewport. A crowded hero is simplified without discarding the brand.
  4. The accepted design rules become a project document used for subsequent prompts and component changes.

What this shows: The shared reference allows feedback to improve a coherent system rather than produce competing page styles.

The process at a glance

Brand alignment becomes repeatable when approved facts and explicit design rules are reviewed on one page before becoming templates.
ProcessDecisionHuman checkpoint
Read Mermaid diagram source
flowchart TD
 A[Audience and approved facts] --> B[Design philosophy]
 B --> C[Tokens and component rules]
 C --> D[Structured design prompt]
 D --> P[One representative page]
 P --> R[Stakeholder and accessibility review]
 R -->|Needs change| C
 R -->|Accepted| T[Reusable templates]

What you should have at the end

  • A reusable brief that works across design tools and AI models.
  • A reviewed page pattern with clear design and content ownership.

Common mistakes and how to avoid them

Prompting with adjectives alone

Translate the desired feeling into hierarchy, behaviour and evidence that can be checked.

Approving an image instead of the experience

Inspect real text, responsive behaviour and interaction states before approving the pattern.

Inventing proof to complete a page

Leave an explicit evidence gap for the owner to resolve. Do not publish generated claims as business facts.

APPLY THE IDEA

Try it yourself

Your task: Rewrite “make our site more premium” as a brief with a visitor task, three design rules and three acceptance checks.

What to produce: A saved prompt and an annotated page showing how the rules affect specific sections.

Check your understanding: Could another person evaluate the result against the same rules without guessing what premium means?

Key terms in plain English

Design token
A named design value, such as a colour role or spacing size.
Visual hierarchy
The arrangement that helps a reader recognise what matters first.
Representative page
A page that exercises the design patterns the rest of the site will reuse.

Sources and further reading