Skip to content
Skillpedia
Interfaces (UI/UX)101k · #777

design-taste-frontend-v1

Lets your agent use an older version of a design tool. It's only useful if you need the exact same behavior as before.

What it does

This tool helps create website or app designs. It defines how visual elements should be arranged and how they move and interact, following specific rules to ensure a modern and functional look.

When to use it

  • ✓When starting a new interface design project.
  • ✓When you want to ensure the design follows the latest trends.
  • ✓To define the appearance and behavior of interactive elements.

Example of what to ask your AI

“Create a homepage layout with a large title, a 'Learn More' button, and an image on the side, using neutral colors with a touch of vibrant blue.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/nexu-io/open-design/blob/main/skills/taste-skill-v1/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/nexu-io/open-design/blob/main/skills/taste-skill-v1/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool uses a set of predefined rules to adjust aspects like colors, fonts, spacing, and motion. It also checks if necessary code libraries are installed before generating the design.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add nexu-io/open-design --skill design-taste-frontend-v1

Or download just the file:

curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/skills/taste-skill-v1/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

High-Agency Frontend Skill

1. ACTIVE BASELINE CONFIGURATION

  • DESIGN_VARIANCE: 8 (1=Perfect Symmetry, 10=Artsy Chaos)
  • MOTION_INTENSITY: 6 (1=Static/No movement, 10=Cinematic/Magic Physics)
  • VISUAL_DENSITY: 4 (1=Art Gallery/Airy, 10=Pilot Cockpit/Packed Data)

AI Instruction: The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.

2. DEFAULT ARCHITECTURE & CONVENTIONS

Unless the user explicitly specifies a different stack, adhere to these structural constraints to maintain consistency:

  • DEPENDENCY VERIFICATION [MANDATORY]: Before importing ANY 3rd party library (e.g. framer-motion, lucide-react, zustand), you MUST check package.json. If the package is missing, you MUST output the installation command (e.g. npm install package-name) before providing the code. Never assume a library exists.
  • Framework & Interactivity: React or Next.js. Default to Server Components (RSC).
    • RSC SAFETY: Global state works ONLY in Client Components. In Next.js, wrap providers in a "use client" component.
    • INTERACTIVITY ISOLATION: If Sections 4 or 7 (Motion/Liquid Glass) are active, the specific interactive UI component MUST be extracted as an isolated leaf component with 'use client' at the very top. Server Components must exclusively render static layouts.
  • State Management: Use local useState/useReducer for isolated UI. Use global state strictly for deep prop-drilling avoidance.
  • Styling Policy: Use Tailwind CSS (v3/v4) for 90% of styling.
    • TAILWIND VERSION LOCK: Check package.json first. Do not use v4 syntax in v3 projects.
    • T4 CONFIG GUARD: For v4, do NOT use tailwindcss plugin in postcss.config.js. Use @tailwindcss/postcss or the Vite plugin.
  • ANTI-EMOJI POLICY [CRITICAL]: NEVER use emojis in code, markup, text content, or alt text. Replace symbols with high-quality icons (Radix, Phosphor) or clean SVG primitives. Emojis are BANNED.
  • Responsiveness & Spacing:
    • Standardize breakpoints (sm, md, lg, xl).
    • Contain page layouts using max-w-[1400px] mx-auto or max-w-7xl.
    • Viewport Stability [CRITICAL]: NEVER use h-screen for full-height Hero sections. ALWAYS use min-h-[100dvh] to prevent catastrophic layout jumping on mobile browsers (iOS Safari).
    • Grid over Flex-Math: NEVER use complex flexbox percentage math (w-[calc(33%-1rem)]). ALWAYS use CSS Grid (grid grid-cols-1 md:grid-cols-3 gap-6) for reliable structures.
  • Icons: You MUST use exactly @phosphor-icons/react or @radix-ui/react-icons as the import paths (check installed version). Standardize strokeWidth globally (e.g., exclusively use 1.5 or 2.0).

3. DESIGN ENGINEERING DIRECTIVES (Bias Correction)

LLMs have statistical biases toward specific UI cliché patterns. Proactively construct premium interfaces using these engineered rules:

Rule 1: Deterministic Typography

  • Display/Headlines: Default to text-4xl md:text-6xl tracking-tighter leading-none.
    • ANTI-SLOP: Discourage Inter for "Premium" or "Creative" vibes. Force unique character using Geist, Outfit, Cabinet Grotesk, or Satoshi.
    • TECHNICAL UI RULE: Serif fonts are strictly BANNED for Dashboard/Software UIs. For these contexts, use exclusively high-end Sans-Serif pairings (Geist + Geist Mono or Satoshi + JetBrains Mono).
  • Body/Paragraphs: Default to text-base text-gray-600 leading-relaxed max-w-[65ch].

Rule 2: Color Calibration

  • Constraint: Max 1 Accent Color. Saturation < 80%.
  • THE LILA BAN: The "AI Purple/Blue" aesthetic is strictly BANNED. No purple button glows, no neon gradients. Use absolute neutral bases (Zinc/Slate) with high-contrast, singular accents (e.g. Emerald, Electric Blue, or Deep Rose).
  • COLOR CONSISTENCY: Stick to one palette for the entire output. Do not fluctuate between warm and cool grays within the same project.

Rule 3: Layout Diversification

…

FAQ

What are 'baseline configurations'?

These are default settings that define the overall design style, such as the level of symmetry, motion intensity, and the amount of elements on the screen.

Why not use emojis?

The tool prioritizes high-quality icons or simple graphic elements instead of emojis to maintain a professional and consistent look.

How does the tool handle different screen sizes?

It uses specific patterns to ensure the design adapts well to different devices, like phones and computers, avoiding display issues.

Details

Original description by the author

The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

repo: nexu-io/open-design

Popularity

GitHub stars
101k
Ranking position
#777
License
Apache-2.0
Updated
10/16/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills