When to load: After Visual Direction, as final Product Brief companion document Agent: Saga or Freya
Without documented visual/UX preferences from real examples, Dream Up agents must guess what the client likes. This causes:
The power of this document: When a client says "I like that layout" pointing at a real site, you now have a concrete, documented reference. Not abstract words — a real example with specific elements they approved or rejected.
For Dream Up quality: Every future generation can self-review against documented preferences. "Did I follow the layout principle from Site 1 that the client liked? Did I avoid the pattern from Site 2 they rejected?"
Satisfaction criteria — by the end you should have:
Quality bar:
Ask the client for 2-4 sites they find inspiring. These could be:
If client is hesitant: Even one site with one thing they like is valuable. Don't require perfection — any concrete reference beats abstract descriptions.
If client has no references: Offer to find 2-3 examples in their industry. Show them and ask for reactions.
Step 1: Load the site — use browser/WebFetch tools to see what the client sees.
Step 2: Ask open first — "What drew you to this site?" / "What do you like about it?" Let the client lead.
Step 3: Get specific — naturally ask about elements you can see on the site. Don't use a checklist. Ask about what's actually there:
Step 4: Capture nuance — listen for:
Step 5: Extract principles — as patterns emerge across sites, identify strategic takeaways. Test your understanding: "I'm noticing you prefer X — is that fair?"
After all sites are analyzed, organize findings into design principles by category:
Confirm with client: "Based on what you liked and didn't like, here's what I'm taking away. Does this capture your vision?"
Layout and structure:
Navigation and UX:
Visual style:
Content display:
Performance and feel:
Create inspiration-analysis.md in the Product Brief output folder.
For each site:
## Site: [Name or URL]
### What Client Liked
- [Specific element] — [Why it works for them]
- [Specific element] — [Why it works]
### What Client Didn't Like
- [Specific element] — [Why it doesn't work]
### Adaptations Needed
- [Element] — [Like the concept but needs modification because...]
### Principles Extracted
- [Strategic takeaway from this site]
Synthesis:
## Design Principles (from all sites)
### Layout
- DO: [Patterns to follow]
- DON'T: [Patterns to avoid]
### Content Hierarchy
- DO: [How to prioritize]
- DON'T: [What not to do]
### Visual Style
- DO: [Visual direction]
- DON'T: [What to avoid]
### User Experience
- DO: [UX patterns to adopt]
- DON'T: [Anti-patterns]
Usage note at the end:
## How to Use This Document
**For Scenario Outlining (Phase 4):**
Reference layout patterns when designing user flows
**For Page Design (Phase 5):**
Use extracted principles as design checklist.
Reference "What Client Liked" for visual direction.
Avoid "What Client Didn't Like" patterns.
**For Dream Up self-review:**
Check generated output against documented preferences.
"I like everything about it" → Nothing is perfect. Probe: "Even if we could copy it exactly, what would you adjust for your business?"
"I hate everything" → Something drew them to share it. Ask: "What made you think of this site initially?"
Contradictory preferences → Different contexts may drive different preferences. Explore: "These sites have very different approaches — what draws you to each?"
Overly technical feedback ("Great CSS grid implementation") → Redirect to user value: "What does that achieve for visitors that you like?"
Brand name dropping ("Make it like Apple") → Probe specifics: "What specifically about Apple's approach appeals to you? The minimalism? The product focus? The typography?"
You've succeeded when:
Dream Up agents can now:
Concrete examples beat abstract descriptions every time. This document turns "make it modern" into "like Site A's single-page layout with fixed contact header, but simpler than Site B's cluttered services grid."