stacks-design-taste

Enforce context-aware design taste rules for Stacks frontend output.

2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/stacksjs/status --skill stacks-design-taste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-design-taste
Source: https://github.com/stacksjs/status/tree/main/.claude/skills/stacks-design-taste
Command: npx skills add https://github.com/stacksjs/status --skill stacks-design-taste

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about stacks-design-taste

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

FAQPage Schema
How do I prevent generic AI slop frontend design in Stacks applications?

To prevent generic AI slop in Stacks apps, enforce context-aware design taste rules that ban overused clichés like purple gradients and default Inter fonts. This ensures frontend output aligns with project briefs and audience needs using Stacks UI components.

How do I build a non-templated Stacks landing page for technical audiences?

Building a non-templated Stacks landing page requires reading project context like audience and vibe words before writing code. You then apply configurable design dials for variance and motion intensity using stx templates and Crosswind utilities.

Does the stacks-design-taste skill work with external design systems or JSX?

The stacks-design-taste skill does not work with external design systems or JSX. It enforces a Stacks-only stack requirement, mandating native tooling like stx templates, Crosswind utilities, and Stacks UI components to maintain strict design guardrails.

What are the pre-flight guardrails for frontend design in Stacks?

Pre-flight guardrails for Stacks frontend design are mandatory checks that ban common AI design clichés, enforce accessibility standards, and ensure layout consistency. They prevent issues like wrapped CTAs, repeated section layouts, and overused serif fonts.

Can I configure visual density and motion intensity for Stacks UI components?

You can configure visual density and motion intensity for Stacks UI components using configurable design dials. These dials tune variance and aesthetic intensity to match project needs, ranging from minimalist B2B SaaS to experimental agency portfolios.

Why does my LLM-generated Stacks frontend look identical to other projects?

LLM-generated Stacks frontends look identical because models default to lazy templated AI slop like identical 3-column feature cards and centered heroes. Enforcing context-aware brief inference and strict design taste rules eliminates this generic output.