analyzthis_design 2.4.1 → 2.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -4,6 +4,37 @@ A set of AI design personas and a task-first evaluation framework that plugs int
4
4
 
5
5
  Install once. Run structured UX critiques, multi-phase ideation, and task-grounded screen reviews — directly inside your AI chat. **No external LLM API keys required** for CLI orchestrator runs: **`/devi`** voices each persona from your host IDE (Cursor, Claude, etc.).
6
6
 
7
+ ## v2.5.0 — personas earn or lose trust
8
+
9
+ Marking a note now moves a score. Previously a rejection *raised* a persona's score by
10
+ 15 — `accept.fix()` recorded `outcome: 'revised'` and scoring counted outcomes without
11
+ reading their value. Punishment was a reward. Fixed.
12
+
13
+ - **Signed, rate-based scoring.** A persona starts at 50 and moves both ways:
14
+ `shipped` +15, `blocked_correctly` +10, `revised` −5, `missed` −15, plus
15
+ `(rating − 3) x 4` per rating. Scored as a **rate per signal**, not a running total,
16
+ so early wins can never make a persona immune to later failures.
17
+ - **Evidence gating.** Under 5 signals a persona reads `Baseline (insufficient
18
+ evidence)`. One bad note does not brand anyone.
19
+ - **Bands:** At risk · Developing · Baseline · Reliable · Trusted.
20
+ - **Devi gets a scoreboard** in every pending prompt and weights its synthesis,
21
+ saying the lean in one line. Advisory only — **no persona is ever dropped from a run.**
22
+ - **Feedback works with no terminal.** New `analyzthis_accept` MCP tool in the
23
+ **lite** catalog, so Claude Desktop can record keep/skip. Same shared core as the
24
+ CLI — both transports write identical state.
25
+ - **The persona asks.** Every note ends with one host-neutral line: *"Was this right?
26
+ Say yes, or no plus one sentence."* The designer answers in plain language; the
27
+ agent picks the transport. No flags, ever.
28
+ - **Lessons learn from rejections too**, tagged `polarity`, and de-duplicated so
29
+ re-marking a note cannot inflate a score.
30
+
31
+ ```bash
32
+ npx analyzthis_design scores # the whole team
33
+ npx analyzthis_design scores --persona arjun # one persona, with the breakdown
34
+ ```
35
+
36
+ Scores are derived on read — changing the weights re-scores history with no migration.
37
+
7
38
  ## v2.4.1 — `/accept` and `/share` (designer keep / skip / send)
8
39
 
9
40
  After `/zara` (or any persona), type `/accept yes` or `/accept no` plus one sentence. No CLI flags. Writes keep or skip for **local** evolution. Slash-only notes still count.
@@ -54,7 +85,7 @@ Pass `--global` to opt into the legacy merged behavior (read `config.sources` an
54
85
 
55
86
  Use `npx analyzthis_design run-unchunked` for the legacy single-pass orchestrator.
56
87
 
57
- **npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.4.1 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
88
+ **npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.5.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
58
89
 
59
90
  ---
60
91
 
@@ -80,7 +111,7 @@ npx analyzthis_design run-unchunked --task "Review invoice approval screen" --pr
80
111
 
81
112
  > **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design install --target <ide>` (or `npx analyzthis_design --target <ide>`).
82
113
  >
83
- > **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. For Lovable, v0, Bolt, Replit, ChatGPT: run `npx analyzthis_design mcp --configure <tool>` for a config snippet.
114
+ > **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. **Browser-only tools (Lovable, v0, Bolt, Replit, ChatGPT) cannot use MCP here** — our server speaks stdio, and a cloud-hosted tool cannot spawn a process on your machine. Paste the team in instead: `npx analyzthis_design system-prompt --mode both`, or copy it with one click from [the tool picker](https://analyzthis-lab.vercel.app/design#install-lovable). Note the paste path gives you the personas but no `/accept`, lessons, or trust scores — those need local state.
84
115
 
85
116
  ### Install by target IDE
86
117
 
@@ -893,7 +924,7 @@ skills/
893
924
  |---------|-------------|
894
925
  | **MCP server** | `npx analyzthis_design mcp` starts a local MCP server exposing 19 tools — all 8 individual personas + 6 combination passes + 5 utilities. Any MCP-compatible client can discover and call them. |
895
926
  | **Auto-configure MCP** | `npx analyzthis_design mcp --configure cursor` (or `claude`, `windsurf`) writes the MCP config automatically. `--target all` now auto-configures MCP during install. |
896
- | **Universal IDE support** | Cursor, Claude Desktop, Windsurf auto-configured. Lovable, v0, Bolt, Replit, ChatGPT: run `mcp --configure <tool>` for a copy-paste config snippet. |
927
+ | **Universal IDE support** | Cursor, Claude Code, Claude Desktop, Windsurf auto-configured via MCP. Lovable, v0, Bolt, Replit, ChatGPT install nothing paste `system-prompt` output into the tool's instructions. |
897
928
  | **MCP lite + full** | Default: router (`analyzthis_design`) + retrieve + session + receipt. Full 19 named tools behind `--catalog full`. |
898
929
  | **System prompt fallback** | `analyzthis_system_prompt` tool generates a consolidated prompt for tools that don't support MCP yet |
899
930
 
@@ -958,7 +989,7 @@ skills/
958
989
 
959
990
  ## Marketing site
960
991
 
961
- The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). Copy now names two doors: lab products for people who already use Cursor or Claude, and custom teams that arrive in a firm’s existing tools. The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
992
+ The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). The home page keeps the packet story and offers three paths: designers (`design.html`), Dev/PMs (three jobs + workspace warning), and firm owners (map one workflow). The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
962
993
 
963
994
  - Live: [https://analyzthis-lab.vercel.app](https://analyzthis-lab.vercel.app)
964
995
  - Design team deep-dive: [https://analyzthis-lab.vercel.app/design](https://analyzthis-lab.vercel.app/design) (`website/design.html`)
@@ -26,3 +26,16 @@ Full Concept B text wireframe (hierarchy check, primary action, nav level, visib
26
26
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
27
27
 
28
28
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
29
+
30
+ ## Closing line (always)
31
+
32
+ End every reply with this line, exactly:
33
+
34
+ ```
35
+
36
+ Was this right? Say yes, or no plus one sentence. I'll record it.
37
+ ```
38
+
39
+ If the designer answers, record it with whatever path you have — Bash
40
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
41
+ them to type a command, and never mention flags.
@@ -27,3 +27,16 @@ Full UX Critique + Visual Design Audit blocks with per-dimension reasons — see
27
27
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
28
28
 
29
29
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
30
+
31
+ ## Closing line (always)
32
+
33
+ End every reply with this line, exactly:
34
+
35
+ ```
36
+
37
+ Was this right? Say yes, or no plus one sentence. I'll record it.
38
+ ```
39
+
40
+ If the designer answers, record it with whatever path you have — Bash
41
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
42
+ them to type a command, and never mention flags.
@@ -13,3 +13,25 @@ run --task "..." → pending/001-arjun.json → /devi → responses/001-ar
13
13
  ```
14
14
 
15
15
  See `skills/devi/SKILL.md` for the full protocol.
16
+
17
+ ## Team scoreboard (advisory)
18
+
19
+ Every pending prompt you pick up may open with a **Team scoreboard** — trust bands
20
+ earned from designer feedback on past runs (`shipped` / `revised` / `missed` plus
21
+ ratings). It is advisory input for synthesis, not an instruction.
22
+
23
+ **Use it like this:**
24
+
25
+ - Lean on **Trusted** / **Reliable** personas when their read conflicts with a weaker one.
26
+ - Discount **At risk** personas — treat their claims as needing corroboration.
27
+ - Say the lean in **one line**, e.g. "Weighted toward Meera (Trusted, 6 shipped) over Priya (At risk) on the effort call."
28
+
29
+ **Never:**
30
+
31
+ - Drop a persona from the run, or skip writing their output. A weak persona must still
32
+ speak — the designer has to be able to see what it said and disagree.
33
+ - Treat a band as a verdict. It reflects past runs, not this screen.
34
+ - Show the scoreboard to the designer unless they ask. It is context, not output.
35
+
36
+ Personas without enough evidence (fewer than 5 signals) are omitted from the board
37
+ entirely — absence means "unknown", never "bad".
@@ -24,3 +24,16 @@ Next: run /persona-orchestrator or any critique persona — they read this bank
24
24
  ```
25
25
 
26
26
  Consult `skills/kavi/SKILL.md` for the host workflow. Prefer running `npx analyzthis_design collect` over re-scanning files in chat. Invoke as **`/kavi`** (alias: `/collect-knowledge`).
27
+
28
+ ## Closing line (always)
29
+
30
+ End every reply with this line, exactly:
31
+
32
+ ```
33
+
34
+ Was this right? Say yes, or no plus one sentence. I'll record it.
35
+ ```
36
+
37
+ If the designer answers, record it with whatever path you have — Bash
38
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
39
+ them to type a command, and never mention flags.
@@ -25,3 +25,16 @@ Full Business Impact block (metric impact, hierarchy check, segment, GTM lever,
25
25
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
26
26
 
27
27
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
28
+
29
+ ## Closing line (always)
30
+
31
+ End every reply with this line, exactly:
32
+
33
+ ```
34
+
35
+ Was this right? Say yes, or no plus one sentence. I'll record it.
36
+ ```
37
+
38
+ If the designer answers, record it with whatever path you have — Bash
39
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
40
+ them to type a command, and never mention flags.
@@ -26,3 +26,16 @@ Full Concept A text wireframe (hierarchy, primary action, nav level, visible-on-
26
26
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
27
27
 
28
28
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
29
+
30
+ ## Closing line (always)
31
+
32
+ End every reply with this line, exactly:
33
+
34
+ ```
35
+
36
+ Was this right? Say yes, or no plus one sentence. I'll record it.
37
+ ```
38
+
39
+ If the designer answers, record it with whatever path you have — Bash
40
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
41
+ them to type a command, and never mention flags.
@@ -25,3 +25,16 @@ Full Feasibility Analysis block (score, blockers, ranked risks, effort, simpler
25
25
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
26
26
 
27
27
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
28
+
29
+ ## Closing line (always)
30
+
31
+ End every reply with this line, exactly:
32
+
33
+ ```
34
+
35
+ Was this right? Say yes, or no plus one sentence. I'll record it.
36
+ ```
37
+
38
+ If the designer answers, record it with whatever path you have — Bash
39
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
40
+ them to type a command, and never mention flags.
@@ -27,3 +27,16 @@ What [losing agent] gives up: [named]
27
27
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
28
28
 
29
29
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
30
+
31
+ ## Closing line (always)
32
+
33
+ End every reply with this line, exactly:
34
+
35
+ ```
36
+
37
+ Was this right? Say yes, or no plus one sentence. I'll record it.
38
+ ```
39
+
40
+ If the designer answers, record it with whatever path you have — Bash
41
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
42
+ them to type a command, and never mention flags.
@@ -28,3 +28,16 @@ Full Delight Pass block (surface, moment, type, specific addition, why-this-one,
28
28
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
29
29
 
30
30
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
31
+
32
+ ## Closing line (always)
33
+
34
+ End every reply with this line, exactly:
35
+
36
+ ```
37
+
38
+ Was this right? Say yes, or no plus one sentence. I'll record it.
39
+ ```
40
+
41
+ If the designer answers, record it with whatever path you have — Bash
42
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
43
+ them to type a command, and never mention flags.
package/dist/README.md CHANGED
@@ -4,6 +4,37 @@ A set of AI design personas and a task-first evaluation framework that plugs int
4
4
 
5
5
  Install once. Run structured UX critiques, multi-phase ideation, and task-grounded screen reviews — directly inside your AI chat. **No external LLM API keys required** for CLI orchestrator runs: **`/devi`** voices each persona from your host IDE (Cursor, Claude, etc.).
6
6
 
7
+ ## v2.5.0 — personas earn or lose trust
8
+
9
+ Marking a note now moves a score. Previously a rejection *raised* a persona's score by
10
+ 15 — `accept.fix()` recorded `outcome: 'revised'` and scoring counted outcomes without
11
+ reading their value. Punishment was a reward. Fixed.
12
+
13
+ - **Signed, rate-based scoring.** A persona starts at 50 and moves both ways:
14
+ `shipped` +15, `blocked_correctly` +10, `revised` −5, `missed` −15, plus
15
+ `(rating − 3) x 4` per rating. Scored as a **rate per signal**, not a running total,
16
+ so early wins can never make a persona immune to later failures.
17
+ - **Evidence gating.** Under 5 signals a persona reads `Baseline (insufficient
18
+ evidence)`. One bad note does not brand anyone.
19
+ - **Bands:** At risk · Developing · Baseline · Reliable · Trusted.
20
+ - **Devi gets a scoreboard** in every pending prompt and weights its synthesis,
21
+ saying the lean in one line. Advisory only — **no persona is ever dropped from a run.**
22
+ - **Feedback works with no terminal.** New `analyzthis_accept` MCP tool in the
23
+ **lite** catalog, so Claude Desktop can record keep/skip. Same shared core as the
24
+ CLI — both transports write identical state.
25
+ - **The persona asks.** Every note ends with one host-neutral line: *"Was this right?
26
+ Say yes, or no plus one sentence."* The designer answers in plain language; the
27
+ agent picks the transport. No flags, ever.
28
+ - **Lessons learn from rejections too**, tagged `polarity`, and de-duplicated so
29
+ re-marking a note cannot inflate a score.
30
+
31
+ ```bash
32
+ npx analyzthis_design scores # the whole team
33
+ npx analyzthis_design scores --persona arjun # one persona, with the breakdown
34
+ ```
35
+
36
+ Scores are derived on read — changing the weights re-scores history with no migration.
37
+
7
38
  ## v2.4.1 — `/accept` and `/share` (designer keep / skip / send)
8
39
 
9
40
  After `/zara` (or any persona), type `/accept yes` or `/accept no` plus one sentence. No CLI flags. Writes keep or skip for **local** evolution. Slash-only notes still count.
@@ -54,7 +85,7 @@ Pass `--global` to opt into the legacy merged behavior (read `config.sources` an
54
85
 
55
86
  Use `npx analyzthis_design run-unchunked` for the legacy single-pass orchestrator.
56
87
 
57
- **npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.4.1 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
88
+ **npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.5.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
58
89
 
59
90
  ---
60
91
 
@@ -80,7 +111,7 @@ npx analyzthis_design run-unchunked --task "Review invoice approval screen" --pr
80
111
 
81
112
  > **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design install --target <ide>` (or `npx analyzthis_design --target <ide>`).
82
113
  >
83
- > **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. For Lovable, v0, Bolt, Replit, ChatGPT: run `npx analyzthis_design mcp --configure <tool>` for a config snippet.
114
+ > **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. **Browser-only tools (Lovable, v0, Bolt, Replit, ChatGPT) cannot use MCP here** — our server speaks stdio, and a cloud-hosted tool cannot spawn a process on your machine. Paste the team in instead: `npx analyzthis_design system-prompt --mode both`, or copy it with one click from [the tool picker](https://analyzthis-lab.vercel.app/design#install-lovable). Note the paste path gives you the personas but no `/accept`, lessons, or trust scores — those need local state.
84
115
 
85
116
  ### Install by target IDE
86
117
 
@@ -893,7 +924,7 @@ skills/
893
924
  |---------|-------------|
894
925
  | **MCP server** | `npx analyzthis_design mcp` starts a local MCP server exposing 19 tools — all 8 individual personas + 6 combination passes + 5 utilities. Any MCP-compatible client can discover and call them. |
895
926
  | **Auto-configure MCP** | `npx analyzthis_design mcp --configure cursor` (or `claude`, `windsurf`) writes the MCP config automatically. `--target all` now auto-configures MCP during install. |
896
- | **Universal IDE support** | Cursor, Claude Desktop, Windsurf auto-configured. Lovable, v0, Bolt, Replit, ChatGPT: run `mcp --configure <tool>` for a copy-paste config snippet. |
927
+ | **Universal IDE support** | Cursor, Claude Code, Claude Desktop, Windsurf auto-configured via MCP. Lovable, v0, Bolt, Replit, ChatGPT install nothing paste `system-prompt` output into the tool's instructions. |
897
928
  | **MCP lite + full** | Default: router (`analyzthis_design`) + retrieve + session + receipt. Full 19 named tools behind `--catalog full`. |
898
929
  | **System prompt fallback** | `analyzthis_system_prompt` tool generates a consolidated prompt for tools that don't support MCP yet |
899
930
 
@@ -958,7 +989,7 @@ skills/
958
989
 
959
990
  ## Marketing site
960
991
 
961
- The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). Copy now names two doors: lab products for people who already use Cursor or Claude, and custom teams that arrive in a firm’s existing tools. The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
992
+ The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). The home page keeps the packet story and offers three paths: designers (`design.html`), Dev/PMs (three jobs + workspace warning), and firm owners (map one workflow). The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
962
993
 
963
994
  - Live: [https://analyzthis-lab.vercel.app](https://analyzthis-lab.vercel.app)
964
995
  - Design team deep-dive: [https://analyzthis-lab.vercel.app/design](https://analyzthis-lab.vercel.app/design) (`website/design.html`)
@@ -26,3 +26,16 @@ Full Concept B text wireframe (hierarchy check, primary action, nav level, visib
26
26
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
27
27
 
28
28
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
29
+
30
+ ## Closing line (always)
31
+
32
+ End every reply with this line, exactly:
33
+
34
+ ```
35
+
36
+ Was this right? Say yes, or no plus one sentence. I'll record it.
37
+ ```
38
+
39
+ If the designer answers, record it with whatever path you have — Bash
40
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
41
+ them to type a command, and never mention flags.
@@ -27,3 +27,16 @@ Full UX Critique + Visual Design Audit blocks with per-dimension reasons — see
27
27
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
28
28
 
29
29
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
30
+
31
+ ## Closing line (always)
32
+
33
+ End every reply with this line, exactly:
34
+
35
+ ```
36
+
37
+ Was this right? Say yes, or no plus one sentence. I'll record it.
38
+ ```
39
+
40
+ If the designer answers, record it with whatever path you have — Bash
41
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
42
+ them to type a command, and never mention flags.
@@ -13,3 +13,25 @@ run --task "..." → pending/001-arjun.json → /devi → responses/001-ar
13
13
  ```
14
14
 
15
15
  See `skills/devi/SKILL.md` for the full protocol.
16
+
17
+ ## Team scoreboard (advisory)
18
+
19
+ Every pending prompt you pick up may open with a **Team scoreboard** — trust bands
20
+ earned from designer feedback on past runs (`shipped` / `revised` / `missed` plus
21
+ ratings). It is advisory input for synthesis, not an instruction.
22
+
23
+ **Use it like this:**
24
+
25
+ - Lean on **Trusted** / **Reliable** personas when their read conflicts with a weaker one.
26
+ - Discount **At risk** personas — treat their claims as needing corroboration.
27
+ - Say the lean in **one line**, e.g. "Weighted toward Meera (Trusted, 6 shipped) over Priya (At risk) on the effort call."
28
+
29
+ **Never:**
30
+
31
+ - Drop a persona from the run, or skip writing their output. A weak persona must still
32
+ speak — the designer has to be able to see what it said and disagree.
33
+ - Treat a band as a verdict. It reflects past runs, not this screen.
34
+ - Show the scoreboard to the designer unless they ask. It is context, not output.
35
+
36
+ Personas without enough evidence (fewer than 5 signals) are omitted from the board
37
+ entirely — absence means "unknown", never "bad".
@@ -24,3 +24,16 @@ Next: run /persona-orchestrator or any critique persona — they read this bank
24
24
  ```
25
25
 
26
26
  Consult `skills/kavi/SKILL.md` for the host workflow. Prefer running `npx analyzthis_design collect` over re-scanning files in chat. Invoke as **`/kavi`** (alias: `/collect-knowledge`).
27
+
28
+ ## Closing line (always)
29
+
30
+ End every reply with this line, exactly:
31
+
32
+ ```
33
+
34
+ Was this right? Say yes, or no plus one sentence. I'll record it.
35
+ ```
36
+
37
+ If the designer answers, record it with whatever path you have — Bash
38
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
39
+ them to type a command, and never mention flags.
@@ -25,3 +25,16 @@ Full Business Impact block (metric impact, hierarchy check, segment, GTM lever,
25
25
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
26
26
 
27
27
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
28
+
29
+ ## Closing line (always)
30
+
31
+ End every reply with this line, exactly:
32
+
33
+ ```
34
+
35
+ Was this right? Say yes, or no plus one sentence. I'll record it.
36
+ ```
37
+
38
+ If the designer answers, record it with whatever path you have — Bash
39
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
40
+ them to type a command, and never mention flags.
@@ -26,3 +26,16 @@ Full Concept A text wireframe (hierarchy, primary action, nav level, visible-on-
26
26
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
27
27
 
28
28
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
29
+
30
+ ## Closing line (always)
31
+
32
+ End every reply with this line, exactly:
33
+
34
+ ```
35
+
36
+ Was this right? Say yes, or no plus one sentence. I'll record it.
37
+ ```
38
+
39
+ If the designer answers, record it with whatever path you have — Bash
40
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
41
+ them to type a command, and never mention flags.
@@ -25,3 +25,16 @@ Full Feasibility Analysis block (score, blockers, ranked risks, effort, simpler
25
25
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
26
26
 
27
27
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
28
+
29
+ ## Closing line (always)
30
+
31
+ End every reply with this line, exactly:
32
+
33
+ ```
34
+
35
+ Was this right? Say yes, or no plus one sentence. I'll record it.
36
+ ```
37
+
38
+ If the designer answers, record it with whatever path you have — Bash
39
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
40
+ them to type a command, and never mention flags.
@@ -27,3 +27,16 @@ What [losing agent] gives up: [named]
27
27
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
28
28
 
29
29
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
30
+
31
+ ## Closing line (always)
32
+
33
+ End every reply with this line, exactly:
34
+
35
+ ```
36
+
37
+ Was this right? Say yes, or no plus one sentence. I'll record it.
38
+ ```
39
+
40
+ If the designer answers, record it with whatever path you have — Bash
41
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
42
+ them to type a command, and never mention flags.
@@ -28,3 +28,16 @@ Full Delight Pass block (surface, moment, type, specific addition, why-this-one,
28
28
  **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
29
29
 
30
30
  **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
31
+
32
+ ## Closing line (always)
33
+
34
+ End every reply with this line, exactly:
35
+
36
+ ```
37
+
38
+ Was this right? Say yes, or no plus one sentence. I'll record it.
39
+ ```
40
+
41
+ If the designer answers, record it with whatever path you have — Bash
42
+ (`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
43
+ them to type a command, and never mention flags.
package/dist/bin/cli.js CHANGED
@@ -1000,6 +1000,60 @@ switch (cmd) {
1000
1000
  break;
1001
1001
  }
1002
1002
 
1003
+ case 'scores': {
1004
+ const em = require('../lib/evolution-metrics');
1005
+ if (flags.includes('--submit') || flags.includes('--submit-dry-run')) {
1006
+ const submitter = require('../lib/feedback-submit');
1007
+ const dry = flags.includes('--submit-dry-run');
1008
+ submitter.submitScores({ dryRun: dry })
1009
+ .then((r) => {
1010
+ if (r.skipped) console.log(`\n Not sent: ${r.skipped}\n`);
1011
+ else if (r.dryRun) console.log(`\n Would send ${r.rows.length} persona score row(s). Counts only — no note text.\n`);
1012
+ else console.log(`\n Sent ${r.sent} persona score row(s).\n`);
1013
+ })
1014
+ .catch((e) => console.log(`\n Submit failed: ${e.message}\n`));
1015
+ break;
1016
+ }
1017
+ const metrics = em.computeEvolutionMetrics(projectVal ? { project: projectVal } : undefined);
1018
+ if (personaVal) {
1019
+ const m = metrics.personas[personaVal];
1020
+ if (!m) {
1021
+ console.log(`\n Unknown persona "${personaVal}". Use: ${em.PERSONAS.join(', ')}\n`);
1022
+ break;
1023
+ }
1024
+ console.log(`\n ${personaVal}: ${m.score}/100 ${m.level}` +
1025
+ (m.sufficient_evidence ? '' : ' (insufficient evidence)'));
1026
+ console.log(` ${m.evidence_count} signal(s) · shipped ${m.outcome_breakdown.shipped}` +
1027
+ ` · revised ${m.outcome_breakdown.revised} · missed ${m.outcome_breakdown.missed}` +
1028
+ (m.avg_rating != null ? ` · avg rating ${m.avg_rating}` : ''));
1029
+ console.log(` contributions: ${JSON.stringify(m.contributions)}\n`);
1030
+ break;
1031
+ }
1032
+ console.log('\n' + em.formatEvolutionSummary(metrics));
1033
+ break;
1034
+ }
1035
+
1036
+ case 'system-prompt': {
1037
+ // The only path into the personas for browser-only tools (Lovable, v0, Bolt,
1038
+ // Replit, ChatGPT). They cannot reach the MCP server — it speaks stdio, and a
1039
+ // cloud-hosted tool cannot spawn a process on the user's machine.
1040
+ const builder = require('../lib/system-prompt');
1041
+ const mode = getFlag('mode') || 'both';
1042
+ if (!['create', 'critique', 'both'].includes(mode)) {
1043
+ console.log(`\n Unknown mode "${mode}". Use: create, critique, or both.\n`);
1044
+ break;
1045
+ }
1046
+ const prompt = builder.buildPrompt({ mode });
1047
+ const out = getFlag('out');
1048
+ if (out) {
1049
+ require('fs').writeFileSync(out, prompt);
1050
+ console.log(`\n Wrote ${prompt.length} chars to ${out}\n Paste it into your tool's system instructions.\n`);
1051
+ } else {
1052
+ console.log(prompt);
1053
+ }
1054
+ break;
1055
+ }
1056
+
1003
1057
  case 'receipt': {
1004
1058
  const receipt = require('../lib/receipt');
1005
1059
  console.log('\n' + receipt.report({ project: projectVal }) + '\n');
@@ -8,6 +8,7 @@
8
8
  var session = require('./session');
9
9
  var feedback = require('./feedback');
10
10
  var outcome = require('./outcome');
11
+ var lessons = require('./lessons');
11
12
 
12
13
  var PERSONA_IDS = session.PERSONA_IDS;
13
14
 
@@ -27,6 +28,16 @@ function resolvePersona(opts) {
27
28
  return id;
28
29
  }
29
30
 
31
+ // Lesson extraction must never break a designer's keep/skip.
32
+ function safeExtract(project, persona) {
33
+ try {
34
+ var r = lessons.extractLessons({ project: project, persona: persona });
35
+ return (r && r.extracted) || 0;
36
+ } catch (e) {
37
+ return 0;
38
+ }
39
+ }
40
+
30
41
  function keep(opts) {
31
42
  opts = opts || {};
32
43
  var persona = resolvePersona(opts);
@@ -36,22 +47,23 @@ function keep(opts) {
36
47
  text: opts.note,
37
48
  });
38
49
  session.markAccepted({ project: opts.project, persona: persona, accepted: true });
39
- if (opts.comment) {
40
- feedback.recordFeedback({
41
- project: opts.project,
42
- persona: persona,
43
- satisfied: true,
44
- rating: 5,
45
- comment: opts.comment,
46
- correction: '',
47
- markRejected: false,
48
- });
49
- }
50
+ // Always record — a bare "/accept yes" is still a rating, and scoring reads it.
51
+ feedback.recordFeedback({
52
+ project: opts.project,
53
+ persona: persona,
54
+ satisfied: true,
55
+ rating: opts.rating != null ? Number(opts.rating) : 5,
56
+ comment: opts.comment || '',
57
+ correction: '',
58
+ tags: ['positive'],
59
+ markRejected: false,
60
+ });
50
61
  var shipped = opts.shipped !== false;
51
62
  if (shipped) {
52
63
  outcome.confirmOutcome({ project: opts.project, persona: persona, outcome: 'shipped' });
53
64
  }
54
- return { persona: persona, kept: true, shipped: shipped };
65
+ var learned = safeExtract(opts.project, persona);
66
+ return { persona: persona, kept: true, shipped: shipped, lessons: learned };
55
67
  }
56
68
 
57
69
  function fix(opts) {
@@ -80,7 +92,8 @@ function fix(opts) {
80
92
  markRejected: true,
81
93
  });
82
94
  outcome.confirmOutcome({ project: opts.project, persona: persona, outcome: 'revised' });
83
- return { persona: persona, kept: false, because: because };
95
+ var learnedFix = safeExtract(opts.project, persona);
96
+ return { persona: persona, kept: false, because: because, lessons: learnedFix };
84
97
  }
85
98
 
86
99
  function preview(opts) {