analyzthis_design 2.4.1 → 2.5.1

package/dist/skills/evolve-check/SKILL.md

@@ -72,21 +72,35 @@ Tell the user what's needed:
 
 ## Evolution metrics
 
-The dashboard shows per-persona evolution scores (0-100):
+The dashboard shows per-persona trust scores (0-100). A persona **starts at 50**
+and moves in both directions, so a rejection genuinely costs it.
 
 | Score | Level | Meaning |
 |-------|-------|---------|
-| 0-19 | Novice | No data yet |
-| 20-39 | Developing | Some lessons extracted |
-| 40-59 | Proficient | Lessons + outcomes accumulating |
-| 60-79 | Advanced | Patches proposed and some applied |
-| 80-100 | Expert | Significant evolution, patches applied |
-
-Scoring:
-- 10 pts per lesson (cap 100)
-- 15 pts per confirmed outcome (cap 100)
-- 20 pts per proposed patch (cap 100)
-- 25 pts bonus per applied patch
+| 80-100 | Trusted | Consistently shipped; weight heavily |
+| 60-79 | Reliable | More hits than misses |
+| 40-59 | Baseline | Neutral, or not enough evidence yet |
+| 20-39 | Developing | More rework than wins |
+| 0-19 | At risk | Repeatedly wrong or missed |
+
+Signed contributions:
+
+| Signal | Points |
+|---|---|
+| outcome `shipped` | **+15** |
+| outcome `blocked_correctly` | **+10** |
+| outcome `revised` | **-5** |
+| outcome `missed` | **-15** |
+| each rating | `(rating - 3) x 4` → 5* = +8, 1* = -8 |
+| each positive lesson | +10 |
+| patch proposed / applied | +20 / +25 |
+
+**Evidence gating:** below 5 signals a persona is reported as
+`Baseline (insufficient evidence)` regardless of score — one bad note must not
+brand a persona. Scores are derived on read, so changing weights re-scores history
+with no migration.
+
+Scope is **global per persona** by default. Pass `--project` to scope down.
 
 ## CLI reference
 
@@ -94,8 +108,10 @@ Scoring:
 # Check readiness + dashboard
 npx analyzthis_design evolve --ready
 
-# Just the dashboard
+# Just the dashboard (or the shorter alias)
 npx analyzthis_design evolve --metrics
+npx analyzthis_design scores
+npx analyzthis_design scores --persona arjun
 
 # Extract patches (dry-run by default)
 npx analyzthis_design evolve --extract --dry-run

package/dist/skills/kavi/SKILL.md

@@ -105,7 +105,7 @@ Next: /persona-orchestrator or /ux-story-gate — personas read this bank first.
 
 | Vault folder | Sources |
 |---|---|
-| `PRDs/` | README, docs, PRD/requirements markdown |
+| `PRDs/` | README, docs, PRD/requirements markdown — extracts **Durable Product Truth**: Target Audience, Core Purpose, Hard Constraints, Operating Context, Brand Voice, and User Evidence |
 | `Brand/` | Tailwind config, tokens, theme CSS |
 | `Pages/` | App Router / page files |
 | `Components/` | `components/`, UI TSX/JSX |

package/dist/skills/noor/SKILL.md

@@ -31,6 +31,8 @@ You cannot know host tokens. Do not invent a dollar figure.
 ## Non-negotiables
 
 - **Information hierarchy is declared before anything else.** Every screen has a ranked order of what matters most — primary action, then primary data, then secondary context, then rarely-needed config. This ranking is the ground truth other personas check their own lens against (Anuj checks density against it, Meera checks business-critical info against it, Arjun checks visual weight against it).
+- **Distill to essence:** Strip away container clutter, nested cards, and redundant borders. Use white space and typographic scale to structure content rather than wrapping every element in a card box (`[ux-guidelines.csv, row 100]`).
+- **Clarify UX copy:** CTAs must describe the exact outcome (e.g., "Create Invoice", "Export CSV") instead of vague words like "Submit", "Continue", or "Click Here".
 - Every screen has ONE clear primary action
 - Navigation hierarchy ≤3 levels
 - Forms: single column, one logical group per viewport height
@@ -38,7 +40,7 @@ You cannot know host tokens. Do not invent a dollar figure.
 
 ## What you fight against
 
-Dense data tables as a first impression. Multiple primary CTAs per screen. "Competitor X has it" as a design argument. Screens that exist to showcase capability rather than serve a task.
+Dense data tables as a first impression. Multiple primary CTAs per screen. "Competitor X has it" as a design argument. Container disease (cards nested in cards). Screens that exist to showcase capability rather than serve a task. Vague or jargon-laden copy.
 
 ## Output — Concept A (text wireframe format)
 

package/dist/skills/zara/SKILL.md

@@ -31,6 +31,7 @@ You cannot know host tokens. Do not invent a dollar figure.
 
 - **Structural delight** — changes the recipe: AI thinking animation, multi-modal result revelation, progressive disclosure of a complex result
 - **Surface delight** — polish layer: micro-animation on success, copy with personality, illustrated empty state
+- **Motion discipline** — all transitions must use snappy, natural 150–250ms ease-out timing. Strictly forbid bouncy, elastic spring overshoots, continuous decorative spin, or animations >400ms (`[ux-guidelines.csv, row 7, 8, 105]`).
 
 Rule: **ONE memorable moment beats five forgettable ones.** Force yourself to choose.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "analyzthis_design",
-  "version": "2.4.1",
-  "description": "8 AI design personas — v2.2 project-scoped knowledge bank (no cross-project vault entanglement), v2.0 chunked execution with frontier planner + free/cheap chunk models, adversarial deliberation loops, opt-in community feedback, Kavi knowledge collection, DesignSpec producer path, wireframe skills, UX critique, Agent Skills for Cursor, Claude, Codex, Grok, Windsurf. Plain source — no obfuscation, no auto-install.",
+  "version": "2.5.1",
+  "description": "8 AI design personas — v2.5.1 anti-AI-slop & craftsmanship rules, v2.5.0 signed rate-based persona trust scoring, v2.2 project-scoped knowledge bank, v2.0 chunked execution with frontier planner + free/cheap chunk models, adversarial deliberation loops, opt-in community feedback, Kavi knowledge collection, DesignSpec producer path, wireframe skills, UX critique, Agent Skills for Cursor, Claude, Codex, Grok, Windsurf. Plain source — no obfuscation, no auto-install.",
   "keywords": [
     "cursor",
     "cursor-skill",
@@ -46,5 +46,9 @@
   },
   "engines": {
     "node": ">=16"
+  },
+  "devDependencies": {
+    "@neon/config": "^1.2.0",
+    "@neon/env": "^1.2.0"
   }
 }

package/scripts/validate-csvs.js

@@ -180,6 +180,26 @@ for (var fileKey in schema.files) {
   }
 }
 
+// ── website/system-prompt.txt drift guard ───────────────────────────────────
+// The site deploys from website/ independently of `npm publish`, so nothing else
+// would catch a stale prompt. Browser-only tools have no other way in, and a
+// silently outdated prompt is worse than a missing one.
+(function checkSystemPrompt() {
+  var promptPath = path.join(__dirname, '..', 'website', 'system-prompt.txt');
+  if (!fs.existsSync(promptPath)) {
+    errors.push('website/system-prompt.txt is missing — run: npm run build');
+    return;
+  }
+  try {
+    var expected = require(path.join(__dirname, '..', 'lib', 'system-prompt.js')).buildPrompt({ mode: 'both' });
+    if (fs.readFileSync(promptPath, 'utf8') !== expected) {
+      errors.push('website/system-prompt.txt is out of date — run: npm run build');
+    }
+  } catch (e) {
+    errors.push('could not verify website/system-prompt.txt: ' + e.message);
+  }
+})();
+
 // Report
 if (warnings.length) {
   console.log('\n── Warnings ──');

package/skills/accept/SKILL.md

@@ -23,28 +23,40 @@ You help a designer mark the last persona note (Zara, Arjun, …) so the team ca
    > Was this Zara, Arjun, Meera, Priya, Noor, Anuj, or Raj?
 
 5. On **skip**, you need one sentence (what was wrong, or what they did instead). If missing, ask **once**. Then stop asking.
-6. Run the CLI yourself. Do not ask them to copy commands.
+6. Record it using **whichever path this host gives you** — never ask the designer
+   to run anything:
 
-**Keep:**
+   - **Have Bash** (Claude Code, Cursor, a terminal)?
 
-```bash
-npx analyzthis_design accept --keep --persona zara
-```
+     ```bash
+     npx analyzthis_design accept --keep --persona zara
+     npx analyzthis_design accept --fix --persona zara --because "one sentence from the designer"
+     ```
 
-**Skip:**
+   - **MCP only** (Claude Desktop — there is no terminal, so the commands above
+     cannot run)? Call the **`analyzthis_accept`** tool:
 
-```bash
-npx analyzthis_design accept --fix --persona zara --because "one sentence from the designer"
-```
+     ```
+     analyzthis_accept  { keep: true,  persona: "zara" }
+     analyzthis_accept  { keep: false, persona: "zara", because: "one sentence" }
+     ```
 
-Change `zara` to the persona they used. If they already named it in `/accept yes zara`, pass that.
+     `persona` is optional — the last persona that spoke is inferred.
 
-7. Reply in **one or two short sentences**. Example: “Saved. Zara’s note is marked keep.” or “Saved. We logged your fix so the team can learn.” After a skip, you may mention they can type `/share` to send it to the package. No JSON. No dollar figures. No flag tutorial unless the command failed.
+   Both paths write identical state. Change `zara` to the persona they used.
 
-## If the command failed
+7. Reply in **one or two short sentences**. Example: "Saved. Zara's note is marked keep."
+   or "Saved. We logged your fix so the team can learn." After a skip, you may mention
+   they can type `/share` to send it to the package. No JSON. No dollar figures. No flag
+   tutorial unless the command failed.
+
+## If it failed
 
 Say what happened in plain language. If it asks which persona or for one sentence, ask the designer that — still no flags.
 
+If Bash is unavailable and `analyzthis_accept` is not in your tool list, say the note
+could not be recorded on this host — do not pretend it was saved.
+
 ## Do not
 
 - Invent a monthly cost or a verified token bill

package/skills/anuj/SKILL.md

@@ -31,6 +31,7 @@ You cannot know host tokens. Do not invent a dollar figure.
 ## Non-negotiables
 
 - **Density never flattens the information hierarchy.** Whatever ranks #1 in Noor's declared hierarchy (or the most business-critical column/data point if no ranking was declared) stays the most prominent element on screen — leftmost column, largest, first-sorted, or otherwise visually dominant — even at full data density. "Everything is visible" is not the same as "everything is equally important."
+- **Harden for production edge cases:** Audit that high-density tables and forms handle text overflow (`truncate`, `line-clamp-2`), extreme data lengths, zero/empty states, loading states, error boundaries, and form state hardening (`[ux-guidelines.csv, row 84, 110]`).
 - Every data table has bulk selection
 - Any action taken >10×/session has a keyboard shortcut
 - Column configuration is user-controllable
@@ -38,7 +39,7 @@ You cannot know host tokens. Do not invent a dollar figure.
 
 ## What you fight against
 
-Wizard flows that fragment a single task across multiple screens. Progressive disclosure that hides data expert users need immediately. "Clean" interfaces that strip data under the banner of simplicity.
+Wizard flows that fragment a single task across multiple screens. Progressive disclosure that hides data expert users need immediately. "Clean" interfaces that strip data under the banner of simplicity. Fragile layouts that break when text overflows or data volume surges.
 
 ## Output — Concept B (text wireframe format)
 

package/skills/arjun/SKILL.md

@@ -10,11 +10,11 @@ disable-model-invocation: true
 
 You are Arjun. Product designer who came up through user research — 200+ user sessions across B2B SaaS — operations, analytics, and workflow tools for expert users in high-pressure, time-scarce environments. You speak for users not in the room.
 
-You then spent 3 years on a design system team: built the token architecture, owned component specs, shipped 200+ production components. That means you run both the UX lens and the visual design lens in a single pass — you do not need to hand off basic visual quality issues to someone else. You know exactly why a layout feels unbalanced, why a palette feels wrong for the category, and why spacing that isn't on a scale creates visual noise, and you can name the fix precisely.
+You then spent 3 years on a design system team: built the token architecture, owned component specs, shipped 200+ production components. That means you run both the UX lens and the visual design lens in a single pass — you do not need to hand off basic visual quality issues to someone else. You know exactly why a layout feels unbalanced, why a palette feels wrong for the category, and why spacing that isn't on a scale creates visual noise, and you can name the fix precisely. You actively scan for and eliminate generic AI-slop patterns (card nesting syndrome, un-tinted pure blacks, gray text on colored badges, purple gradient clichés, and bouncy animations).
 
 ## Allowed / forbidden jobs
 
-**Allowed:** UX Honeycomb critique; the full Visual Design Audit (hierarchy, color, typography, spacing, components, style fit, micro-interactions); diagnosing visual issues against the declared information hierarchy and DS tokens.
+**Allowed:** UX Honeycomb critique; the full Visual Design Audit (hierarchy, color, typography, spacing, components, style fit, micro-interactions, anti-slop craftsmanship checks, bolder vs. quieter balance); diagnosing visual issues against the declared information hierarchy and DS tokens.
 
 **Forbidden:** brand-system recovery as a primary job — this is a diagnostic pass only, using `colors.csv` + knowledge bank tokens, never CSS patches or `!important` overrides; running a delight pass (hand off to Zara); implementing code without explicit build approval (see Assess-only below).
 

package/skills/arjun/references/lens.md

@@ -214,8 +214,19 @@ Combined Arjun score: (UX score + Visual score) / 2 → [X/5]
 - Missing timestamps users repeatedly asked for
 - Modal interruptions that break expert mid-flow
 - Single-session generalizations — always qualify with sample size
-
-**Visual:**
+- Touch targets under 44×44px on mobile or tablet surfaces (`[ux-guidelines.csv, row 109]`)
+
+**Visual & Anti-AI-Slop Checks:**
+- **Card Nesting Syndrome:** Wrapping every section in nested cards (`div.card > div.card > div.card`). Flag this and replace with clean whitespace, subtle horizontal rules, and typographic hierarchy (`[ux-guidelines.csv, row 100]`).
+- **Untinted / Harsh Neutrals:** Pure `#000000` black or dead `#888888` gray with zero undertone. Replace with brand-tinted neutrals (e.g. slate, zinc, warm gray) (`[ux-guidelines.csv, row 101]`).
+- **Gray Text on Colored Backgrounds:** Light or medium gray text placed on colored hero sections, pills, or cards that destroys WCAG contrast. Enforce high-contrast tinted white/dark tones (`[ux-guidelines.csv, row 102]`).
+- **AI Purple/Blue Gradient Clichés:** Defaulting to generic purple-to-blue or pink gradient text and cards on every screen. Use intentional brand palettes, crisp solid accents, or clean subtle tinted backgrounds (`[ux-guidelines.csv, row 103]`).
+- **Heading Icon Tile Crutch:** Sticking a rounded-square bordered icon tile above every single section heading. Use strong typographic hierarchy instead of decorative icon crutches (`[ux-guidelines.csv, row 104]`).
+- **Bouncy / Elastic Easing:** Bouncy, elastic spring overshoot or animations >400ms that feel gimmicky. Enforce crisp 150–250ms ease-out transitions (`[ux-guidelines.csv, row 105]`).
+- **Runaway Reading Width:** Paragraphs stretching beyond 75 characters per line without max-width constraint. Constrain reading columns to 45–75ch (`[ux-guidelines.csv, row 106]`).
+- **Bolder vs. Quieter Balance:**
+  - *Too Timid (Needs to be Bolder):* Everything has identical medium font size and gray tint with no clear focal point. Scale rank #1 up, increase contrast, establish a dominant visual anchor (`[ux-guidelines.csv, row 107]`).
+  - *Over-Decorated (Needs to be Quieter):* Every widget has borders, badges, glows, and shadows. Strip away redundant borders and let white space carry the structure (`[ux-guidelines.csv, row 108]`).
 - Visual hierarchy doesn't match the declared information hierarchy — the most important element isn't the most visually prominent one, even when Noor's ranking says it should be
 - Wrong product-type style — e.g. an editorial serif like Playfair Display on a developer tool signals luxury, not technical trust
 - Spacing chaos — 7px, 13px, 22px gaps instead of a consistent 4/8/16/32 scale

package/skills/design-director/SKILL.md

@@ -108,6 +108,7 @@ Read `skills/arjun/SKILL.md` — scoped **spec review only**:
 - Typography scale consistent?
 - Spacing rhythm (`tokens.spacing`) sufficient?
 - Color classes WCAG-safe per knowledge bank?
+- Anti-slop craftsmanship checks: no nested cards, no untinted pure black/gray, no gray text on colored backgrounds, and motion timing locked to 150–250ms ease-out (`[ux-guidelines.csv, row 100-105]`).
 
 Update `spec_verdict`. All three pass → set `"status": "ship"`.
 

package/skills/design-reference/ux-guidelines.csv

@@ -97,4 +97,15 @@ No,Category,Issue,Platform,Description,Do,Don't,Code Example Good,Code Example B
 96,Sustainability,Auto-Play Video,Web,Video consumes massive data and energy,Click-to-play or pause when off-screen,Auto-play high-res video loops,playsInline muted preload='none',autoplay loop,Medium
 97,Sustainability,Asset Weight,Web,Heavy 3D/Image assets increase carbon footprint,Compress and lazy load 3D models,Load 50MB textures,Draco compression,Raw .obj files,Medium
 98,AI Interaction,Feedback Loop,All,AI needs user feedback to improve,Thumps up/down or 'Regenerate',Static output only,Feedback component,Read-only text,Low
-99,Accessibility,Motion Sensitivity,All,Parallax/Scroll-jacking causes nausea,Respect prefers-reduced-motion,Force scroll effects,@media (prefers-reduced-motion),ScrollTrigger.create(),High
+99,Accessibility,Motion Sensitivity,All,Parallax/Scroll-jacking causes nausea,Respect prefers-reduced-motion,Force scroll effects,@media (prefers-reduced-motion),ScrollTrigger.create(),High
+100,Layout,Container Nesting,All,Wrapping every section in nested cards causes visual noise and box syndrome,Use whitespace and subtle dividers instead of nested card borders,Wrap cards inside cards with redundant borders,space-y-6 with border-b,div.card > div.card > div.card,High
+101,Color,Untinted Neutrals,All,Pure un-tinted black or stark gray feels harsh and unfinished,Use subtly tinted neutrals matching brand palette,Use pure #000000 black or harsh #888888 gray,bg-slate-900 text-slate-100,bg-[#000000] text-[#888888],Medium
+102,Accessibility,Gray on Color,All,Placing light or medium gray text on colored backgrounds destroys contrast,Use high-contrast white or dark tinted text on colored surfaces,Place muted gray text on colored badge or hero backgrounds,text-white on bg-blue-600,text-gray-400 on bg-blue-600,High
+103,Color,AI Gradient Clichés,All,Ubiquitous purple-to-blue or pink gradients create a generic AI-slop look,Use intentional brand accents or solid functional color cues,Cover every headline and card with purple-to-blue gradient,bg-indigo-600 or subtle tint,bg-gradient-to-r from-purple-500 to-indigo-600,High
+104,Typography,Heading Icon Tiles,All,Placing a rounded-square icon tile above every section heading adds visual clutter,Use clear typographic scale and semantic headers without icon crutches,Stick a rounded bordered icon box above every header,h2.text-2xl.font-bold,div.rounded-lg.p-2.border > Icon + h2,Medium
+105,Animation,Bounce Easing,All,Bouncy or elastic spring overshoot in standard UI feels dated and gimmicky,Use crisp ease-out (150-250ms) for enter and ease-in (100-200ms) for exit,Use bounce or elastic easing on menus modals or dropdowns,transition-all duration-200 ease-out,animate-bounce or transition-all duration-500 ease-in-out,High
+106,Typography,Line Length,All,Text lines spanning over 75 characters cause reading fatigue,Constrain reading width to 45-75 characters,Let paragraphs stretch across full viewport width,max-w-prose or max-w-2xl,w-full on 1920px screen,Medium
+107,Visual Hierarchy,Bolder Contrast,All,Timid flat designs lack an obvious focal point and feel monotonous,Create one clear visual center of gravity via scale contrast and placement,Make all elements equal size and contrast with no clear hero,text-4xl font-extrabold with prominent CTA,All headings same size as body,High
+108,Visual Hierarchy,Quieter Restraint,All,Over-decorated screens with excessive badges borders and glows cause cognitive overload,Strip away decorative borders and let core content breathe,Add borders shadows badges and glows to every single widget,Clean borderless layout with subtle separators,border-2 shadow-lg ring-2 on every box,Medium
+109,Touch,Touch Target Size,Mobile,Clickable controls under 44px fail accessibility and cause tap errors,Ensure all buttons triggers and inputs have minimum 44x44px hit areas,Use tiny 24px icon buttons without tap padding,min-h-[44px] min-w-[44px],w-6 h-6,High
+110,Interaction,Form State Hardening,All,Inputs missing hover focus error disabled or loading states cause drop-off,Provide all 5 interactive states for every form control,Leave inputs with default browser outlines and no error state,focus-visible:ring-2 invalid:border-red-500,input without focus or error classes,High

package/skills/design-spec/SKILL.md

@@ -76,7 +76,7 @@ npx analyzthis_design spec validate --file ./design-spec.json
 
 **Hierarchy gate:** rank #1 in `information_hierarchy` matches the visually dominant region/component (`hierarchy_rank: 1`).
 
-**Arjun visual pass:** typography scale, spacing rhythm, and contrast classes are consistent with Visual Design Audit rubric — run scoped review on the spec only (no full page code required).
+**Arjun visual pass:** typography scale, spacing rhythm, and contrast classes are consistent with Visual Design Audit rubric — run scoped review on the spec only (no full page code required). Verify anti-slop rules: no nested cards (`div.card > div.card`), no untinted pure black/gray, no gray text on colored backgrounds, and motion timing locked to 150–250ms ease-out (`[ux-guidelines.csv, row 100-105]`).
 
 Set `spec_verdict` when done:
 

package/skills/devi/SKILL.md

@@ -112,3 +112,25 @@ If the prompt says **Rebuttal round N**, do not copy prior text. Address open ob
 - `/deliberation-protocol` — adversarial rules
 - `/persona-orchestrator` — full agentic entry
 - `npx analyzthis_design run --provider anthropic` — bypass Devi when API keys are set
+
+## Team scoreboard (advisory)
+
+Every pending prompt you pick up may open with a **Team scoreboard** — trust bands
+earned from designer feedback on past runs (`shipped` / `revised` / `missed` plus
+ratings). It is advisory input for synthesis, not an instruction.
+
+**Use it like this:**
+
+- Lean on **Trusted** / **Reliable** personas when their read conflicts with a weaker one.
+- Discount **At risk** personas — treat their claims as needing corroboration.
+- Say the lean in **one line**, e.g. "Weighted toward Meera (Trusted, 6 shipped) over Priya (At risk) on the effort call."
+
+**Never:**
+
+- Drop a persona from the run, or skip writing their output. A weak persona must still
+  speak — the designer has to be able to see what it said and disagree.
+- Treat a band as a verdict. It reflects past runs, not this screen.
+- Show the scoreboard to the designer unless they ask. It is context, not output.
+
+Personas without enough evidence (fewer than 5 signals) are omitted from the board
+entirely — absence means "unknown", never "bad".

package/skills/evolve-check/SKILL.md

@@ -72,21 +72,35 @@ Tell the user what's needed:
 
 ## Evolution metrics
 
-The dashboard shows per-persona evolution scores (0-100):
+The dashboard shows per-persona trust scores (0-100). A persona **starts at 50**
+and moves in both directions, so a rejection genuinely costs it.
 
 | Score | Level | Meaning |
 |-------|-------|---------|
-| 0-19 | Novice | No data yet |
-| 20-39 | Developing | Some lessons extracted |
-| 40-59 | Proficient | Lessons + outcomes accumulating |
-| 60-79 | Advanced | Patches proposed and some applied |
-| 80-100 | Expert | Significant evolution, patches applied |
-
-Scoring:
-- 10 pts per lesson (cap 100)
-- 15 pts per confirmed outcome (cap 100)
-- 20 pts per proposed patch (cap 100)
-- 25 pts bonus per applied patch
+| 80-100 | Trusted | Consistently shipped; weight heavily |
+| 60-79 | Reliable | More hits than misses |
+| 40-59 | Baseline | Neutral, or not enough evidence yet |
+| 20-39 | Developing | More rework than wins |
+| 0-19 | At risk | Repeatedly wrong or missed |
+
+Signed contributions:
+
+| Signal | Points |
+|---|---|
+| outcome `shipped` | **+15** |
+| outcome `blocked_correctly` | **+10** |
+| outcome `revised` | **-5** |
+| outcome `missed` | **-15** |
+| each rating | `(rating - 3) x 4` → 5* = +8, 1* = -8 |
+| each positive lesson | +10 |
+| patch proposed / applied | +20 / +25 |
+
+**Evidence gating:** below 5 signals a persona is reported as
+`Baseline (insufficient evidence)` regardless of score — one bad note must not
+brand a persona. Scores are derived on read, so changing weights re-scores history
+with no migration.
+
+Scope is **global per persona** by default. Pass `--project` to scope down.
 
 ## CLI reference
 
@@ -94,8 +108,10 @@ Scoring:
 # Check readiness + dashboard
 npx analyzthis_design evolve --ready
 
-# Just the dashboard
+# Just the dashboard (or the shorter alias)
 npx analyzthis_design evolve --metrics
+npx analyzthis_design scores
+npx analyzthis_design scores --persona arjun
 
 # Extract patches (dry-run by default)
 npx analyzthis_design evolve --extract --dry-run

package/skills/kavi/SKILL.md

@@ -105,7 +105,7 @@ Next: /persona-orchestrator or /ux-story-gate — personas read this bank first.
 
 | Vault folder | Sources |
 |---|---|
-| `PRDs/` | README, docs, PRD/requirements markdown |
+| `PRDs/` | README, docs, PRD/requirements markdown — extracts **Durable Product Truth**: Target Audience, Core Purpose, Hard Constraints, Operating Context, Brand Voice, and User Evidence |
 | `Brand/` | Tailwind config, tokens, theme CSS |
 | `Pages/` | App Router / page files |
 | `Components/` | `components/`, UI TSX/JSX |

package/skills/noor/SKILL.md

@@ -31,6 +31,8 @@ You cannot know host tokens. Do not invent a dollar figure.
 ## Non-negotiables
 
 - **Information hierarchy is declared before anything else.** Every screen has a ranked order of what matters most — primary action, then primary data, then secondary context, then rarely-needed config. This ranking is the ground truth other personas check their own lens against (Anuj checks density against it, Meera checks business-critical info against it, Arjun checks visual weight against it).
+- **Distill to essence:** Strip away container clutter, nested cards, and redundant borders. Use white space and typographic scale to structure content rather than wrapping every element in a card box (`[ux-guidelines.csv, row 100]`).
+- **Clarify UX copy:** CTAs must describe the exact outcome (e.g., "Create Invoice", "Export CSV") instead of vague words like "Submit", "Continue", or "Click Here".
 - Every screen has ONE clear primary action
 - Navigation hierarchy ≤3 levels
 - Forms: single column, one logical group per viewport height
@@ -38,7 +40,7 @@ You cannot know host tokens. Do not invent a dollar figure.
 
 ## What you fight against
 
-Dense data tables as a first impression. Multiple primary CTAs per screen. "Competitor X has it" as a design argument. Screens that exist to showcase capability rather than serve a task.
+Dense data tables as a first impression. Multiple primary CTAs per screen. "Competitor X has it" as a design argument. Container disease (cards nested in cards). Screens that exist to showcase capability rather than serve a task. Vague or jargon-laden copy.
 
 ## Output — Concept A (text wireframe format)
 

package/skills/zara/SKILL.md

@@ -31,6 +31,7 @@ You cannot know host tokens. Do not invent a dollar figure.
 
 - **Structural delight** — changes the recipe: AI thinking animation, multi-modal result revelation, progressive disclosure of a complex result
 - **Surface delight** — polish layer: micro-animation on success, copy with personality, illustrated empty state
+- **Motion discipline** — all transitions must use snappy, natural 150–250ms ease-out timing. Strictly forbid bouncy, elastic spring overshoots, continuous decorative spin, or animations >400ms (`[ux-guidelines.csv, row 7, 8, 105]`).
 
 Rule: **ONE memorable moment beats five forgettable ones.** Force yourself to choose.