Style Fits the Job

What does Style Fits the Job do?

Problem

AI-generated UI has a default aesthetic that gets applied everywhere, regardless of the context:

• Glassmorphism cards (backdrop-filter: blur() + semi-transparent white)
• Neumorphism inset/outset shadows
• Purple-to-blue gradients on buttons, text, and borders
• Blurred colorful light orbs floating on dark backgrounds
• Neon glowing box-shadow, with hover effects that enlarge, lift, or rotate elements
• Every block is a card with 24px border radius, preceded by an emoji in the heading
• Copy like "✨ AI-Powered", "🚀 Get Started Now"

Result: An expense approval tool for finance or a log viewer for ops looks like a game launcher or a crypto landing page. Users who spend eight hours a day on it find it visually noisy, hard to scan, and unprofessional — undermining trust.

The reverse also happens: a casual game for friends, a lottery spinner, or a pet diary gets built as a gray table with default blue buttons. All the fun is gone.

Style isn't about "looking good" — it's about "being appropriate."

Step 1: Check What Already Exists in the Project

Priority order (highest to lowest):

1. Existing design system / component library / theme files (tailwind.config, theme.ts, CSS variables, Figma link, brand guidelines): Use them as-is; don't reinvent the wheel.
2. Existing pages in the project: Any new page should feel like it belongs to the same family.
3. Platform guidelines: Windows native apps follow Fluent / WinUI, macOS follows HIG, Android follows Material. Platform-specific materials (like Windows 11's Mica / Acrylic) are legitimate when used in their prescribed places (window background, flyout menus), not by adding blur to every single card.
4. If none of the above applies, only then do you make a scenario-based judgment.

Step 2: Determine the Scenario

Look at these signals:

Signal	Conservative	Lively
Who uses it	Employees, professionals, clients' clients	Casual players, friends, children, fans
How they use it	Long daily sessions, repetitive tasks	Occasional use, short sessions, play
Content	Tables, numbers, forms, logs, code	Images, characters, stories, achievements, interactions
Cost of error	High: money, data, contracts, production	Low: just try again
User's desired feeling	Reliable, efficient, professional, unobtrusive	Fun, surprising, personal, shareable

Step 3: Choose a Direction Based on the Scenario

Business / Productivity / Internal Tools / Data Dashboards / Developer Tools

• Color palette: Primarily neutrals (white, light gray, dark gray), with one accent color reserved for primary actions and critical states. Status colors (success/warning/error) have fixed meanings and should not be used as decoration.
• Typography: System font stack or a mature sans-serif. Use monospaced digits or font-variant-numeric: tabular-nums so columns align.
• Density: Medium to high information density, compact table row heights. Whitespace should serve grouping, not a feeling of being "premium."
• Decoration: Barely any. Small border-radius (4–8px), thin borders or very subtle shadows. No gradients, glows, glass effects, or background light spots.
• Motion: Only for feedback (loading, expand, state change) — 150–200ms. No entrance animations, hover enlarge, or parallax.
• Icons: Consistent set of outline icons (Lucide, Fluent Icons, Material Symbols). No emoji as icons.
• Copy: Direct and specific: "Save", "Export CSV", "3 records pending approval."

Entertainment / Games / Creative / Social / Children / Personal Interests

• Color palette: Can be vibrant, bold, colorful, and memorable. Thematic color schemes, gradients, and illustrated backgrounds are all welcome.
• Typography: Headings can use expressive display fonts, but body text must remain readable.
• Decoration: Illustrations, stickers, textures, characters, hand-drawn elements are all fair game, but they must be thematic — not a generic "cool" effect slapped on. A pixel-art game should look pixel-art; a fairy-tale theme should feel like a fairy tale, not a uniform purple neon style.
• Motion: Can be richer: elastic, particle, celebration animations, sound effects — rewarding user actions.
• Copy: Can have personality, voice, and inside jokes.

The Middle Ground

Consumer-facing utility products (habit trackers, to-do lists, calendars, fitness logs), portfolios, and product landing pages: Start with a restrained, usability-first base. Add personality in select places (empty states, completion moments, brand color, illustrations).

Lively does not mean the AI default aesthetic. Glassmorphism, purple-blue gradients, and neon light spots — even in entertainment contexts — are still just "generic AI style," not that product's unique style. Good lively design is thematic.

When in Doubt: Ask the User

When the scenario isn't clear, or the user's needs naturally allow multiple approaches, ask first, then build. Ask concretely, offering directions the user can choose from — not a vague "What style do you like?":

✓ "For this tool's style, which do you prefer?
   A. Clean & professional: light background, neutrals, compact tables — like Linear / Notion
   B. Friendly & relaxed: rounded shapes, soft colors, a few illustrations — like Duolingo's settings page
   C. Bold personality: dramatic colors and motion, great for showcase or entertainment
   If you're not sure, I'll go with A for now."

If your environment supports live rendering, you can also create two or three small mockups (the same interface with different colors and fonts) for the user to compare.

Don't ask when it's unnecessary: If the user has already described the purpose ("for the company's finance team"), the project already has an established style, or the requirement is obvious ("build a Tetris mini-game"), just go ahead and implement. Mention your chosen direction in the output so the user can correct you if needed.

Step 4: Self-Check After Building

Ask yourself for every decorative element on the interface: If I remove it, what does the user lose? If the answer is "nothing," and this is a tool interface, remove it.

Go through this checklist:

• Search your code for backdrop-filter, linear-gradient, box-shadow (colored glows), animation, and emoji. Is each instance intentional?
• Is the accent color used only for primary actions and critical states, or is it everywhere?
• Take a screenshot and look at it (background-friendly): What catches your eye first — the content and primary action, or the decoration?
• Put yourself in the user's shoes: If they open this for eight hours a day / ten minutes of play, does this style feel appropriate?

Boundaries

• If the user explicitly requests a certain style ("Make it cyberpunk," "Go all out on the flashy effects"), follow their request, even for a tool.
• If the user provides a reference image, reference website, or brand guidelines, defer to those.
• Demo, marketing, and showcase pages can be more expressive than everyday tools, but they still need to align with the brand and audience.

Checklist

• Does the project have an existing design system, theme, or existing pages? Am I following them?
• What's the scenario? Who uses it, how long, and what's the cost of error?
• If the scenario was unclear, did I ask the user with concrete options?
• Tool interface: no glassmorphism, purple-blue gradients, neon glows, light spots, emoji icons, or unnecessary animations?
• Entertainment interface: thematic personality, not a gray table or generic AI flashy style?
• Is the accent color used only where it belongs?
• Can I justify every decorative element's purpose?