design-taste-frontend-v1

Generates opinionated React and Tailwind frontend code following anti-generic design rules and motion patterns.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/w0lzard/Wolzard-s-Marketplace --skill design-taste-frontend-v1-w0lzard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend-v1
Source: https://github.com/w0lzard/Wolzard-s-Marketplace/tree/main/plugins/personal-skills/skills/design-taste-frontend-v1
Command: npx skills add https://github.com/w0lzard/Wolzard-s-Marketplace --skill design-taste-frontend-v1-w0lzard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to look generic: centered heroes, purple gradients, Inter font, three-card layouts, and static components. This Skill encodes a strict set of design engineering rules, bias corrections, and motion patterns so generated React/Next.js interfaces look deliberately designed rather than templated. ## Core Features & Use Cases - Tunable Design Dials: Three baseline parameters (DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY) drive layout asymmetry, animation intensity, and information density across all generated UI. - Anti-Slop Rulebook: Bans common AI tells such as Inter font, neon glows, pure black, 3-column card rows, generic placeholder names, and Unsplash links, replacing them with concrete alternatives. - Bento Grid Motion Specs: Provides five card archetypes with Framer Motion spring physics, perpetual micro-interactions, and performance guardrails like Client Component isolation. - Use Case: Ask for a SaaS dashboard landing page and receive a Next.js implementation with asymmetric bento grids, staggered reveals, skeleton loading states, and a curated font pairing instead of a default-looking template. ## Quick Start Build a pricing page for my SaaS app using the design-taste-frontend-v1 guidelines with high design variance and moderate motion.

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 in favor of Geist or Satoshi, limit accent colors to one desaturated hue, forbid centered hero layouts, and replace 3-column card rows with asymmetric grids. This Skill encodes those rules as enforceable generation directives.

How to add Framer Motion animations without hurting React performance?

Use useMotionValue and useTransform outside the React render cycle instead of useState for continuous animations. Isolate perpetual motion loops in memoized Client Components, animate only transform and opacity, and wrap dynamic lists in AnimatePresence.

Does this work with Tailwind CSS v4 projects?

Yes, but the Skill enforces a version check against package.json first. For Tailwind v4 it requires @tailwindcss/postcss or the Vite plugin instead of the legacy tailwindcss PostCSS plugin, and it avoids v4-only syntax in v3 projects.

Can I use shadcn/ui components with these design rules?

Yes, shadcn/ui is permitted but never in its default state. The rules require customizing border radii, colors, and shadows so components match the project's specific aesthetic rather than the stock theme.

Why should hero sections avoid h-screen in mobile layouts?

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