anti default design

Modern UI design often suffers from "LLM average"—a sterile, repetitive aesthetic born from training data probability. This skill breaks that cycle by decoupling visual style from structural composition. It forces variance into your frontend work by injecting verifiable entropy into the design process while keeping the brand's core identity fixed.

What it does

• Fixes the register by extracting physical materials, hue families, and lettering traditions from your brief before any design begins.
• Injects entropy using a real Bash-based roll script to generate structural, compositional, and motion constraints.
• Synthesizes a design contract that maps rolled constraints onto the fixed brand register, ensuring uniqueness without losing coherence.
• Enforces mobile-first implementation with a requirement that signature elements must survive responsive transitions.
• Lints the output using a specialized script to detect and eliminate "default" design fingerprints like centered hero blocks or generic card layouts.

How it works

1. Brief extraction. The agent identifies the materials, colors, and voice of the subject.
2. Bash roll. It executes scripts/roll.sh to get verifiable, non-arbitrary skeleton constraints.
3. Contract generation. It writes a docs/design-direction.md file pinning fonts, palettes, and density rules.
4. Execution. It builds the UI phone-first, strictly following the pinned contract.
5. Validation. It runs scripts/lint.sh to ensure no generic LLM patterns leaked into the code.

Frameworks & tools

Works with any frontend stack including React, Vue, Svelte, Tailwind CSS, and vanilla HTML/CSS. Requires a shell environment to execute the entropy and linting scripts.

Why this beats prompting it yourself

Prompting an LLM to "be creative" just shifts the mean of the distribution to a different cliché. This skill uses external entropy and a rigid design contract to ensure the agent cannot retreat to safe, average UI patterns.

Use cases

• Building a landing page for a brand that needs to look artisanal or specific rather than "tech-startup-generic."
• Redesigning legacy interfaces that feel dated or templated.
• Rapidly prototyping diverse UI directions for a single brief to explore structural variance.
• Ensuring design consistency across a team by pinning direction in a markdown contract before coding.

Known limitations

Requires a functional Bash environment to run the scripts. Not suitable for projects that must strictly follow an existing, rigid enterprise design system or OS-native human interface guidelines.