design-taste-frontend

Generates non-templated frontend designs for landing pages, portfolios, and redesigns using inferred design direction.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/yehezkieldio/topaz --skill design-taste-frontend-yehezkieldio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/yehezkieldio/topaz/tree/main/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/yehezkieldio/topaz --skill design-taste-frontend-yehezkieldio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to fall back on the same templated look: purple gradients, centered heroes, three equal feature cards, and Inter on slate. This Skill forces the agent to read the brief first, infer the right design direction, and ship landing pages, portfolios, and redesigns that do not look like default LLM output. ## 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 real official packages (Fluent, Material, Carbon, Polaris, GOV.UK Frontend, shadcn/ui, Tailwind v4) when the brief matches a known system instead of hand-rolling CSS. - Anti-Slop Guardrails and Pre-Flight Audit: Enforces hard rules on typography, color palettes, hero layout, eyebrows, bento grids, CTA contrast, and responsive behavior, with a mechanical pre-flight check before shipping. - Use Case: Ask for a redesign of a premium cookware landing page and receive a Tailwind v4 + Next.js page with a non-default palette, asymmetric hero, real image assets, and a passed pre-flight checklist. ## Quick Start Ask the agent to design a landing page or portfolio from your brief, for example: redesign my SaaS landing page to feel Linear-style minimalist and avoid generic AI design patterns.

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, avoid default patterns like purple gradients and centered heroes, and run a pre-flight audit on typography, color, and layout rules.

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

For modern SaaS marketing sites, Tailwind v4 utilities with shadcn/ui components is the default recommendation. If the brief matches an established ecosystem like Microsoft, Google, IBM, or Shopify, use the official Fluent, Material, Carbon, or Polaris packages instead of recreating their CSS.

Does this approach work with Next.js and Tailwind v4?▼

Yes, Next.js with React Server Components and Tailwind v4 is the default stack. Interactive components using Motion or scroll listeners must be isolated client components, and Tailwind v4 requires @tailwindcss/postcss rather than the v3 PostCSS plugin.

When should I use a serif font in web design?▼

Serif fonts are 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 premium consumer brands, sans-serif display fonts like Geist Display or Cabinet Grotesk are the correct default.

Why do AI-generated hero sections look broken on mobile?▼

Common causes include using h-screen instead of min-h-[100dvh], which breaks on iOS Safari, oversized headline fonts that push CTAs below the fold, and missing explicit mobile collapse rules for multi-column layouts. Hero headlines should stay within two lines with CTAs visible without scrolling.

What are the limitations of this frontend design approach?▼

The skill explicitly excludes dashboards, data tables, and multi-step product UI, focusing only on landing pages, portfolios, and redesigns. It also depends on available image-generation tools or real photography sources, since text-only pages are treated as incomplete work.