UI Direction — concept before code
Without direction a model draws the average website. This skill replaces "modern and clean"
with a concept derived from the subject, written down so every later page and every later run
reuses it. Read rules/core/ui-anti-slop.mdc (~/goodai-base/rules/core/ui-anti-slop.mdc when running outside goodai-base) first — it is the shared tell catalog and the
thresholds this skill must respect.
Workflow
ui-direction Progress:
- [ ] Step 1: Establish the brief (subject, audience, primary job, surface type)
- [ ] Step 2: Read what already exists (brand, DESIGN.md, tokens, real content)
- [ ] Step 3: Mine 8–12 subject facts
- [ ] Step 4: Deal three directions
- [ ] Step 5: Pick one; write the idea sentence; competitor + swap test
- [ ] Step 6: Plan palette, type, layout (ASCII), motion, signature, imagery
- [ ] Step 7: Generic-default self-check; revise and log what changed
- [ ] Step 8: Write DESIGN.md and report
Step 1 — Brief
Establish, from the request and the repo:
| Field |
Example |
| Subject |
an independent bike-repair shop in Lisbon |
| Audience |
commuters with a broken bike today |
| Primary job / one required action |
book a repair slot |
| Surface type |
marketing (page that persuades) or app (screen that is used: dashboard, admin, editor, inbox, settings) |
| Constraints |
existing brand, framework, component library, dark mode, locales |
Ask only when a missing field blocks the concept; otherwise state one concrete assumption and
continue. If the brief names a specific look, follow it exactly and skip Step 4.
Step 2 — Read what exists
- Existing
DESIGN.md, theme/tokens files, Tailwind config, logo, brand guide, screenshots.
- Real content: product names, prices, copy, data shapes. Real content beats placeholders in
every later step.
- An established design system is a constraint, not a reason to be bland: the direction then
lives in composition, content, imagery, and the signature element.
Step 3 — Mine the subject (8–12 facts)
Raw material for the concept: the name and what it means, the place, the trade's tools and
materials, its numbers, rituals, printed artefacts (receipts, tickets, labels, manuals, maps),
its vocabulary, what the audience is anxious about. Write them as a list in DESIGN.md.
Step 4 — Three directions
Sketch three different directions in 3–4 lines each, each grounded in different facts from
Step 3. Concrete references only ("workshop repair tag + chalkboard price list",
"1970s transit signage") — never adjectives like "modern", "clean", "bold", "premium".
At least one direction must be uncomfortable for you; the comfortable one is the average.
Step 5 — Choose and test
Pick one; give the reason in terms of the subject and audience. Then write the idea sentence:
On this page, [the subject's thing] becomes [the direction's device].
- Competitor test — would the nearest real competitor fit the same sentence equally well?
If yes, the idea is too generic; go back to Step 4.
- Swap test — could a competitor put its logo on the result unnoticed? Same verdict.
Step 6 — Plan
| Dimension |
What to decide |
Hard limits (from ui-anti-slop) |
| Palette |
4–6 named colors with roles: ground, ink, accent, + support/status. Hex + role + where used |
Accent on primary action + ≤1 other. Body pairs ≥4.5:1, UI pairs ≥3:1 — compute and list the ratios |
| Type |
1–2 families with roles, scale ratio, body size/leading/measure |
No default-only Inter/Roboto/system; marketing display ≥3× body; app ≤3 visible sizes |
| Layout |
Grid, alignment axis, section/screen list with one sentence each, ASCII wireframes at desktop and phone |
Neighbor sections differ in structure; no stock page order |
| Shape |
Radius scale by role, separation method (tone vs border vs shadow) |
Shadows only on floating layers |
| Motion |
The one orchestrated moment (or none) + interaction feedback |
100–400ms, reduced-motion variant |
| Signature |
Exactly ONE memorable element, tied to the idea sentence |
One. Not two. |
| Imagery |
Order: project's own → generated → open-licensed real → drawn in code → type & color only |
No stock blobs, floating people, fake dashboards |
| Copy voice |
3 rules for the voice + outcome-labeled primary CTA |
No filler verbs, no invented proof |
For app surfaces: color is for data and status, panels stay quiet, density matches the
task, and every screen lists its empty / loading / error / sparse / dense states.
Step 7 — Generic-default self-check
Re-read the plan as a stranger. For each dimension ask: is this what a model would produce for
any similar page? Score the plan against the tell catalog in ui-anti-slop.mdc. Any T1 tell,
or slop score ≥4, means revise. Log every revision as changed X → Y because Z.
Then remove one element from the plan.
Step 8 — Output
Write DESIGN.md at the project root (or the path the user names; update in place if it exists):
# Design Direction — <product>
## Brief
## Subject facts
## Directions considered (3, with why the other two lost)
## Idea sentence
## Palette (name | hex | role | contrast pairs)
## Typography (family | role | scale | body size/leading/measure)
## Layout (grid, alignment, ASCII wireframes desktop + phone)
## Shape & elevation
## Motion
## Signature element
## Imagery
## Voice & copy rules
## Not doing (explicit tells banned for this project)
## Exemptions (tells deliberately chosen, with reason)
## Revision log
Report to the user: idea sentence, the three directions in one line each, why this one, the
signature element, and the path to DESIGN.md. Offer ui-craft as the next step.
Exit criteria
Done only when DESIGN.md exists with every section filled, the idea sentence passed the
competitor and swap tests, the plan has no T1 tell and a slop score ≤3 (or recorded
exemptions), every listed contrast pair meets its threshold, and the revision log names what
the self-check changed.
Iron Laws
| Rule |
Why |
| No code in this skill |
Code before direction is how the average gets built |
| Every choice cites a subject fact or the brief |
Unanchored choices are the model's prior |
| Exactly one signature element |
Two signatures compete; none is memorable |
| Contrast ratios are computed, not assumed |
Distinctive and unreadable is still a failure |
| Interaction stays conventional |
Distinctive look, familiar behavior (Jakob's Law) |
| Do not repeat the previous project's direction |
Re-convergence on your own favorites is slop too |
Red Flags
| Thought |
Reality |
| "Clean and modern will be fine" |
That sentence is the average website |
| "Let's use a dark theme with one neon accent to stand out" |
Second-wave slop; justify it from the subject or drop it |
| "I'll add a gradient for depth" |
Depth comes from tone steps and layering, not washes |
| "The user didn't give content, so lorem ipsum" |
Write plausible, clearly-marked sample content from subject facts |
| "Three directions is overkill" |
The first idea is the most probable one |
1---2name: ui-direction3description: |4 Use when: a new page, screen, product, or redesign needs a visual concept BEFORE any UI code5 is written, or when existing UI "looks generic / AI-made / like every other SaaS" and needs a6 distinctive direction. Produces a persistent DESIGN.md (concept sentence, palette, type,7 layout wireframes, motion stance, signature element, not-doing list) that ui-craft builds from8 and review-ui-ux reviews against. Triggers: "design direction", "make it unique",9 "не нейрослоп", "придумай визуальный концепт", "redesign the look", "/ui-direction".10 NOT for: writing the components (ui-craft), reviewing existing UI (review-ui-ux), or11 token/component-library maintenance in an established design system (design:design-system).12version: "1.0.0"13triggers:14 - "design direction"15 - "visual concept"16 - "make the ui unique"17 - "не нейрослоп"18 - "визуальный концепт"19 - "/ui-direction"20metadata:21 source: https://skillmd.com/skills/mrciphersmith/ui-direction22 author: "MrCipherSmith"23 version: "1.0.0"24 category: "design"25license: "MIT"26compatibility: "cursor,codex,zed,opencode,claude"27---2829# UI Direction — concept before code3031Without direction a model draws the average website. This skill replaces "modern and clean"32with a concept derived from the subject, written down so every later page and every later run33reuses it. Read `rules/core/ui-anti-slop.mdc` (`~/goodai-base/rules/core/ui-anti-slop.mdc` when running outside goodai-base) first — it is the shared tell catalog and the34thresholds this skill must respect.3536---3738## Workflow3940```41ui-direction Progress:42- [ ] Step 1: Establish the brief (subject, audience, primary job, surface type)43- [ ] Step 2: Read what already exists (brand, DESIGN.md, tokens, real content)44- [ ] Step 3: Mine 8–12 subject facts45- [ ] Step 4: Deal three directions46- [ ] Step 5: Pick one; write the idea sentence; competitor + swap test47- [ ] Step 6: Plan palette, type, layout (ASCII), motion, signature, imagery48- [ ] Step 7: Generic-default self-check; revise and log what changed49- [ ] Step 8: Write DESIGN.md and report50```5152---5354## Step 1 — Brief5556Establish, from the request and the repo:5758| Field | Example |59|---|---|60| Subject | an independent bike-repair shop in Lisbon |61| Audience | commuters with a broken bike today |62| Primary job / one required action | book a repair slot |63| Surface type | `marketing` (page that persuades) or `app` (screen that is used: dashboard, admin, editor, inbox, settings) |64| Constraints | existing brand, framework, component library, dark mode, locales |6566Ask only when a missing field blocks the concept; otherwise state one concrete assumption and67continue. If the brief names a specific look, follow it exactly and skip Step 4.6869## Step 2 — Read what exists7071- Existing `DESIGN.md`, theme/tokens files, Tailwind config, logo, brand guide, screenshots.72- Real content: product names, prices, copy, data shapes. Real content beats placeholders in73 every later step.74- An established design system is a constraint, not a reason to be bland: the direction then75 lives in composition, content, imagery, and the signature element.7677## Step 3 — Mine the subject (8–12 facts)7879Raw material for the concept: the name and what it means, the place, the trade's tools and80materials, its numbers, rituals, printed artefacts (receipts, tickets, labels, manuals, maps),81its vocabulary, what the audience is anxious about. Write them as a list in `DESIGN.md`.8283## Step 4 — Three directions8485Sketch three different directions in 3–4 lines each, each grounded in different facts from86Step 3. Concrete references only ("workshop repair tag + chalkboard price list",87"1970s transit signage") — never adjectives like "modern", "clean", "bold", "premium".88At least one direction must be uncomfortable for you; the comfortable one is the average.8990## Step 5 — Choose and test9192Pick one; give the reason in terms of the subject and audience. Then write the idea sentence:9394> On this page, **[the subject's thing]** becomes **[the direction's device]**.9596- **Competitor test** — would the nearest real competitor fit the same sentence equally well?97 If yes, the idea is too generic; go back to Step 4.98- **Swap test** — could a competitor put its logo on the result unnoticed? Same verdict.99100## Step 6 — Plan101102| Dimension | What to decide | Hard limits (from ui-anti-slop) |103|---|---|---|104| Palette | 4–6 named colors with roles: ground, ink, accent, + support/status. Hex + role + where used | Accent on primary action + ≤1 other. Body pairs ≥4.5:1, UI pairs ≥3:1 — compute and list the ratios |105| Type | 1–2 families with roles, scale ratio, body size/leading/measure | No default-only Inter/Roboto/system; marketing display ≥3× body; app ≤3 visible sizes |106| Layout | Grid, alignment axis, section/screen list with one sentence each, ASCII wireframes at desktop and phone | Neighbor sections differ in structure; no stock page order |107| Shape | Radius scale by role, separation method (tone vs border vs shadow) | Shadows only on floating layers |108| Motion | The one orchestrated moment (or none) + interaction feedback | 100–400ms, reduced-motion variant |109| Signature | Exactly ONE memorable element, tied to the idea sentence | One. Not two. |110| Imagery | Order: project's own → generated → open-licensed real → drawn in code → type & color only | No stock blobs, floating people, fake dashboards |111| Copy voice | 3 rules for the voice + outcome-labeled primary CTA | No filler verbs, no invented proof |112113For `app` surfaces: color is for data and status, panels stay quiet, density matches the114task, and every screen lists its empty / loading / error / sparse / dense states.115116## Step 7 — Generic-default self-check117118Re-read the plan as a stranger. For each dimension ask: *is this what a model would produce for119any similar page?* Score the plan against the tell catalog in `ui-anti-slop.mdc`. Any T1 tell,120or slop score ≥4, means revise. Log every revision as `changed X → Y because Z`.121Then remove one element from the plan.122123## Step 8 — Output124125Write `DESIGN.md` at the project root (or the path the user names; update in place if it exists):126127```markdown128# Design Direction — <product>129130## Brief131## Subject facts132## Directions considered (3, with why the other two lost)133## Idea sentence134## Palette (name | hex | role | contrast pairs)135## Typography (family | role | scale | body size/leading/measure)136## Layout (grid, alignment, ASCII wireframes desktop + phone)137## Shape & elevation138## Motion139## Signature element140## Imagery141## Voice & copy rules142## Not doing (explicit tells banned for this project)143## Exemptions (tells deliberately chosen, with reason)144## Revision log145```146147Report to the user: idea sentence, the three directions in one line each, why this one, the148signature element, and the path to `DESIGN.md`. Offer `ui-craft` as the next step.149150---151152## Exit criteria153154Done only when `DESIGN.md` exists with every section filled, the idea sentence passed the155competitor and swap tests, the plan has no T1 tell and a slop score ≤3 (or recorded156exemptions), every listed contrast pair meets its threshold, and the revision log names what157the self-check changed.158159---160161## Iron Laws162163| Rule | Why |164|---|---|165| No code in this skill | Code before direction is how the average gets built |166| Every choice cites a subject fact or the brief | Unanchored choices are the model's prior |167| Exactly one signature element | Two signatures compete; none is memorable |168| Contrast ratios are computed, not assumed | Distinctive and unreadable is still a failure |169| Interaction stays conventional | Distinctive look, familiar behavior (Jakob's Law) |170| Do not repeat the previous project's direction | Re-convergence on your own favorites is slop too |171172## Red Flags173174| Thought | Reality |175|---|---|176| "Clean and modern will be fine" | That sentence is the average website |177| "Let's use a dark theme with one neon accent to stand out" | Second-wave slop; justify it from the subject or drop it |178| "I'll add a gradient for depth" | Depth comes from tone steps and layering, not washes |179| "The user didn't give content, so lorem ipsum" | Write plausible, clearly-marked sample content from subject facts |180| "Three directions is overkill" | The first idea is the most probable one |