roast-my-design-system 5.6.0 → 5.6.2

package/README.md

@@ -40,7 +40,7 @@ One scan powers all of it; the flags decide what lands on disk. Combine freely.
 | `... --rules` | The same rules written to `design-system-rules.md` instead, for pasting by hand |
 | `... --card` | `roast-card.svg`: a shareable 1200x630 card with the score and worst findings. Pure SVG, embeds in a README |
 | `... --sarif` | `design-system-roast.sarif` for GitHub code scanning: upload it in CI and findings appear in the Security tab, annotated on files |
-| `... --mcp` | The scan as a local MCP server: five tools your agent calls while writing UI, from "is there a Button already?" to "review my changes". See [Live answers over MCP](#live-answers-over-mcp) |
+| `... --mcp` | The scan as a local MCP server: five tools your agent calls while writing UI, from "is there a Button already?" to "review my changes", plus the `roast-fix` prompt that serves the top fix from a fresh scan. See [Live answers over MCP](#live-answers-over-mcp) |
 | `... --check` | The working tree's changed files checked against the design system, in the terminal. Exits 1 on findings, so it slots into scripts |
 | <code>...&nbsp;--by&nbsp;"Dwayne&nbsp;Hicks"</code> | A requester credit in the report header, next to the scan date |
 | <code>...&nbsp;--notes&nbsp;&lt;file.md&gt;</code> | An agent-written analysis embedded in the report as **"What the numbers mean"**: labelled as written by AI, kept apart from the measured numbers. The Claude Code skill writes and passes this automatically; the flag is here so any agent can |
@@ -61,7 +61,7 @@ One scan powers all of it; the flags decide what lands on disk. Combine freely.
 
 The full report for vercel/ai-chatbot, top to bottom — including "What the numbers mean", Claude's read of the scan, embedded right under the verdict:
 
-![The full diagnosis report for vercel/ai-chatbot in dark mode: health score, the What the numbers mean analysis written by Claude, priced Where to start moves, the wrapped present with the agent rules, an agent trap callout, three-yardstick tiles, the adoption map treemap, palette forensics, spacing receipts, typography specimens, offenders, duplicates, and the component usage ledger](https://raw.githubusercontent.com/gregkozakiewicz/roast-my-design-system/main/assets/report-full-dark.png?v=5.5.1)
+![The full diagnosis report for vercel/ai-chatbot in dark mode: health score, the What the numbers mean analysis written by Claude, priced Where to start moves each with its copy-the-fix-prompt button, the wrapped present with the agent rules, an agent trap callout, three-yardstick tiles, the adoption map treemap, palette forensics, spacing receipts, typography specimens, offenders, duplicates, and the component usage ledger](https://raw.githubusercontent.com/gregkozakiewicz/roast-my-design-system/main/assets/report-full-dark.png?v=5.6.1)
 
 The same report in light mode (one file, built-in toggle):
 
@@ -110,6 +110,10 @@ The report and the rules file describe the repo as it was at scan time. `--mcp`
 
 The loop: context before building, find while building, validate before saving, review before finishing.
 
+And when the goal is fixing the system rather than building on it, the `roast-fix` prompt serves the top Where-to-start move from a fresh scan, as a ready-made fix prompt (byte-identical to the report's copy buttons). Fix it, ask again, and the next move has risen to the top: the scan is the progress bar. Pass `move: 2` to jump the queue.
+
+To use it in Claude Code, type `/mcp__roast__roast-fix` in the chat (MCP prompts appear as slash commands, named after whatever you registered the server as; the `/` autocomplete menu lists them too). Add the move number to jump the queue: `/mcp__roast__roast-fix 2`. Other clients list server prompts in their own prompt picker; wherever `roast-build-ui` and `roast-review-ui` show up, `roast-fix` sits beside them.
+
 Add it to Claude Code:
 
 ```bash

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "roast-my-design-system",
-  "version": "5.6.0",
+  "version": "5.6.2",
   "mcpName": "io.github.gregkozakiewicz/roast-my-design-system",
-  "description": "Your AI can write the UI. This makes sure it writes your UI. A deterministic scanner scores your design system 0-100 against 34 public repos, writes rules for Claude, Cursor, Copilot and Windsurf with --apply, and runs as a local MCP server with --mcp.",
+  "description": "Your AI can write the UI. This makes sure it writes your UI. A deterministic scanner scores your design system 0-100 against 34 public repos, hands you a copy-paste fix prompt for each top finding, writes rules for Claude, Cursor, Copilot and Windsurf with --apply, and runs as a local MCP server with --mcp.",
   "keywords": [
     "design-system",
     "mcp",

package/skills/roast-my-design-system/scripts/diagnose/index.mjs

@@ -890,6 +890,12 @@ function extraSectionsHtml() {
 </section>`).join('\n\n');
 }
 
+// Filled by whereToStartSection when the template renders (which happens
+// before the summary is written): the same moves and prompts the report's
+// buttons hold, published in --summary so the MCP server's roast-fix prompt
+// hands out byte-identical text. One composer, two doors.
+let startMoves = [];
+
 function whereToStartSection() {
   const c = [];
   if (agentFiles.length === 0) c.push({ score: 60, metric: null, title: 'Write the agent rules file',
@@ -1019,6 +1025,10 @@ function whereToStartSection() {
     deltaText: item.delta > 0 ? `about +${item.delta} points` : (item.target ? `about +${item.target.gain} points once ${item.target.target === 0 ? 'they are all cleared' : `the count is under ${n(item.target.target)}`}` : ''),
     repoName: h.repo ? String(h.repo).split('/').pop() : '',
   });
+  startMoves = top3.map((item) => ({
+    title: unesc(item.title), sub: unesc(item.sub),
+    delta: item.delta || 0, prompt: promptFor(item),
+  }));
   return `<section class="glass pad">
     ${sectionHead('Where to start', head)}
     <div class="ledger">${top3.map((item, i) => `
@@ -1636,6 +1646,7 @@ if (summaryPath) {
     noSystemLikely,
     verdict,
     tiles: bigStats.map((s) => ({ label: s.label, value: s.num, health: s.health })),
+    ...(startMoves.length ? { moves: startMoves } : {}),
     packages: (h.packages ?? []).filter((p) => p.scored && p.metrics)
       .map((p) => ({ dir: p.dir, name: p.name, ...(scorePackage(p.metrics) ?? {}) }))
       .filter((p) => p.score !== undefined)

package/skills/roast-my-design-system/scripts/lib/version.mjs

@@ -1,4 +1,4 @@
 // Single version constant for the engine — imported by diagnose (report
 // footer) and rules (generated-by line). This is the bump spot that used to
 // live as a const inside diagnose/index.mjs.
-export const VERSION = '5.6.0';
+export const VERSION = '5.6.2';

package/skills/roast-my-design-system/scripts/mcp/server.mjs

@@ -13,7 +13,11 @@
  *   node src/mcp/server.mjs <repo-path>
  */
 import { createInterface } from 'node:readline';
-import { resolve } from 'node:path';
+import { resolve, join, dirname } from 'node:path';
+import { readFileSync, mkdtempSync, rmSync } from 'node:fs';
+import { tmpdir } from 'node:os';
+import { spawnSync } from 'node:child_process';
+import { fileURLToPath } from 'node:url';
 import { loadKnowledge, freshKnowledge } from './knowledge.mjs';
 import { getContext, findComponent, findToken, validate, review } from './tools.mjs';
 import { rulesMarkdown } from '../rules/build.mjs';
@@ -69,8 +73,43 @@ const PROMPTS = [
     description: 'Review the current UI changes against the design system',
     text: 'Call roast_review to check the working tree\'s changed files against this repository\'s design system. For each finding, apply the named fix (use roast_find_component and roast_find_token to find the canonical replacement). Rerun roast_review until it reports no measured violations, then summarise what changed.',
   },
+  {
+    name: 'roast-fix',
+    description: 'Fix the top Where-to-start move from a fresh scan; call again for the next one',
+    dynamic: true,
+    arguments: [{ name: 'move', description: 'Which move to fix (1-3); default is the top of the current list', required: false }],
+  },
 ];
 
+// roast-fix runs the real report pipeline (harvest, then diagnose --summary)
+// so the prompt is byte-identical to what the report's copy buttons hold: one
+// composer, two doors. Fresh scan every call, deliberately: fix the top move,
+// ask again, and the next move has risen to the top. The two temp files match
+// the promise the README already makes (a temp JSON and the report).
+function fixMovePrompt(root, moveArg) {
+  const dir = mkdtempSync(join(tmpdir(), 'roast-fix-'));
+  try {
+    const here = dirname(fileURLToPath(import.meta.url));
+    const hPath = join(dir, 'h.json'), sPath = join(dir, 's.json');
+    const run = (script, args) => {
+      const r = spawnSync(process.execPath, [join(here, script), ...args], { encoding: 'utf8', timeout: 120000 });
+      if (r.status !== 0) throw new Error(`${script} exited ${r.status}`);
+    };
+    run('../harvest/index.mjs', [root, '--out', hPath]);
+    run('../diagnose/index.mjs', [hPath, '--out', join(dir, 'report.html'), '--summary', sPath]);
+    const summary = JSON.parse(readFileSync(sPath, 'utf8'));
+    const moves = summary.moves ?? [];
+    if (!moves.length) {
+      return `A fresh scan of this repository found no Where-to-start moves: nothing at the top level is worth a fix prompt right now${summary.score !== null && summary.score !== undefined ? ` (score ${summary.score}/100)` : ''}. Run roast_review on your changed files if you want the working tree checked instead.`;
+    }
+    const idx = Math.min(Math.max(parseInt(moveArg, 10) || 1, 1), moves.length) - 1;
+    const extra = moves.length > 1 ? `\n\n(${moves.length} moves on the current list; this is number ${idx + 1}. Ask for roast-fix again after fixing: the scan refreshes and the next move rises to the top.)` : '';
+    return moves[idx].prompt + extra;
+  } finally {
+    rmSync(dir, { recursive: true, force: true });
+  }
+}
+
 // ---------- resource bodies ----------
 function resourceBody(uri, k) {
   if (uri === 'roast://rules') {
@@ -173,12 +212,13 @@ export function serve(root) {
           return;
         }
         case 'prompts/list':
-          reply(id, { prompts: PROMPTS.map(({ name, description }) => ({ name, description })) });
+          reply(id, { prompts: PROMPTS.map(({ name, description, arguments: args }) => ({ name, description, ...(args ? { arguments: args } : {}) })) });
           return;
         case 'prompts/get': {
           const p = PROMPTS.find((x) => x.name === params?.name);
           if (!p) { fail(id, -32602, `Unknown prompt: ${params?.name}`); return; }
-          reply(id, { description: p.description, messages: [{ role: 'user', content: { type: 'text', text: p.text } }] });
+          const text = p.dynamic ? fixMovePrompt(root, params?.arguments?.move) : p.text;
+          reply(id, { description: p.description, messages: [{ role: 'user', content: { type: 'text', text } }] });
           return;
         }
         default: