design-taste-frontend

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to fall back on the same templated aesthetics: AI-purple gradients, centered heroes, generic card grids, and default fonts. This Skill forces the agent to read the brief first, infer the right design direction, and ship interfaces that do not look machine-generated. ## 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, shadcn/ui, Tailwind v4, GOV.UK Frontend) when the brief matches a real system, and gives honest implementation guidance for aesthetics like glassmorphism, bento, and brutalism. - Anti-Slop Guardrails and Pre-Flight Audit: Enforces rules on typography, color palettes, hero layout, eyebrow restraint, CTA contrast, and section-layout diversity, with a mechanical pre-flight check before shipping. - Use Case: Ask for a redesign of a premium cookware landing page and receive a React/Tailwind implementation with a deliberate non-default palette, asymmetric layout, real image assets, and a passing pre-flight audit. ## Quick Start Redesign my SaaS landing page so it looks like a Linear-style minimalist site and audit it against the pre-flight checklist before shipping.

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 configure variance, motion, and density dials, avoid default palettes like AI-purple gradients, and run a pre-flight audit checking eyebrow count, layout repetition, and CTA contrast.

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

Match the system to the brief: shadcn/ui or Tailwind v4 for modern SaaS, Fluent for Microsoft-style enterprise, Carbon for IBM-style B2B, and GOV.UK Frontend or USWDS for public-sector sites. Use one official system per project rather than mixing libraries.

Does this skill 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 must be isolated client components, and Tailwind v4 requires @tailwindcss/postcss or the Vite plugin instead of the legacy PostCSS setup.

When should I not use this frontend design skill?

It is scoped to landing pages, portfolios, and redesigns, not dashboards, data tables, or multi-step product UI. For dense application interfaces, use a component-driven design system workflow instead of the marketing-site rules defined here.

Why does my AI-generated hero section look broken on mobile?

Common causes are using h-screen instead of min-h-[100dvh], oversized headline fonts, and missing mobile collapse rules for multi-column layouts. The skill mandates viewport-stable heights, capped hero font scales, and explicit per-section mobile fallbacks.