taste-skill

Generates anti-slop frontend designs for landing pages using a Three Dials configuration system.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill taste-skill-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taste-skill
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/creative/taste-skill
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill taste-skill-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? LLM-generated frontend code tends to fall back on generic defaults like purple gradients, centered dark heroes, and three-column card grids. This Skill enforces deliberate design decisions for landing pages, portfolios, and redesigns so output avoids recognizable AI patterns. ## Core Features & Use Cases - Three Dials System: Configures DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY based on brief inference, mapping vibe words and audience signals to concrete design parameters. - Design Directives & Pre-Flight Check: Applies hard rules for typography, color, layout, hero composition, and interactive states, then validates output against a mandatory checklist covering WCAG AA contrast, eyebrow counts, and theme locks. - Real Design System Mapping: Maps briefs to established systems like shadcn/ui, Radix, Carbon, Polaris, and Tailwind v4, with a companion reference for generating per-section image art direction. - Use Case: Ask for a premium SaaS landing page redesign and receive a React/Next.js + Tailwind implementation with asymmetric layouts, a locked accent palette, Motion-based spring animations, and real image placements instead of placeholder gradients. ## Quick Start Redesign my portfolio landing page to look premium and avoid generic AI design patterns.

Frequently Asked Questions about taste-skill

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

FAQPage Schema
How do I make an AI-generated landing page not look generic?▼

Use brief inference to pick design parameters before coding: set DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY based on vibe words and audience. Then enforce rules like one locked accent color, asymmetric heroes, and a maximum of one eyebrow per three sections.

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

For modern SaaS with custom components use shadcn/ui; for Tailwind-based SaaS use Tailwind v4 with dark mode support. Enterprise briefs map to Carbon or Fluent, and exactly one system should be used per project without mixing.

Does this skill work for dashboards and data tables?▼

No, the Three Dials system explicitly does not apply to data-dense surfaces like dashboards, data tables, or multi-step product UI. The skill targets landing pages, portfolios, editorial pages, and redesigns only.

Which icon libraries are recommended for React frontend projects?▼

Allowed families are Phosphor Icons, Hugeicons, Radix Icons, and Tabler Icons, with lucide-react discouraged unless already a project dependency. Pick one family per project and standardize strokeWidth globally.

Why does my hero section break on mobile viewports?▼

Using h-screen causes overflow issues on mobile browsers with dynamic toolbars. Always use min-h-[100dvh] for full-height heroes, cap top padding at pt-24 on desktop, and define explicit mobile collapse behavior per section.