FIELD NOTE 08 / DESIGN BEYOND THE DEFAULT
Give it taste it can actually see.
Get a deliberate visual direction before another generic page gets built.
“Make it premium” leaves too many decisions unstated. A few concrete references, a clear audience, and a visible before-and-after give the model something useful to work against.
“Show it, don't describe it.”
Paul’s working notes · September 2026
What it looks like
“Make this beautiful and modern.”
Use this reference for spacing, this one for navigation, and this one for motion. Our audience needs to compare three options quickly. Show a desktop and phone direction before implementation.
Put it to work
- 01
Choose references for a reason.
Find a small set of real interfaces. Label the specific thing each teaches: type hierarchy, information density, navigation, or a transition. Reference a principle rather than asking for a copy of another brand.
- 02
Make the direction reviewable.
Ask for a rendered mockup or working preview with real copy. A screen full of placeholder content can hide the actual layout problem. Compare the phone version too. If the design feels wrong, identify the specific part to retain before revising.
- 03
Turn an approved result into a procedure.
Save the typography, spacing, contrast, motion, and responsive checks that made the design work. Apply that procedure to the next page, then inspect the actual render. Keep fewer, better interactions and provide a still experience.
Give this to your AI
Adapt the brackets to your task.Before building this page, inspect the existing site and these references: [links or screenshots]. Explain what you would adapt from each and what should remain ours. Propose one clear direction for [audience and task]. Use real draft copy. Show a rendered desktop and mobile preview. Evaluate delight, performance, efficiency, and simplicity. After I choose the direction, implement it and verify the real interactions, reduced motion, contrast, and overflow.
A skill name cannot supply missing taste or missing content. A prettier screenshot can still hide a broken flow. Use permitted assets, preserve original work, and check the implemented page rather than relying on the mockup.
Show the reference, name the principle, inspect the result.
Sources & further reading
Personal counts are from Paul’s prompt-history analysis. Tool guidance was checked against these sources in September 2026. Confirm current behavior in your installed version.