design-taste-frontend

Generates landing pages, portfolios, and redesigns with brief-driven design systems and anti-default rules.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/optimaxin/Tredev_Gems --skill design-taste-frontend-optimaxin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/optimaxin/Tredev_Gems/tree/main/agent/skills/design-taste-frontend
Command: npx skills add https://github.com/optimaxin/Tredev_Gems --skill design-taste-frontend-optimaxin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to look templated: AI-purple gradients, centered heroes, three equal feature cards, and generic glassmorphism. This Skill forces the agent to read the brief first, infer the right design direction, and ship interfaces that avoid those default patterns. ## Core Features & Use Cases - Brief Inference and Design Read: Analyzes page kind, vibe words, references, audience, and constraints, then declares a one-line design read before writing any code. - Three-Dial Configuration: Tunes DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY based on the brief, with presets for SaaS landings, portfolios, editorial sites, and public-sector services. - Design System Mapping: Selects official packages (Fluent, Material, Carbon, Polaris, GOV.UK Frontend, shadcn/ui, Tailwind v4) when the brief matches a real system, and gives honest implementation guidance for aesthetics like bento, brutalism, or glassmorphism. - Pre-Flight Layout Discipline: Enforces hard rules on hero sizing, eyebrow restraint, CTA contrast, palette consistency, and section-layout diversity. - Use Case: Ask for a redesign of a public-sector service site and the agent will reach for GOV.UK Frontend or USWDS with low-variance, low-motion dials instead of inventing custom CSS. ## Quick Start Redesign my SaaS landing page so it feels Linear-style minimalist and does not look like a generic AI template.

Frequently Asked Questions about design-taste-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated landing pages not look templated?

Start with a brief inference step that identifies page kind, audience, and vibe before writing code. Then set variance, motion, and density dials, pick a real design system when one fits, and audit against known AI defaults like purple gradients and centered heroes.

What design system should I use for a SaaS landing page?

For indie and small-team SaaS, Tailwind v4 utilities with shadcn/ui components is the default. Enterprise briefs map to official systems like Fluent, Carbon, or Material, and public-sector sites should use GOV.UK Frontend or USWDS.

Does this approach work with Next.js Server Components?

Yes. Static layouts render as Server Components, while any component using Motion, scroll listeners, or pointer physics must be an isolated leaf with 'use client' at the top. Global state providers also require a client wrapper.

When should I avoid using serif fonts in web design?

Serif is discouraged as a default and only appropriate when the brand brief names a serif or the aesthetic is genuinely editorial, luxury, or heritage. For creative agencies, portfolios, and modern brands, sans-serif display fonts like Geist or Cabinet Grotesk are the correct default.

Why do AI-generated heroes overflow the viewport?

Heroes overflow when headlines exceed two lines, subtext passes 20 words, or top padding exceeds pt-24. The fix is reducing font scale or cutting copy so the headline, subtext, and CTA all fit in the initial viewport without scrolling.

What are the limitations of this frontend design approach?

It explicitly excludes dashboards, data tables, and multi-step product UI, focusing only on landing pages, portfolios, and redesigns. It also requires real image assets, so without an image-generation tool or stock sources it leaves labeled placeholder slots instead of fake screenshots.