design-taste-frontend

Generates React and Next.js interfaces with enforced design rules, motion physics, and anti-generic styling constraints.

Updated May 2, 2026
One-click install
npx skills add https://github.com/FadhilAlif/jejak_karier --skill design-taste-frontend-fadhilalif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/FadhilAlif/jejak_karier/tree/main/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/FadhilAlif/jejak_karier --skill design-taste-frontend-fadhilalif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to produce generic, clichéd interfaces with centered heroes, purple gradients, Inter fonts, and static states. This Skill enforces metric-based design rules and strict component architecture so generated UI code avoids these default AI biases. ## Core Features & Use Cases - Bias-Corrected Design Rules: Bans common AI tells such as neon glows, pure black, 3-column card rows, generic names, and Unsplash links, while enforcing deterministic typography and single-accent color palettes. - Configurable Design Dials: Drives output through three tunable baselines (DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY) that control layout asymmetry, animation depth, and information density. - Motion & Performance Guardrails: Specifies Framer Motion spring physics, staggered orchestration, hardware-accelerated transforms, and mandatory loading, empty, and error states. - Use Case: Ask for a SaaS dashboard bento grid and receive Next.js code with perpetual micro-interactions, isolated client components, diffusion shadows, and mobile-safe responsive fallbacks instead of a generic card layout. ## Quick Start Use the design-taste-frontend skill to build a Next.js landing page with an asymmetric hero, bento grid features, and Framer Motion animations.

Frequently Asked Questions about design-taste-frontend

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

FAQPage Schema
How do I generate a non-generic Next.js landing page with AI?

Request the page with this Skill active and it applies asymmetric layouts, single-accent neutral palettes, and banned-pattern filters automatically. The output avoids centered heroes, gradient text, and generic three-card feature rows by default.

How to add Framer Motion animations without hurting mobile performance?

Use useMotionValue and useTransform outside the React render cycle instead of useState for continuous animations. Animate only transform and opacity, and isolate perpetual motion loops in memoized client components.

Does this work with Tailwind CSS v3 and v4 projects?

Yes, but the Skill checks package.json first and locks syntax to the installed version. For v4 it requires @tailwindcss/postcss or the Vite plugin instead of the legacy tailwindcss PostCSS plugin.

Can I use shadcn/ui components with this design system?

Yes, shadcn/ui is allowed but never in its default state. You must customize radii, colors, and shadows to match the project aesthetic defined by the design dials and palette constraints.

Why should hero sections use min-h-[100dvh] instead of h-screen?

h-screen causes layout jumping on mobile browsers like iOS Safari because the viewport height changes when toolbars hide. min-h-[100dvh] tracks the dynamic viewport and keeps full-height sections stable.

When should I use GSAP or Three.js instead of Framer Motion?

Use GSAP or Three.js only for isolated full-page scrolltelling or canvas backgrounds, wrapped in useEffect cleanup blocks. Never mix them with Framer Motion in the same component tree; Framer Motion remains the default for UI interactions.