@ericrisco/rsc 3.1.4 → 3.3.1

package/skills/design/evals/cases.yaml

@@ -1,56 +1,45 @@
 skill: design
 
 should_trigger:
-  - prompt: "Design a landing page for our new analytics SaaS — hero, pricing, the works."
-    why: "Explicit landing-page design with full marketing-page composition; this is the skill's core use case."
-  - prompt: "Our homepage looks generic, like every other AI-generated startup site. Can you make it feel premium and intentional?"
-    why: "Rescuing a 'feels generic / AI-slop' UI is named verbatim in the description and the When-to-use list."
-  - prompt: "Pick a color palette and type pairing for my product, and give me the Tailwind tokens."
-    why: "Choosing a visual system (color, type, tokens) is an explicit trigger; the skill ships Tailwind v4 @theme OKLCH tokens."
-  - prompt: "Can you do a design review of this hero section and tell me how to make it convert better?"
-    why: "Design review / critique plus conversion intent; the skill has a dedicated design-review QA checklist and a 0-10 visual-audit rubric."
-  - prompt: "I've got the React components built and working, but it all just looks flat and amateur — help me polish the visuals and spacing."
-    why: "A polish pass on an existing surface; user names the symptom (flat/amateur) without naming a tool, which the skill targets ('make an interface feel premium')."
-  - prompt: "Write the hero headline and a punchy value prop for our developer-tool site, and lay out the page so it sells."
-    why: "Conversion copy (hero/value-prop) plus page layout for selling — the skill owns visual + landing structure and co-owns copy; non-obvious because it leads with copy."
-  - prompt: "Add a bento-grid features section to our marketing site that doesn't look like a template."
-    why: "'bento section' is an explicit named trigger; involves layout/composition for a marketing surface."
+  - prompt: "Design a landing page for our new analytics SaaS."
+    why: "A public page to design from scratch is the page run's core case (Persuade mode)."
+  - prompt: "Our homepage looks generic, like every other AI-generated startup site. Make it look designed."
+    why: "'Looks generic / AI-made' is named in the description; the skill exists to replace the model's default."
+  - prompt: "Hazme la web de un restaurante de mi pueblo, que no parezca una plantilla."
+    why: "A local business page in Spanish; the inventory of the subject and real pictures are exactly what the run forces."
+  - prompt: "Rediseña el dashboard de facturación, que se ve feo y desordenado."
+    why: "An app screen redesign (Operate mode) follows the app-screen run with its own draw and inspector."
+  - prompt: "Review this portfolio page and tell me the three changes that would improve it most."
+    why: "A review of an existing page: record the before in the browser, critique the screenshots, stop at findings."
+  - prompt: "Restyle our docs site so it stops looking like every other docs template."
+    why: "Read mode: the style owns the frame while the reading column stays calm."
 
 should_not_trigger:
-  - prompt: "Write the SEO keyword strategy and do a technical SEO audit for our marketing site, targeting buyer-intent terms."
-    route_to: "marketing"
-    why: "Deep keyword research, GEO, and technical SEO audits are explicitly delegated to the marketing sibling; design only enforces SEO-aware markup structure."
-  - prompt: "Set up the Next.js 15 App Router routing, server actions, and data fetching for these pages."
+  - prompt: "Write the hero headline, offer and CTA copy for our pricing page."
+    route_to: "landing-copy"
+    why: "The words on a conversion page belong to landing-copy; design builds the page around them."
+  - prompt: "Where should the filter state live, in the URL or in the component, and how do we handle loading and errors?"
+    route_to: "ui-engineering"
+    why: "How interface is built (state, boundaries, async states) is ui-engineering, not visual design."
+  - prompt: "Make our web app pass WCAG 2.2 AA: fix the axe violations and keyboard traps."
+    route_to: "accessibility"
+    why: "Conformance remediation is the accessibility skill's job."
+  - prompt: "Create our logo brief and a full brand book with print colours."
+    route_to: "brand-identity"
+    why: "A brand system for every medium is brand-identity; design consumes it with --keep palette,type."
+  - prompt: "Set up Next.js App Router routing and server actions for these pages."
     route_to: "nextjs"
-    why: "Pure App Router / React 19 build mechanics are the nextjs sibling's job; design hands off the build."
-  - prompt: "Build a daily-use internal ops dashboard for our support team to triage tickets fast — pure data tables, no marketing."
-    route_to: "none"
-    why: "Dense internal operational tooling is explicitly a do-NOT-force-a-landing case; the skill says not to paint a marketing skin on a daily-use tool. Routes to product judgment, not a sibling."
-  - prompt: "Mirror our brand colors and typography into the Flutter mobile app's theme."
-    route_to: "flutter"
-    why: "Translating brand tokens into a Flutter app is the flutter sibling's job, not web UI design."
-  - prompt: "Implement an iOS 26 SwiftUI Liquid Glass material for this native settings panel."
-    route_to: "none"
-    why: "Native iOS Liquid Glass is the external liquid-glass-design reference; this skill ships only the web glass approximation, so it should decline/defer (no in-repo sibling)."
-  - prompt: "Help me wire up the spring physics and AnimatePresence layout animations for this modal in Framer Motion."
-    route_to: "none"
-    why: "Deep motion-code mechanics (springs, AnimatePresence internals) are explicitly deferred to the external motion-ui references; design only sets motion intent + budget."
+    why: "Framework build mechanics are nextjs."
 
 capability:
-  - scenario: "User asks: 'Design the hero section for our new SaaS landing page and make it look premium.' (No 02-DOCS/wiki/brand/ study exists in the repo yet.)"
+  - scenario: "Asked to build a landing page for a bakery with no brand and no photographs."
     must_include:
-      - "STOPS before designing and checks for a brand study at 02-DOCS/wiki/brand/ (via root CLAUDE.md ## Brand & voice); on finding it missing/incomplete, asks a focused batch of brand-grounding questions instead of guessing."
-      - "Runs (or states it will run) the research-first protocol: WebSearch award galleries / tier-1 sites and synthesize a cited DESIGN DIRECTION before prescribing, rather than shipping from memory."
-      - "Enforces the 5-second value-prop test: hero states what it is, who it's for, why it's better, above the fold — and shows the product, not a centered headline over an atmospheric gradient."
-      - "Uses design tokens (Tailwind v4 @theme, OKLCH color, modular type scale, 4/8px spacing, radius/shadow tokens) — no magic hex or arbitrary px."
-      - "Treats accessibility as a hard constraint: text contrast >= 4.5:1, visible focus, one <h1>, semantic landmarks, touch targets >= 24px (44px ideal)."
-      - "Treats Core Web Vitals as design constraints: LCP < 2.5s with next/image priority on the hero image, INP < 200ms, CLS < 0.1, next/font."
-      - "Benefit-led, specific copy that avoids the ban-list (revolutionary, seamless, game-changer, unlock, supercharge, elevate, etc.)."
-  - scenario: "User asks: 'Here's our current pricing page — do a design review and tell me how good it actually is.'"
+      - "inventory of eight to twelve things only this client has"
+      - "draw.mjs deals three directions; one is chosen against the inventory with a written reason"
+      - "an idea sentence that fails the competitor test, and one live thing"
+      - "at least four real pictures found with assets.mjs and credited"
+      - "inspect.mjs at 1440, 768 and 390 with zero FAIL before reporting"
+  - scenario: "The machine has no Chrome and Node 20."
     must_include:
-      - "Applies the design-review QA checklist (value prop in 5s, contrast >= 4.5:1, visible focus, one <h1>, semantic landmarks, LCP image priority, next/font, no transition: all, tokens not magic numbers, ban-list-clean copy, 360px fit, empty/loading/error states)."
-      - "Scores the 11-dimension visual-audit rubric 0-10 with weights and reports the weighted total on its /115 scale, mapped to a band (<69 generic / 69-91 competent / 92-108 premium / 109+ award-tier)."
-      - "For each dimension scoring below 8, gives a concrete actionable fix (e.g. exact spacing/token change), not a vague 'improve spacing'."
-      - "Checks copy against the ban-list and flags hype/vague value props that fail the 5s test."
-      - "Flags any transition: all, magic hex/px, cards-in-cards, or purple->blue everything gradient as defects, not preferences."
-      - "Ties findings back to the brand study / cited trend source where the bar is set, rather than asserting taste."
+      - "runs lint.mjs and critiques screenshots from another browser tool"
+      - "the report says 'inspector not run' with the reason and claims no gate pass"

package/skills/design/references/design-md.md

@@ -0,0 +1,49 @@
+# DESIGN.md: the record of the system
+
+Adapted from impeccable's `document` by Paul Bakaus (Apache-2.0), which follows the open
+`design.md` format. Rewritten and shortened.
+
+The point: the next edit, the next session and the next tool keep the look instead of drifting back
+to the model's default. Write it **after** the build, from what was actually built and measured,
+never before. A rulebook written ahead of the build gets defended against reality.
+
+## Where and when
+
+- `DESIGN.md` at the project root, committed with the code.
+- Written when a surface creates or replaces the visual system. Extending an existing surface reads
+  it and does not rewrite it.
+- If `02-DOCS/wiki/brand/` exists, `DESIGN.md` uses the brand's colours and faces and names that
+  file as its source.
+
+## Shape
+
+YAML front matter holds the tokens; the body explains them.
+
+```markdown
+---
+name: <product>
+description: <one line: the idea sentence>
+colors:
+  ground: "#…"
+  ink: "#…"
+  accent: "#…"
+  field: "#…"
+typography:
+  display: { fontFamily: "…", fontWeight: 600, letterSpacing: "-0.03em", lineHeight: 0.95 }
+  text: { fontFamily: "…", fontSize: "18px", lineHeight: 1.5 }
+rounded: { button: "0px", media: "0px" }
+spacing: { margin: "24px", section: "200px" }
+direction: { id: "<dealt id>", seed: <n> }
+---
+
+## Overview        the idea, the mode, the direction and why it was chosen
+## Colors          roles and proportions (one ground, one ink, one accent, fields)
+## Typography      the scale actually used, tracking, measure
+## Layout          grid, outer margins, section rhythm, the phone composition
+## Imagery         sources, crops, treatment, where credits live
+## Motion          the signature move and the entrance recipe
+## Components      buttons, navigation, the live thing, footer
+## Do's and Don'ts the house rules this project relies on, plus any `--allow` and its reason
+```
+
+Values come from the built CSS and the inspector's measurements, not from memory.

package/skills/design/references/finish-review.md

@@ -0,0 +1,46 @@
+# The fresh review
+
+Adapted from impeccable's finish reviewer by Paul Bakaus (Apache-2.0); rewritten and shortened.
+
+The builder believes its own page. The review runs **outside** the build: a fresh subagent with no
+history of this conversation, so it does not inherit the builder's framing or optimism. Without
+subagents, step fully out of the build and run the same checks yourself, and say in the report that
+the review was not independent.
+
+## The packet
+
+Hand it only this:
+
+- the original request and the user's answers;
+- the screenshots from `.taste-skill/inspect/` at every width (the reviewer has no browser);
+- the last `inspect.mjs` result;
+- the direction sheet (`draw.mjs --show`), the idea sentence and the live thing;
+- the paths of `../engine/RUN.md` (house rules) and `../engine/references/critique.md`.
+
+## The checks, in order
+
+0. **Evidence.** Every width captured, no blank or half-loaded screenshot, content where the
+   filename says. If one fails, the answer is `recapture` and nothing else.
+1. **First screen.** Within five seconds: what is this, why does it matter, what do I do?
+2. **The idea.** Is the idea sentence visible on the page, in every section, and does it fail the
+   competitor test (would it work for the nearest competitor)?
+3. **The direction.** Was the dealt direction built, or did the build drift back to the layout the
+   model would have made anyway?
+4. **Substance.** Real pictures, full content, no screen that is mostly empty ground.
+5. **Truth.** No invented customers, quotes, numbers or logos. Sample content marked.
+6. **Floor.** The house rules in `../engine/RUN.md`, plus what screenshots show and code hides:
+   states (hover, focus, loading, empty, error), themed selection and focus rings, text that fits.
+
+## The four words
+
+The first line of the answer is exactly one of these. The word follows from the checks:
+
+- `recapture`: the evidence failed, not the page. Capture again, then a full review.
+- `rebuild`: the focal element or the direction itself is wrong. Re-derive it; patches will not do.
+- `fix`: an ordered list of material fixes, at most eight, most important first.
+- `ship`: nothing material remains.
+
+Then: `fixes` (when `fix`) and `keep`, one line naming what must not be diluted while fixing.
+Apply the fixes in one batch, run the gate again, and send the new screenshots back for a verdict
+on each fix: resolved, partial or unresolved. Two rounds at most. A partial or unresolved fix
+never becomes `ship`. Report the reviewer's word as it was given.

package/skills/design/references/modes.md

@@ -0,0 +1,51 @@
+# The four modes
+
+Adapted from impeccable by Paul Bakaus (Apache-2.0); rewritten and shortened. The mode names what
+the visitor's success looks like on this surface. Pick it from the surface, never the product: a
+developer tool's landing page is Persuade, a fashion house's docs are Read.
+
+## Persuade
+
+The visitor decides and acts. The design is what they judge.
+
+- The first screen makes the offer clear and shows **the action visitors came to take, working**: a
+  flight search, open appointment slots, add to cart. A button that points somewhere else is not it.
+- The subject's world carries the page; it is never painted over it as a poster with no working parts.
+- Refuse both ends: the poster, and the stock product page (headline, subline, button, a row of
+  equal cards; or the split hero with a badge row under it).
+
+## Experience
+
+The visitor is inside the work: portfolio, gallery, showcase. The work leads from the first
+viewport and the interface recedes. Same page run as Persuade.
+
+## Operate
+
+The visitor completes a task. Someone who uses tools like this should know where everything is
+before they notice the style.
+
+- The direction lends four things only: **type, palette, density and one signature move** (service
+  health drawn as a transit map, a schedule in a timetable's column rhythm). Never the layout, the
+  navigation model or the controls.
+- Every control is the standard one the visitor already knows. No costume of a terminal, an
+  instrument bezel or ledger paper.
+- Colour does real jobs: a committed shell, state colours, data series, selection. A grey screen
+  with one accent is the category default without its polish.
+- Realistic data with units and one state worth seeing (an alert, a degraded service, an empty
+  filter). Never grey placeholder bars.
+- The bar is the cleanest product in its category; the signature move adds to that, never replaces it.
+
+The run, rules and checks for these screens: `../engine/references/app-screens.md`
+(`draw.mjs --app`, `inspect.mjs --app`).
+
+## Read
+
+The visitor understands something: docs, guide, article, changelog.
+
+- The style owns **the frame**: masthead, rail, ground, title and section openers, how code and
+  tables are set. That is where palette, type and the signature move commit fully.
+- The reading column stays calm: a reading face, real contrast, about 60–75 characters at about
+  16px. No monospace prose. Nothing performs behind the text.
+- The style never supplies the reading order or replaces the navigation with something to learn.
+- Check: can a reader tell where they are, where to go next, and read comfortably? Cover the name:
+  could this be any other product's docs? Then the frame has not taken the style yet.

package/skills/expo/SKILL.md

@@ -8,10 +8,9 @@ origin: risco
 
 # Expo & EAS: shipping React Native
 
-**Hand-off — the app vs its motion.** This skill owns the Expo platform: router, config plugins, EAS,
-native modules, store builds. **Animation and gestures** — Reanimated worklets, the UI runtime,
-sheets, screen transitions, press feedback, haptics, motion that stutters on a real device — are
-`../motion-craft/SKILL.md`'s.
+**Scope.** This skill owns the Expo platform: router, config plugins, EAS, native modules, store
+builds. Animation and gestures (Reanimated worklets, sheets, press feedback, haptics) follow
+`../react-native/SKILL.md`. Visual design of web pages and screens is `../design/SKILL.md`'s.
 
 
 ## What this skill owns

package/skills/marketing/references/landing-copy.md

@@ -1,6 +1,6 @@
 # Landing Copy by Section
 
-The words for every landing section, mapped 1:1 to the `design` skill's section anatomy (`../../design/references/landing-anatomy-and-cro.md`). `design` owns the visual treatment and layout; this file owns the copy that goes inside each section. Each section has **one copy job**; cut any section whose job you can't name. Ground every line in the brand study (`brand-grounding.md`) and run the value prop through the canvas (`copy-frameworks.md`) first.
+The words for every landing section. `../../design/SKILL.md` owns the visual treatment, the layout and which sections exist (its argument step: one claim per section); this file owns the copy that goes inside each section. Each section has **one copy job**; cut any section whose job you can't name. Ground every line in the brand study (`brand-grounding.md`) and run the value prop through the canvas (`copy-frameworks.md`) first.
 
 ## Section map (copy job + framework)
 
@@ -187,5 +187,5 @@ Good — "Stop babysitting staging. Start free — no credit card."
 
 - `copy-frameworks.md` — the frameworks and headline formulas each section uses.
 - `brand-grounding.md` — the value prop, proof, and voice every line is grounded in.
-- `../../design/references/landing-anatomy-and-cro.md` — the visual anatomy these words fill.
+- `../../design/SKILL.md` — the page these words fill; write the copy deck before its markup.
 - `campaigns-and-channels.md` — driving traffic to this page.

package/skills/react/SKILL.md

@@ -10,8 +10,8 @@ origin: risco
 
 **Hand-off — picking dependencies.** Which library to reach for (UI primitives, command menus,
 toasts, OTP inputs, charts, virtualization, drag and drop, state, styling, theming) is
-`../ui-engineering/SKILL.md`'s — build vs adopt is decided there, before hand-rolling a component. Animating what you
-install is `../motion-craft/SKILL.md`'s.
+`../ui-engineering/SKILL.md`'s — build vs adopt is decided there, before hand-rolling a component. The look of a page
+or screen, and its motion layer, is `../design/SKILL.md`'s.
 
 
 > Build or review a fast, typed, correctly-architected **client-side** React single-page app bundled by Vite. No server runtime, no RSC tree, no framework router. Server-rendered React (App Router, server actions, SSR/SSG) is not this skill — that is `../nextjs/SKILL.md`.

package/skills/react-native/SKILL.md

@@ -8,9 +8,9 @@ origin: risco
 
 # React Native (app code)
 
-**Hand-off — the app vs its motion.** Animation and gestures in a React Native app — Reanimated
-worklets on the UI runtime, gesture handoff, sheets, press feedback, haptics — are
-`../motion-craft/SKILL.md`'s, whose guidance is platform-agnostic and applies to bare React Native as well as Expo.
+**Scope.** App code, including animation and gestures (Reanimated worklets on the UI runtime, gesture
+handoff, sheets, press feedback, haptics), in bare React Native and in Expo. Visual design of web
+pages and screens is `../design/SKILL.md`'s.
 
 
 You write the code that runs *inside* the app: render, navigate, animate, list, persist, and author native modules. Mobile is split across two skills by **verb** — run the verb test before doing anything:

package/skills/suggest/SKILL.md

@@ -55,13 +55,12 @@ name it and offer it. This runs mid-conversation, not only at project start.
 1. `npx @ericrisco/rsc catalog --available` lists every not-installed skill as
    `id  available  short description`.
 2. Pick the single best fit **by meaning**, the way you would match a request to a teammate's
-   expertise — "mandar emails de bienvenida" → an email/outreach skill, though not one keyword
-   overlaps. If nothing genuinely fits, say so
-   and move on: a tangential suggestion is worse than none.
+   expertise, even when no keyword overlaps. If nothing genuinely fits, say so and move on: a
+   tangential suggestion is worse than none.
 3. Ask once, plainly: "Para esto instalaría `<id>`, que aún no tienes. ¿La instalo? (sí/no)".
 4. On yes, run `npx @ericrisco/rsc add <id>`, then continue the original task.
 
-Installing changes the user's environment, so it is always their call. One suggestion at a time,
+One suggestion at a time,
 and never to interrupt a flow with a nice-to-have. Never recommend something already installed
 (`npx @ericrisco/rsc list`).
 
@@ -78,9 +77,8 @@ Not covered → one line, skill or agent. Rules: `skill-scout`.
 
 ## 3. A harness that is broken fixes itself
 
-You are injected into every session, so you are the only thing that can notice a broken
-harness before its owner does — and its owner usually cannot, because the symptoms name
-nothing they recognise. When any of these is true, act on it **once** in the session:
+Its owner rarely notices: the symptoms name nothing they know. When any of these
+is true, act on it **once** in the session:
 
 - `.rsc.json` exists and what it declares is not what is installed;
 - the same hook seems to run several times;
@@ -100,7 +98,7 @@ a cause. Then:
   teammate added, disarming a gate — **ask first**. A `git pull` never rewrites someone's
   machine.
 
-Offer once per session. Never mention any of it when the harness is healthy.
+Offer once per session; say nothing when the harness is healthy.
 
 ## 4. First contact
 
@@ -114,6 +112,12 @@ Before handling the first request of a session, check the workspace:
   `.rsc/.no-harness`, confirm in one line, and never auto-start `init` in this repo again.
 - With a profile, this gate is inert. Never re-onboard.
 
+## 5. «Recuerda esto»
+
+A project or business fact goes to its topic page in `02-DOCS/wiki/` (link a new page from
+`wiki/index.md`); say the path. Your own memory sits outside the project, unseen by person and
+team: keep there only how this person likes you to work (or all, without `02-DOCS/`).
+
 ## Explain without assuming
 
 Define a term at first use; never give a command, flag or path without saying what it does.

package/skills/suggest/evals/cases.yaml

@@ -76,3 +76,9 @@ capability:
       - "Names that one missing automation/connector skill"
       - "Asks one short confirmation before installing and does not auto-install"
       - "On confirmation, runs `npx @ericrisco/rsc add <id>` for that one missing skill, then resumes the automation task"
+
+  - scenario: "In a workspace with `02-DOCS/wiki/`, the user says 'recuerda que toda la actividad, también la de Andorra, va por una sola sociedad, Nadsan 2006 S.L.'. Show where rsc-suggest puts it."
+    must_include:
+      - "Writes the fact into the `02-DOCS/wiki/` page of its topic (creating it and linking it from `wiki/index.md` if none exists), not only into the assistant's own memory under `~/.claude/projects/`"
+      - "Tells the person the path where it was saved"
+      - "Opens no FTD document and asks no lane question for it"

package/skills/swift-ios/SKILL.md

@@ -13,7 +13,7 @@ origin: risco
 app lifecycle, Xcode, iOS APIs, App Store shipping. Language-level Swift — Swift 6 data-race safety
 and approachable concurrency, actors and task groups, `some` vs `any`, ARC and performance, Swift
 Testing, macros — is this skill's own ground. A concurrency error, a hang, a data race or a
-retain cycle belongs here. Interface feel, springs and materials: `../motion-craft/SKILL.md`.
+retain cycle belongs here, and so do interface feel, springs and materials on iOS.
 
 
 Native Apple-platform apps: the code is `.swift`, the UI is SwiftUI, and the compiler enforces actor isolation. If the answer is a `@MainActor`, `@Observable`, `async let`, `#expect`, `NavigationStack`, or `@Model`, you are in the right place.

package/skills/ui-engineering/SKILL.md

@@ -2,7 +2,7 @@
 name: ui-engineering
 description: "Use when the question is how interface should be BUILT — component boundaries, state that belongs in the URL vs the component, loading/empty/error states, forms, optimistic updates, build vs adopt. NOT the visual system (`design`), NOT framework mechanics (`react`/`nextjs`)."
 tags: [interface, frontend, architecture, components, state, craft]
-recommends: [design, motion-craft]
+recommends: [design]
 profiles: [core, full]
 origin: risco
 ---
@@ -108,7 +108,6 @@ The split is not about difficulty, it is about **who is the authority on the beh
 
 ## See Also
 
-- `../design/SKILL.md` — the visual system these decisions serve.
-- `../motion-craft/SKILL.md` — how the pieces here move once they exist.
-- `../design-loop/SKILL.md` — the graded critique that judges the result.
+- `../design/SKILL.md` — the visual system these decisions serve, its motion layer, and the
+  browser-measured critique that judges the result.
 - `../accessibility/SKILL.md` — the ground under focus, semantics and forms.

package/skills/ui-engineering/evals/cases.yaml

@@ -22,10 +22,10 @@ should_not_trigger:
     route_to: "react"
     why: "Framework mechanics. This skill decides what to build, not how the framework behaves."
   - prompt: "The dropdown animation feels cheap, what duration should it use?"
-    route_to: "motion-craft"
+    route_to: "design"
     why: "Once the component exists, how it moves is motion craft."
   - prompt: "Grade this dashboard and tell me if it is actually good."
-    route_to: "design-loop"
+    route_to: "design"
     why: "Judging a finished screen is the critique loop, not the build decisions."
   - prompt: "Set up the Next.js App Router with server actions for this project."
     route_to: "nextjs"

package/skills/variant-explorer/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: variant-explorer
-description: "Use when someone wants OPTIONS rather than an answer — 'show me a few versions', picking between approaches by seeing them. Genuinely different candidates, cheap to throw away, trade-off named. NOT the critique that judges one (`design-loop`), NOT the spec (`specify`)."
+description: "Use when someone wants OPTIONS rather than an answer — 'show me a few versions', picking between approaches by seeing them. Genuinely different candidates, cheap to throw away, trade-off named. NOT the critique that judges one (`design`), NOT the spec (`specify`)."
 tags: [prototyping, divergence, options, exploration, decision]
-recommends: [design-loop]
+recommends: [design]
 profiles: [full]
 origin: risco
 ---
@@ -84,10 +84,10 @@ handing the work back. Say which one you would pick and why, and make it easy to
 | Present five or six to be thorough | Past three, they stop being compared and start being skimmed. |
 | Give options with no recommendation | Standing back is not neutrality; it hands the work back to the person who asked. |
 | Explore a decision that is cheap to reverse | Just ship one. Divergence is for what is expensive to unwind. |
-| Keep iterating on the winner here | Once one is chosen, refining it is `../design-loop/SKILL.md` or the relevant build skill. |
+| Keep iterating on the winner here | Once one is chosen, refining it is `../design/SKILL.md` or the relevant build skill. |
 
 ## See Also
 
-- `../design-loop/SKILL.md` — the graded critique that takes over once a direction is chosen.
+- `../design/SKILL.md` — the graded critique that takes over once a direction is chosen.
 - `../specify/SKILL.md` — when what is missing is an agreed WHAT/WHY, not options.
 - `../design/SKILL.md` — building the chosen direction properly.

package/skills/variant-explorer/evals/cases.yaml

@@ -16,7 +16,7 @@ should_trigger:
 
 should_not_trigger:
   - prompt: "Review this checkout screen and grade it."
-    route_to: "design-loop"
+    route_to: "design"
     why: "Judging one finished thing is critique, the opposite of divergence."
   - prompt: "We need to agree what this feature is for before anyone builds it."
     route_to: "specify"

package/targets/clone-bootstrap.mjs

@@ -95,7 +95,7 @@ export function readManifest(root) {
   const ids = (v) => (Array.isArray(v) ? v.filter((x) => typeof x === 'string' && ID.test(x)) : []);
   // Retired skills read as their successors. Canonical map: scripts/lib/retired-skills.js — inlined
   // because this file cannot import anything, and tests/retired-skills.test.js holds the two equal.
-  const RETIRED = { eli5: 'orient', 'show-me': 'orient', bro: 'unslop' };
+  const RETIRED = { eli5: 'orient', 'show-me': 'orient', bro: 'unslop', 'design-loop': 'design', 'design-dna': 'design', 'motion-craft': 'design' };
   const skills = [...new Set(ids(parsed.skills).map((id) => (Object.hasOwn(RETIRED, id) ? RETIRED[id] : id)))];
   const own = ids(parsed.ownSkills);
   // A manifest with nothing declared is not a clone waiting to be equipped; there is nothing to offer.

package/scripts/lib/design-identity.js

@@ -1,117 +0,0 @@
-// Does this harness have a design identity, and can we tell?
-//
-// `design` has declared for a long time that without a brand study it STOPS and does not design.
-// Nothing checked it: `grep -rln "wiki/brand" scripts/` returned nothing before this file existed.
-// That is P2 — a rule declared binding with no mechanism is a decorative gate. Spec:
-// 02-DOCS/wiki/sdd/specs/design-area-cleanup.md
-//
-// Three states, and the third is the whole point. A checker that cannot look must never report
-// green: that exact defect was found and fixed in the design-dna style checker two days earlier,
-// where regex probes ran against empty text and returned vacuous passes. Absence of evidence is
-// reported as absence of evidence.
-//
-// Read-only. It never writes: 02-DOCS is untracked (P9) and there is no undo there.
-import { existsSync, lstatSync, readFileSync, readdirSync, statSync } from 'node:fs';
-import { join } from 'node:path';
-
-// Where the harness keeps durable design knowledge, and the section in the root instructions file
-// that points at it. Both are the `design`/`harness` convention, not invented here.
-export const BRAND_DIR = join('02-DOCS', 'wiki', 'brand');
-export const BRAND_SECTION = '## Brand & voice';
-
-/**
- * @returns {{state: 'present'|'missing'|'inconclusive', linked: boolean, articles: string[],
- *            reason: string, fix?: string}}
- *   `present`      — articles exist under the brand dir. `linked` says whether the root
- *                    instructions file points at them, which is how other skills find it.
- *   `missing`      — looked, found nothing. Carries the fix (P6: a denial carries its way out).
- *   `inconclusive` — could not look. Never conflated with `missing`, and never with green.
- */
-export function designIdentity(root = process.cwd()) {
-  const dir = join(root, BRAND_DIR);
-
-  let articles;
-  try {
-    if (!existsSync(dir)) {
-      // existsSync FOLLOWS symlinks, so a dangling one reports false and would be filed as "no
-      // identity here". It is not absence, it is unreadability — the same conflation this whole
-      // area was cleaning up. lstat sees the link itself and tells the two apart.
-      let danglingLink = false;
-      try { danglingLink = lstatSync(dir).isSymbolicLink(); } catch { /* genuinely absent */ }
-      if (danglingLink) {
-        return {
-          state: 'inconclusive',
-          linked: false,
-          articles: [],
-          reason: `${BRAND_DIR} is a symlink that does not resolve`,
-        };
-      }
-      return {
-        state: 'missing',
-        linked: false,
-        articles: [],
-        reason: `no ${BRAND_DIR}/ in this harness`,
-        fix: 'run `design-loop` to converge on a winner, then `design-dna` to write its record here',
-      };
-    }
-    // Not statSync: it follows symlinks, so a symlink here could report on a directory outside the
-    // declared zone. Same reason drift-check.js:167 uses dirents.
-    if (!statSync(dir).isDirectory()) {
-      return {
-        state: 'inconclusive',
-        linked: false,
-        articles: [],
-        reason: `${BRAND_DIR} exists but is not a directory`,
-      };
-    }
-    articles = readdirSync(dir).filter((f) => f.endsWith('.md') && f !== 'index.md');
-  } catch (e) {
-    // Unreadable for any reason (permissions, dangling symlink, ELOOP). We did not look, so we
-    // cannot say. Reporting `missing` here would invent a finding; reporting green would hide one.
-    return {
-      state: 'inconclusive',
-      linked: false,
-      articles: [],
-      reason: `cannot read ${BRAND_DIR}: ${e.code || e.message}`,
-    };
-  }
-
-  // The link matters on its own: five skills reach the identity through the root instructions file,
-  // so an unlinked identity is one they will not find.
-  let linked = false;
-  const claudeMd = join(root, 'CLAUDE.md');
-  if (existsSync(claudeMd)) {
-    try {
-      linked = readFileSync(claudeMd, 'utf8').includes(BRAND_SECTION);
-    } catch {
-      // The articles are what we were asked about and we did read them. A CLAUDE.md we could not
-      // read makes `linked` unknown, not the whole answer unknown — report it in the reason.
-      return {
-        state: articles.length ? 'present' : 'missing',
-        linked: false,
-        articles,
-        reason: `${articles.length} article(s), but CLAUDE.md could not be read to confirm the link`,
-      };
-    }
-  }
-
-  if (!articles.length) {
-    return {
-      state: 'missing',
-      linked,
-      articles: [],
-      reason: `${BRAND_DIR}/ exists but holds no identity article`,
-      fix: 'run `design-loop` to converge on a winner, then `design-dna` to write its record here',
-    };
-  }
-
-  return {
-    state: 'present',
-    linked,
-    articles,
-    reason: linked
-      ? `${articles.length} article(s), linked from CLAUDE.md`
-      : `${articles.length} article(s), but no "${BRAND_SECTION}" section in CLAUDE.md points at them`,
-    ...(linked ? {} : { fix: `add a "${BRAND_SECTION}" section to CLAUDE.md linking ${BRAND_DIR}/` }),
-  };
-}