🇺🇸English

Research-First Design

Don't guess—know. Study real products, learn from the best, then design with confidence.

But remember: References are just ingredients. Your product needs its own flavor. Use Refero for a rock-solid foundation (80%), then breathe soul into it (20%)—the distinctive choices that make your design memorable.

Mindset: Research isn't copying the average. It's finding what the TOP 10% do that others don't. Generic findings ("offer discount", "show social proof") are table stakes—hunt for specific tactics with exact copy, exact numbers, exact conditions. Generic design copies patterns. Great design understands psychology.

Always ask: "If I showed this to 10 users tomorrow, what would they remember?"

Before You Start: Discovery

Never design blind. Ask these questions first:

1. WHAT are we building?
   → Screen type, Platform, Scope

2. WHO is this for?
   → Audience, Technical level

3. WHAT should users accomplish?
   → Primary action, Success metric

4. WHAT feeling should it evoke?
   → Tone, Energy

5. WHAT JOB is the user hiring this page to do?
   → "Help me decide" (pricing, comparison)
   → "Convince me to trust you" (fintech, healthcare, enterprise)
   → "Get me started without friction" (onboarding, signup)
   → "Show me what to do next" (empty state, dashboard)
   → "Make me feel I'm not missing out" (waitlist, upgrade)

6. WHAT objections might they have?
   → "Is it worth the price?" / "Is it legit?" / "Will it work for me?"

7. WHAT should they remember tomorrow?
   → The hook, the differentiator, the "aha"

8. ANY constraints?
   → Brand guidelines, Technical requirements, Inspirations

Output a Design Brief:

"I'm designing a [WHAT] for [WHO] that helps them [GOAL] and should feel [TONE]. The user's job: [JOB]. Main objection to overcome: [OBJECTION]. They should remember: [HOOK]. Constraints: [CONSTRAINTS]."

The Workflow

┌─────────────────────────────────────────────────────────────────┐
│  0. DISCOVER → Design Brief                                     │
│                              ↓                                  │
│  1. RESEARCH                                                    │
│     Experiment with queries: broad → narrow → leader            │
│     Try different angles until patterns emerge                  │
│     → Raw material: dozens of references                        │
│                              ↓                                  │
│  2. ANALYZE                                                     │
│     Extract and structure what you found                        │
│     Compare approaches, identify patterns                       │
│     → Synthesis: documented patterns + decisions                │
│                              ↓                                  │
│  3. DESIGN                                                      │
│     Apply craft: typography, color, spacing, copy               │
│     Define soul: what makes THIS product unique                 │
│     → Blueprint: design system + unique identity                │
│                              ↓                                  │
│  4. IMPLEMENT                                                   │
│     Build the actual interface                                  │
│     Validate against references and quality gates               │
│     → Ship-ready design                                         │
└─────────────────────────────────────────────────────────────────┘

Phase 1: Research

Goal: Gather raw material. Experiment freely with different search strategies.

Search by Facts, Not Feelings

Query what's literally on the screen—not abstract concepts:

• ✅ "pricing toggle", "testimonial carousel", "feature comparison table"
• ✅ "Stripe", "Linear", "Notion" (company names)
• ✅ "dark mode", "minimalist", "gradient" (visual styles)
• ✅ "ios", "web", "android" (platforms)
• ❌ "fintech onboarding", "enterprise SaaS" (industry is in metadata, not descriptions)
• ❌ "user-friendly pricing" (subjective, not searchable)

Note: Industry info lives in the category field, not screen descriptions. Search "onboarding" → filter results by relevant category.

Example queries for a pricing page:

Screen type:  "pricing", "pricing page", "plans"
Elements:     "pricing toggle", "annual/monthly switch", "plan cards"
Companies:    "Linear", "Superhuman", "Loom", "Notion"
Styles:       "dark mode pricing", "minimalist pricing"
Platforms:    "ios pricing", "web pricing", "mobile subscription"

Search Strategy: Experiment

Don't settle on the first query. Try multiple angles until you've seen the landscape.

Query Types:

Search Loop:

1. Start BROAD → see what exists
2. Notice interesting patterns → go SPECIFIC
3. Find a great example → search that COMPANY
4. Try different ELEMENT → "plan comparison", "feature table"
5. Go CROSS-PLATFORM → designing for iOS? check web too (fresh ideas)
6. Filter by CATEGORY → narrow to your industry
7. Repeat until you've seen 50-100 results

Example: Designing a pricing page

"pricing page" (broad) → see toggle patterns
→ "pricing toggle annual monthly" (specific element)
→ "Linear" (great example) → explore their approach
→ "plan comparison", "feature table" (different elements)
→ check both web and mobile versions
→ filter by SaaS category
→ 50+ results, clear picture of patterns

Go Deep, Not Just Wide:

Don't stop at page 1. The best inspiration hides beyond obvious results:

• Skip the usual suspects (Stripe, Linear, Notion) — everyone copies them
• Search adjacent industries — fintech can learn from healthcare
• Find the weird ones — unconventional solutions spark original ideas

The gold is in the long tail. First 10 results = what everyone sees. Results 50-100 = unique inspiration.

Tool Selection

Decision tree:

Journey (multi-step)?  → FLOWS first, then screens for details
Single screen?         → SCREENS only
Few flow results?      → Search screens and reconstruct the journey

Key Question: "Does this screen have a BEFORE and AFTER?"

• YES → search both screens AND flows
• NO → search screens only

Uselimit parameter. Get more context per query—don't hesitate to set limit=25 or even 50.

Deep Dive: get_screen (Required)

Search results contain brief descriptions only. You MUST callget_screen for 5-10 best results to get full analysis:

• Full detailed description (much more than search snippet)
• Complete metadata (company, category, tags)
• Capture exact details: specific copy, numbers, conditions, timing — not generic descriptions
• include_similar: true — returns visually similar screens. Found one good example? Similar screens = more good examples fast.
• image_size: use "none" (default) for text analysis, "thumbnail" or "full" for visual inspiration.

💡 Batching tip: Call for 2-3 screens at a time, not all at once. If something fails—try smaller batches, don't stop.

❌ Reading search descriptions only = surface research ✅ Calling get_screen for best finds = real research

Example workflow:

1. search_screens("pricing page", limit=30) → scan results
2. Pick 8 most interesting screens
3. get_screen(screen_1, include_similar=true) → deep analysis
4. get_screen(screen_2, screen_3) → compare approaches
5. Repeat for remaining screens

Focus Your Research

Every task has two dimensions: the challenge you're solving and the type of research needed. Identify both before searching.

By Challenge — what problem are you solving?

Ask: "What's the #1 thing that could go wrong here?" Then research how others solved it.

By Goal — what type of research do you need?

Visual direction — finding the right style

Look for:  typography (fonts, sizes, weights), colors, spacing, details (shadows, radii, gradients)
Queries:   "dark mode", "minimalist dashboard", "gradient hero", "glassmorphism"
Extract:   font pairings, color palettes, spacing rhythm, micro-details
Skip:      conversion tactics, copy analysis

Competitive analysis — understanding how others position

Look for:  headlines, value propositions, pricing structure, feature framing
Queries:   "[competitor name]", "saas landing", "pricing page", "hero section"
Extract:   how they explain value, what objections they address, pricing tiers
Skip:      visual details (unless relevant to positioning)

UX/Flow optimization — improving journeys

Look for:  step count, friction points, error handling, save states
Queries:   "onboarding flow", "checkout", "signup", "cancellation"
Extract:   what reduces friction, decision points, recovery patterns
Skip:      visual polish (focus on structure)

Component design — specific UI elements

Look for:  all states (default, hover, active, disabled, loading, error, empty)
Queries:   "toggle", "dropdown", "modal", "card", "table"
Extract:   interaction patterns, edge cases, accessibility considerations
Skip:      page-level patterns

Mix as needed:

• Abstract request ("design a pricing page") → use all recipes
• Specific request ("find dark mode inspiration") → focus on Visual
• Mixed request ("pricing page like Linear") → Competitive + Visual

For detailed tool parameters, see references/mcp-tools.md.

Three Lenses (Use All)

Lens A: Structure — What do they all do?

• Layout, components, information hierarchy
• Common solutions to common problems

Lens B: Visual Craft — How does it LOOK and FEEL? For each strong reference, notice:

1. Typography — What fonts? Serif or sans? What makes headlines feel premium?
2. Color — Warm or cool? How many colors? What's the accent?
3. Spacing — Tight or airy? What's the rhythm?
4. Details — Shadows, borders, radii, gradients?
5. Icons/Illustrations — Style? Stroke width? Custom or library?
6. Overall vibe — Premium? Playful? Technical? Minimal?

Don't copy—extract principles. "This feels premium because of tight letter-spacing and generous whitespace" → apply that principle to your design.

Lens C: Conversion & Soul — What makes this one WORK? For each strong reference, ask:

1. What's the HOOK in the first 3 seconds?
2. How do they handle OBJECTIONS?
3. Where's the TRUST (social proof, guarantees)?
4. What's UNIQUE that I haven't seen in others?
5. What MICROCOPY has personality?
6. What would a user REMEMBER tomorrow?

For Flows (additional lens):

• Step count — how many screens to complete the task?
• Decision points — where does the user choose?
• Friction reducers — what makes it feel easy?
• Save states — can they resume if interrupted?
• Error handling — what happens when things go wrong?
• Recovery paths — how do they get back on track?

Research Completion Check

Research is done when you can answer YES to all:

• Tried 5+ different query variations (not just same topic rephrased)
• Reviewed 50+ screens or flows in search results
• Called get_screen for 5-10 best screens (deep analysis)
• Found 5+ clever tactics worth adapting (not common—clever)
• Each finding has EXACT details (copy/numbers/conditions), not generic descriptions
• Found at least 1 thing that surprised you
• Can describe "what the best products do and why"
• Can answer: "What do most products do?" and "What do the best ones do differently?"

Common mistakes:

• ❌ All queries about same topic ("paywall", "subscription paywall", "iOS paywall")—vary by companies, elements, styles, colors, platforms
• ❌ Reading only search descriptions without calling get_screen
• ❌ Stopping at first 10-20 results when deeper exploration would help
• ❌ Hitting a problem and giving up—try smaller batches, different approach, keep going

Good research vs bad research:

❌ Surface research:
   - 3 queries, all variations of "pricing page"
   - Read 15 search descriptions
   - Skipped get_screen calls
   - Findings: "offer discount", "show value", "collect feedback" (generic)

✅ Real research:
   - 7+ queries across different angles
   - Reviewed 50+ screens in search results
   - Called get_screen for 8 best finds
   - Findings with EXACT details: "Copy.ai shows 60% discount ONLY after 'too expensive' reason, with exact copy 'We'd hate to lose you over price' and 24h countdown"
   - Can explain "why" behind each pattern

Output

Raw collection of 50-100 references. Don't filter yet—gather everything potentially useful.

Research Summary (Required)

After completing research, ALWAYS present a summary to the user:

📊 RESEARCH SUMMARY
────────────────────────────────────────
Queries: [count] | Screens analyzed: [count]

WHAT I FOUND:
  [Adapt to user's question — visual details, flow logic, patterns, etc.]
  
  Key findings (facts with sources):
  • [Company] — [specific detail: exact copy, size, color, step count, etc.]
  • [Company] — [specific detail]
  
  Notable differences:
  • [what varies between products — if relevant to the task]

GAPS: [what wasn't found]
────────────────────────────────────────

Quality check: Every finding should be a fact you observed, not an opinion. Include source (company/product name). Be specific — "20px font" not "large font", "5-step flow" not "short flow".

Phase 2: Analyze

Goal: Structure your research. Extract patterns. Make decisions.

This phase is pure synthesis—no opinions, just document what you found.

Research ≠ Copying the Average

Don't just follow "best practices." Research is about understanding WHY choices work, not copying WHAT everyone does.

The experiment mindset:

• Best practices = starting point, not destination
• "Safe" often = "forgettable"
• If 80% use approach A, but B fits YOUR context—use B
• Document reasoning: "Most use X, but we chose Y because..."

When analyzing, ask:

1. Why did they make this choice?
2. Does this serve THEIR users or MINE?
3. What's the bold choice that makes it memorable?

What to Extract

For each strong reference, document:

Pattern Table

Compare 3-5 best references:

Steal List (Required — minimum 5 items)

Don't just document patterns—capture specific tactics to adapt:

STOP: If this table has fewer than 5 rows, go back to research.

Be specific, not vague:

• ❌ "Linear — clean design" (not actionable)
• ✅ "Linear — 13px/20px body text, -0.01em tracking, 48px section gaps, #5E6AD2 accent at 8% opacity for hover states"

Categories to cover (pick relevant ones):

• Trust signal (social proof, guarantee, security)
• Objection killer (addresses "but what if...")
• Friction reducer (makes action feel easy)
• Visual treatment (typography, color, spacing you'll adapt)
• Micro-detail (shadow, border, animation, icon style)
• Memorable element (what will they screenshot?)

Output

Structured document with:

1. Patterns identified across references
2. Specific choices for your design
3. Reasoning for each decision

Phase 3: Design

Goal: Achieve professional quality. This is where craft matters.

You have the structure from research. Now execute like a senior product designer.

Typography

Scale: Use a ratio (1.2 or 1.25). Max 6-8 sizes: Display (48-64px), H1 (36-48px), H2 (24-32px), Body (16-18px), Small (13-14px), Caption (11-12px).

Leading: Larger text = tighter (1.0-1.2). Body = looser (1.5-1.6).

⚠️ LETTER-SPACING — DO NOT SKIP

Common mistakes:

• ❌ ALL CAPS without tracking (looks cramped)
• ❌ Small text without positive tracking (hard to read)

Line length: 50-75 characters (max-width: 65ch). Pairing: Max 2 fonts.

→ Full guide: references/typography.md

Color

Palette: 4 layers — Neutrals (70-90%), Primary accent (5-10%), Semantic (success/warning/danger), Effects (rare).

Neutrals: 10-12 steps (50…950). Create breathing room with spacing, not faded text.

Primary: One brand color with scale (50–950). Use 600 default, 700 hover, 800 active, 100-200 for tints.

Contrast: 4.5:1 for body text (≤16px), 3:1 for large text.

Dark theme: Not inverted. Separate neutrals. Background #0f0f0f, not #000. Text #f0f0f0, not #fff.

Tokens: Name by purpose (--primary), not color (--blue).

→ Full guide: references/color.md

Spacing (Summary)

Base unit: 4px or 8px. Everything multiplies from this.

4px system:  4, 8, 12, 16, 24, 32, 48, 64, 96
8px system:  8, 16, 24, 32, 48, 64, 96, 128

Proximity = relationship. Closer = connected, farther = separate. Spacing explains grouping.

Rhythm: Consistent gaps between similar elements. Larger gap = new section.

Avoiding AI Slop

⛔ NO INDIGO/VIOLET — Unless the user explicitly requests purple/indigo, do not use it. Every LLM defaults to indigo (#6366f1) because it's "safe." This makes it the biggest tell of AI-generated design. Choose brand-appropriate colors from your research instead.

Generic AI output:

• ❌ Default system fonts without intention
• ❌ Safe blue gradients everywhere
• ❌ Perfect symmetry (no visual tension)
• ❌ Blob/wave backgrounds (meaningless decoration)
• ❌ Stock illustrations that could be anywhere

Professional design:

• ✅ Brand-appropriate color chosen from research
• ✅ Intentional font pairing that matches tone
• ✅ Visual tension and asymmetry
• ✅ Purposeful whitespace
• ✅ Custom or curated imagery
• ✅ At least one "clever" element from Steal List implemented
• ✅ Social proof present (or justified absence)

Generic structure trap: Don't default to: Hero → Features Grid → Pricing → FAQ → CTA This is the "safe" template everyone uses. Ask: "What can I add, remove, or reorder to make this more effective for THIS product?"

→ Full guide: references/anti-ai-slop.md

Motion

Motion serves: Feedback (it worked), Continuity (where it went), Hierarchy (look here). If animation doesn't do one—remove it.

Easing: Enter = ease-out, Exit = ease-in, Change = ease-in-out.

Micro-interactions: Button press scale: 0.98 90ms. Hover background shift 120ms.

Required: prefers-reduced-motion support. No animation > 500ms in product UI.

Anti-patterns: ❌ 300ms+ on hover ❌ Linear easing ❌ Everything animates at once

→ Full guide: references/motion.md

Icons

Icons are typography, not illustration. Punctuation marks, not mini-pictures.

Style: One style per product (outline OR solid). Mixing libraries = visual collage.

Optical corrections: Geometric center ≠ visual center. Arrows, chevrons need 0.5–1px shift.

Size: Match text's visual weight. Icon height ≈ text line-height or smaller.

Color: currentColor inherits automatically. Semantic colors only for status.

Accessibility: Action icons need aria-label. Hit area 44×44px minimum.

Libraries: Lucide (SaaS default), Heroicons (Tailwind), Material Symbols, SF Symbols (Apple).

→ Full guide: references/icons.md

The Persuasion Layer (Before Visuals)

STOP: Fill this table before writing any code.

Required trust signals (pick at least 2):

• Testimonials with real names/photos
• Company logos ("Trusted by...")
• Specific numbers ("50K+ users", "$2M saved")
• Guarantees ("Cancel anytime", "Money back")
• Security badges (if relevant)

If you can't fill this table, you're designing decoration, not persuasion.

The Soul

~80% proven patterns + ~20% unique choices.

Where to add distinctiveness:

• One bold visual choice (color, type treatment, illustration style)
• Voice and personality in copy
• Micro-interactions that surprise
• One detail users will remember and mention

Test: "If someone screenshots this, would they know it's from THIS product?"

Output

Complete design specification:

• Typography system (fonts, scale, spacing)
• Color palette with usage rules
• Spacing system
• Component patterns
• Unique identity elements

Phase 4: Implement

Goal: Build it. Validate against references and quality standards.

Build Checklist

• Semantic HTML structure
• CSS custom properties for all tokens
• Responsive breakpoints (320px, 768px, 1200px minimum)
• Hover/focus states for all interactive elements
• Accessible contrast ratios
• Smooth transitions (0.2s ease for most interactions)

→ For implementation details (forms, focus, images, touch, performance): references/craft-details.md

Quality Gate

Side-by-Side Test

Place your implementation next to top 3 references.

Target: Match or exceed in 3/4 criteria:

• Polish (details, alignment, consistency)
• Clarity (hierarchy, readability)
• Uniqueness (memorable elements)
• Usability (obvious actions, no confusion)

When to Return to Research

• Something feels "off" but you can't say why
• Stuck between two approaches
• New requirement invalidates earlier decisions

Example

For a complete walkthrough (SaaS churn reduction), see references/example-workflow.md.

Reference Files

Resources

• Refero MCP — 150K+ screens and flows
• Refero.design — Browse visually
• Apple HIG / Material Design — Platform conventions

Don't guess. Research with Refero. Craft with intention. Infuse it with soul.

Weekly Installs

724

Repository

referodesign/re…ro_skill

GitHub Stars

14

First Seen

Feb 28, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykWarn

Installed on

codex716

cursor715

cline713

gemini-cli713

opencode713

github-copilot713