← ClaudeAtlas

no-medianlisted

Design or redesign product interfaces with AI using explicit constraints, references, multiple off-code variants, taste reflection, subtraction, reusable components, and real-data verification. Use for UI, landing page, TUI, prototype, component, or design-feedback work. Do not use for copy-only, data-visualization, or backend-only tasks.
TinyFrontier/vibetax · ★ 5 · AI & Automation · score 72
Install: claude install-skill TinyFrontier/vibetax
# NoMedian Turn fast AI-generated interface work into a coherent product design. Distilled from Matt Dailey's guide [«How I Design with AI»](https://x.com/reactiverobot/status/2092638003789439075); the constraints loop follows Christopher Alexander's *Notes on the Synthesis of Form*. ## Sources and boundaries - Project design tokens, style guides, components, product requirements, and explicit user instructions are the binding product sources. Locate them before proposing visuals. - When a required fact is missing, state the assumption or ask the user when the choice would materially change the result. Do not invent brand or workflow rules. - Taste guides choices within the constraints; it does not override product facts. - Do not deploy, access customer data, or write project documentation unless the task and available authorization cover those actions. ## Terms - **constraint** — a testable condition the design must satisfy. - **papercut** — a minor annoyance to collect for cohesive future work unless the user asks to fix it now. - **prototype gravity** — refining the first coded version instead of exploring alternatives. - **design surface** — Figma, another design tool, or a throwaway standalone prototype outside production code. - **de-slop pass** — removing every element the design can succeed without. - **taste note** — a specific reaction plus the design principle inferred from it. ## Workflow 1. **Route the request and load context.** Find the project