design-taste-frontend

Generates non-templated frontend interfaces for landing pages, portfolios, and redesigns using React, Next.js, and Tailwind.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill design-taste-frontend-desarrolloainia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/desarrolloainia/nuevo_circuito_mir/tree/main/frontend/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill design-taste-frontend-desarrolloainia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to look templated and generic, repeating the same purple gradients, centered heroes, and default font choices. This Skill forces the agent to read the brief first, infer the right design direction, and ship interfaces that avoid recognizable AI design clichés. ## Core Features & Use Cases - Brief Inference and Design Read: Analyzes page kind, vibe words, references, audience, and constraints before writing any code, then declares a one-line design direction. - 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) when the brief matches a real system, and gives honest implementation guidance for aesthetics like glassmorphism, bento, and brutalism. - Pre-Flight Layout Rules: Enforces hard constraints on hero sizing, eyebrow frequency, CTA contrast, palette consistency, and section layout diversity. - Use Case: Ask for a redesign of a premium consumer brand landing page and receive a React/Next.js page with a deliberate palette, real image assets, varied section layouts, and no AI-default styling. ## Quick Start Use the design-taste-frontend skill to build a landing page for my SaaS product with a minimalist Linear-style aesthetic.

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 by inferring the design direction from the brief: page kind, vibe words, audience, and references. Then set variance, motion, and density dials, pick an appropriate design system or aesthetic family, and audit the output against anti-default rules before shipping.

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

For indie and small-team SaaS marketing sites, Tailwind v4 utilities with a dark variant are the default. If the brief matches an established ecosystem, use the official package such as shadcn/ui, Radix Themes, Fluent, or Carbon instead of recreating its CSS by hand.

Does this skill work for dashboards or data-heavy product UI?▼

No. The skill explicitly scopes itself to landing pages, portfolios, editorial sites, and redesigns. Dashboards, data tables, and multi-step product interfaces are out of scope and need different density and component patterns.

Can I use Framer Motion with Next.js Server Components?▼

Yes, but any component using Motion, scroll listeners, or pointer physics must be an isolated leaf component with 'use client' at the top. Import from motion/react in new code, and use useMotionValue instead of useState for continuous values like scroll progress.

Why does the skill ban Inter and serif fonts as defaults?▼

Inter plus slate-900 and display serifs like Fraunces are the most recognizable LLM default choices, making output look AI-generated. The skill requires deliberate font selection such as Geist, Satoshi, or Cabinet Grotesk, with serif allowed only when the brand brief genuinely justifies it.

How should I handle images when no image generation tool is available?▼

Use real photography sources such as picsum.photos with descriptive seeds, or brand-provided URLs. If neither is possible, leave clearly labeled placeholder slots and tell the user which placements need real images rather than shipping fake CSS screenshots.