Anti generic ui

Anti-Generic UI

This skill exists because AI-generated portfolio interfaces often become visually acceptable but strategically dead.

They are not always ugly.

They are often worse:

• generic
• familiar in the wrong way
• over-smoothed
• interchangeable
• visually current but identity-empty

Core Rule

A portfolio should not look like it was assembled from default startup instincts.

It should feel selected, not auto-completed.

Common Generic Patterns

Watch for these:

• dark page + glow + gradient + glass with no real point of view
• endless equal-weight cards
• soft startup copy attached to premium styling
• default hero + metrics strip + project cards + testimonial rhythm
• AI-futurist styling with weak project meaning
• polished surfaces doing the work of hierarchy

Visual Red Flags

If you see several of these at once, the UI is drifting toward generic:

• every section uses the same composition logic
• everything looks "nice" but nothing feels necessary
• type contrast exists, but hierarchy is still soft
• accents are trendy rather than meaningful
• cards multiply instead of being edited
• the interface wants admiration more than clarity

Questions To Ask

1. Could this portfolio belong to 30 different builders with only the copy changed?
2. Is the visual system helping identity, or hiding the lack of identity?
3. Is the UI selected, or merely assembled from current-good-looking ingredients?
4. Does the page have one or two real signature moves, or only many familiar good practices?
5. Is the layout proving authorship, or just proving competence?

Correction Rules

When the UI feels generic:

• remove one repeated pattern before inventing a new one
• increase contrast between section roles, not only type sizes
• choose fewer, stronger visual ideas and let them carry more weight
• let one section become structurally distinct instead of keeping uniform rhythm everywhere
• reduce decorative effects before adding new styling layers
• strengthen project hierarchy instead of polishing every surface equally
• cut one card, badge row, or glow treatment whenever the page starts admiring itself

Before / After Pattern Shifts

Use these shifts when the page looks competent but interchangeable:

Before

• same card grid across multiple sections
• equal visual weight for proof, biography, and secondary details
• glow, blur, or glass doing the work of emphasis

After

• one section becomes denser, one becomes calmer, one becomes more direct
• proof gets stronger hierarchy than background credibility content
• emphasis comes from structure, contrast, and selection before effects

Before

• dark luxury styling with no point-of-view move
• premium surfaces attached to startup-default layout logic
• every block looks polished enough to survive, so nothing gets cut

After

• one unmistakable signature move
• one clear hierarchy decision that shapes the page
• one intentional removal pass that makes the page feel edited

Practical Correction Sequence

If you are fixing a generic interface, do it in this order:

1. identify the most repeated visual pattern
2. remove or break that pattern once
3. decide which section deserves the strongest structural identity
4. reduce decorative styling in one area by 20 to 30 percent
5. strengthen proof hierarchy before polishing supporting sections
6. stop when the page feels more selective, not merely more elaborate

What To Favor

• controlled asymmetry
• section-specific identity
• edited card count
• visual hierarchy that mirrors content hierarchy
• details that feel tied to the builder, not the market

What To Avoid

• trend compliance mistaken for taste
• premium styling without narrative function
• cloned SaaS section logic
• decorative density standing in for identity
• AI-made smoothness with no authored edge

Success Condition

This skill succeeds when the portfolio feels:

• unmistakably authored
• controlled
• selective
• hard to confuse with market-default AI portfolio design