stacks-design-taste

What problem does it solve?

LLM-generated frontend for Stacks applications often defaults to generic, templated "AI slop" — overused clichés like purple gradients, default Inter font, identical 3-column feature cards, and centered heroes that make every project look indistinguishable. This Skill eliminates that problem by enforcing context-aware design taste rules tailored to the Stacks stack, ensuring output matches the project's unique brief, audience, and brand instead of falling back to lazy defaults.

Core Features & Use Cases

• Brief Inference: Automatically reads project context (audience, vibe words, reference signals, brand assets) to align design direction before writing any code.
• Configurable Design Dials: Tune variance, motion intensity, and visual density to match project needs, from minimalist B2B SaaS to experimental agency portfolios.
• Pre-Flight Guardrails: Mandatory checks that ban common AI design clichés, enforce accessibility standards, and ensure layout consistency (no wrapped CTAs, no repeated section layouts, no overused serif fonts).
• Stacks-Only Stack Enforcement: Requires use of native Stacks tooling (stx templates, Crosswind utilities, Stacks UI components, Iconify icons) with no external design systems, JSX, or unsanctioned libraries.
• Use Case: Ideal for building Stacks app landing pages, developer/designer portfolios, marketing sections, or full redesigns that need to avoid generic templated aesthetics.

Quick Start

Use the stacks-design-taste skill to build a non-templated landing page for my Stacks open-source monitoring tool targeting technical engineering teams with a clean, dark tech aesthetic.