design-taste-frontend

Enforce typography, color, layout, and interaction-state standards for React or Next.js interfaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents generic, cliché UI patterns by enforcing metric-based layout rules, interaction state coverage, and deterministic component architecture for modern frontend work.

Core Features & Use Cases

  • Premium interface engineering: Applies fixed design baselines and color/typography/layout constraints to keep output consistent and institutionally styled.
  • Interaction-cycle completeness: Requires loading, empty, error, and tactile feedback states rather than only “happy path” screens.
  • Motion and performance guardrails: Directs when and how to use Framer Motion (or motion-like effects) while avoiding GPU and layout-jank pitfalls.

Quick Start

Use the design-taste-frontend skill to generate a Tailwind + Next.js UI spec that follows the baseline values and includes loading, empty, error, and active interaction states.

Frequently Asked Questions about design-taste-frontend

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

FAQPage Schema
How do I standardize UI design patterns to avoid generic-looking Next.js interfaces?▼

Ensure interaction state coverage by explicitly requiring loading, empty, error, and tactile feedback states. This interaction-cycle completeness prevents UI flows from only rendering happy-path screens and handles edge cases gracefully.

Does Tailwind work with strict RSC versus client component isolation rules?▼

Tailwind works with strict RSC versus client isolation by enforcing deterministic component architecture. It satisfies strict constraints on Tailwind usage, ensuring hardware-accelerated animation practices and performance-safe UI behaviors across product screens.

What is the best way to use Framer Motion without causing layout jank in React?▼

The best way to use Framer Motion safely is by following motion and performance guardrails. These rules direct when and how to apply hardware-accelerated animation practices while avoiding GPU pitfalls and layout jank in Tailwind interfaces.

Can I generate a complete UI spec that includes error and loading states for Tailwind?▼

You can generate a Tailwind and Next.js UI spec that follows baseline values and includes loading, empty, error, and active interaction states. This ensures deterministic component structuring and metric-based layout rules for modern frontend work.