Suede AI Design Skills Make the next action clear.
Review an existing flow or UI diff without changing the application, or implement an authorized design using the product's current components, tokens and brand. Start with the user's task and primary action, then examine hierarchy, content, accessibility, state coverage and visual fit. Keep source findings, rendered observations and conversion hypotheses distinct.
"review this flow and the UI diff without editing"->/suede-designAsk in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
claude code · sample session
$ /suede-design review this flowmode: read-only review · user task and primary actionevidence: source findings and observed states labeled separatelyOUTPUT: PRIORITIZED FINDINGS WITH EVIDENCE
Follow the user's goal through entry, decision, action, feedback and recovery states.
Review a UI diff for changed behavior, hierarchy, accessibility and scope without editing the application.
Prioritize task completion, clarity and conversion hypotheses before decorative polish.
Record source locations and observed states so each finding can be checked.
Build within the product
Use the current components, tokens, typography, color roles and approved brand assets.
Apply layout, dark mode, motion, responsive behavior and accessibility rules to the authorized surface.
Implement a selected mock or screenshot with an available image-to-code capability, or the existing local stack.
Compare matched viewport, content, theme and state when checking a design against a render.
Choose the matching task
Review: keep the application unchanged and return findings with proposed fixes. Build or fix: implement the authorized change and verify its behavior. Visual QA: compare the current render with the supplied target and report the observed gaps.
An optional visual kit can guide an explicitly selected direction. Record its source and reuse rights, then translate its useful principles through the product's existing brand. Keep approved marks, protected assets and factual claims intact.
Inspect local components before considering a third-party source. Review the actual source, license and proposed dependency change before adoption. Availability in a registry alone does not establish suitability.
Know what was verified
Source findings explain what the inspected code supports. Rendered findings describe states actually observed. If no browser or render is available, report that limitation and leave visual checks unverified. Source inspection alone never establishes a rendered visual pass.
A review can identify friction and suggest a conversion hypothesis. Claim a measured improvement only when a valid before-and-after measurement supports it.
Example review request
Use $suede-design for a read-only whole-flow review of this checkout and its UI diff. Prioritize the user's task, primary action, error recovery, hierarchy and accessibility. Preserve the current brand and scope. Return source-backed findings, rendered observations and proposed fixes separately. Do not change application files or call unobserved states verified.
It ships inside the Suede AI Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.