design-taste-frontend-v1

Generates React and Next.js frontend interfaces following v1 design, motion, and layout rules.

1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/tanveerriaz/Skillz --skill design-taste-frontend-v1-tanveerriaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/tanveerriaz/Skillz/tree/main/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/tanveerriaz/Skillz --skill design-taste-frontend-v1-tanveerriaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code often looks generic, with clichéd layouts, default fonts, and missing interaction states. This Skill preserves the original v1 design rule set so projects that depend on its exact visual behavior keep producing consistent, distinctive interfaces. ## Core Features & Use Cases - Design Engineering Directives: Enforces deterministic typography, single-accent color calibration, asymmetric layouts, and bans common AI design tells like Inter font, purple gradients, and 3-column card rows. - Motion & Interaction Specs: Defines Framer Motion spring physics, perpetual micro-interactions, staggered orchestration, and a Bento 2.0 dashboard paradigm with five animated card archetypes. - Performance Guardrails: Mandates transform/opacity-only animations, isolated Client Components for perpetual motion, min-h-[100dvh] viewport safety, and dependency verification against package.json. - Use Case: A team maintaining a product originally built with the v1 design rules uses this Skill to generate new pages that match the established visual system exactly, rather than migrating to the v2 rewrite. ## Quick Start Ask the agent to build a React dashboard page using the v1 design-taste rules with your brand colors and content.

Frequently Asked Questions about design-taste-frontend-v1

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

FAQPage Schema
How do I make AI-generated React UI look less generic?▼

Apply explicit design constraints: ban default fonts like Inter, limit accents to one desaturated color, forbid centered hero layouts and 3-column card rows, and require loading, empty, and error states. This Skill encodes those rules as enforceable directives.

When should I use design-taste-frontend-v1 instead of v2?▼

Use v1 only when a project depends on its exact visual behavior and you need backward compatibility. For new projects, the current default is the v2 rewrite, which is a substantial redesign of the rule set.

Does this work with Tailwind CSS v3 and v4?▼

Yes, but the Skill requires checking package.json first and locking syntax to the installed version. For v4 it forbids the tailwindcss PostCSS plugin and requires @tailwindcss/postcss or the Vite plugin instead.

Can I mix Framer Motion with GSAP or Three.js in one component?▼

No. The rules prohibit mixing GSAP or Three.js with Framer Motion in the same component tree. Framer Motion handles UI interactions, while GSAP or Three.js are reserved for isolated scrolltelling or canvas backgrounds with useEffect cleanup.

Why does the Skill ban h-screen for hero sections?▼

h-screen causes layout jumping on mobile browsers like iOS Safari because the viewport height changes as browser chrome hides. The rules require min-h-[100dvh] for full-height sections to keep layouts stable.