design-taste-frontend

Generates landing pages, portfolios, and redesigns with anti-default design rules and pre-flight checks.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill design-taste-frontend-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/design-taste-frontend
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill design-taste-frontend-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to fall back on the same templated aesthetics: purple gradients, centered heroes, three equal feature cards, and generic glassmorphism. This Skill forces the agent to read the brief first, infer the right design direction, and ship interfaces that do not look like default AI output. ## Core Features & Use Cases - Brief Inference and Design Read: Analyzes page kind, vibe words, references, audience, and constraints before writing code, then declares a one-line design read. - Three-Dial Configuration: Tunes DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY based on the brief, with presets for SaaS landings, portfolios, editorial sites, and public-sector services. - Design System Mapping: Routes briefs to official packages (Fluent, Material, Carbon, Polaris, GOV.UK, shadcn/ui, Tailwind v4) instead of hand-rolled imitations, and honestly labels aesthetic approximations. - Hard Layout and Accessibility Rules: Enforces hero viewport fit, eyebrow restraint, CTA contrast checks, palette locks, and a mechanical pre-flight audit before shipping. - Use Case: Ask for a premium consumer cookware landing page and receive a React/Tailwind build with a non-default palette, real image assets, varied section layouts, and a passing pre-flight check. ## Quick Start Ask the agent to build a landing page or portfolio from your brief, for example: create a minimalist B2B SaaS landing page for a code review tool with a Linear-style aesthetic.

Frequently Asked Questions about design-taste-frontend

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

FAQPage Schema
How do I stop AI-generated landing pages from looking templated?

Start with a brief inference step that reads page kind, vibe words, audience, and constraints before coding. Then set variance, motion, and density dials, avoid default palettes like AI-purple gradients, and run a pre-flight audit on layout repetition and contrast.

What design system should I use for a SaaS landing page?

For modern SaaS marketing pages, Tailwind v4 utilities with shadcn/ui components is the default recommendation. Enterprise briefs map to official systems like Fluent, Carbon, or Material instead of hand-rolled recreations.

Does this approach work with Next.js and Tailwind v4?

Yes, Next.js with Server Components and Tailwind v4 is the default stack. Interactive components using Motion must be isolated client components, and Tailwind v4 requires @tailwindcss/postcss rather than the v3 PostCSS plugin.

When should I use serif fonts in web design?

Serif is discouraged as a default and only appropriate when the brand brief names a serif or the aesthetic is genuinely editorial, luxury, or heritage. For emphasis inside headlines, use italic or bold of the same font family rather than mixing families.

Why do AI-generated hero sections break on mobile?

Common causes are using h-screen instead of min-h-[100dvh], oversized headline fonts, and excessive top padding. The fix is capping hero top padding at pt-24, limiting headlines to two lines, and planning font scale together with asset size.

What are the limitations of this frontend design approach?

It targets landing pages, portfolios, and redesigns, not dashboards, data tables, or multi-step product UI. It also depends on available image-generation tools or real photography sources, since text-only pages are treated as incomplete work.