void-frontend-design

Enforces anti-AI-slop UI design discipline with density-first layouts, 3-size typography, and mobile-first dual-viewport verification.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-frontend-design-voidcorp-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: void-frontend-design
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-frontend-design
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-frontend-design-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated UI tends to look generic: gradient backgrounds, low information density, decorative motion, and inconsistent typography. This Skill encodes a concrete design discipline so interfaces built by coding agents stop reading as machine-generated and instead follow structural, typographic, and motion rules. ## Core Features & Use Cases - Banned-pattern enforcement: Blocks AI-tell patterns such as gradient text, glassmorphism, side-stripe borders, hero-metric templates, and cream-colored body backgrounds, plus banned marketing copy phrases. - Structural design rules: Mandates information architecture before visuals, density-first layouts, a 3-size type token system, one primary action color per view, and motion under 250ms with ease-out curves. - Mobile-first dual-quality: Requires layouts to start at 360-390px and pass screenshot review on both mobile and desktop viewports before merge, with components composed from @repo/ui (Radix/shadcn) rather than hand-rolled primitives. - Use Case: When asked to build a dashboard page, the Skill guides the agent to define hierarchy and primary action first, use tabular metrics instead of card grids, apply the 3-token type system, and verify both viewports with screenshots. ## Quick Start Ask the agent to build or modify a UI screen, such as "redesign the settings page following the frontend design discipline," and the Skill's rules apply automatically.

Frequently Asked Questions about void-frontend-design

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

FAQPage Schema
How do I prevent AI-generated UI from looking generic?▼

Apply a banned-pattern list that rejects gradient text, glassmorphism, hero-metric templates, and decorative animations over 250ms. Combine this with information-architecture-first design, density-first layouts, and a strict 3-size typography token system.

What typography rules should a design system enforce?▼

Limit the system to three type sizes (display, heading, body) and create variation through weight and color instead of arbitrary pixel sizes. Cap body line length at 65-75ch, keep display clamp() under 6rem, and avoid system-ui as the primary typeface.

Does this work with shadcn and Radix UI components?▼

Yes, components are composed from @repo/ui, which is a shadcn-style library built on Radix primitives with Tailwind tokens. Hand-rolled UI primitives like styled divs with click handlers are explicitly banned.

How is mobile-first design verified before merging?▼

Layouts must start at 360-390px and be progressively enhanced wider, never desktop-first. A viewport-screenshot-gate hook fails pull requests that lack both mobile and desktop screenshots.

When can banned visual patterns like gradients be overridden?▼

Brand-specific overrides are allowed when documented in the project's DESIGN.md file with justification. The default is rejection; the brand contract upstream decides exceptions, not the individual component.

What are the limitations of this design discipline?▼

It does not decide brand identity, which lives in the consumer project's DESIGN.md, and it does not perform post-build audits, which belong to the separate ui-review skill. It is a build-time floor, not an audit-time ceiling.