@tekyzinc/gsd-t 2.69.10 → 2.69.12

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.69.12] - 2026-04-05
+
+### Fixed (gsd-t-design-audit, gsd-t-design-decompose)
+- **Explicit `get_screenshot` prohibition** — agents were choosing `get_screenshot` (returns pixels) instead of `get_design_context` (returns structured code/tokens) for per-widget Figma extraction, defeating structured comparison. Both commands now have explicit tool guards: "NEVER use `get_screenshot` for Figma design extraction." `get_screenshot` is only acceptable for capturing the built page, not for extracting Figma source data.
+
+## [2.69.11] - 2026-04-05
+
+### Changed (gsd-t-design-audit)
+- **Auto-fix prompt** — after audit completes, if CRITICAL/HIGH deviations found, automatically prompts `/user:gsd-t-quick` with the audit report as source of truth. Re-runs audit after fixes to verify. Up to 2 fix cycles before stopping.
+
 ## [2.69.10] - 2026-04-05
 
 ### Added

package/commands/gsd-t-design-audit.md

@@ -33,13 +33,16 @@ Figma node tree:
 
 ### 1b. Extract each widget node
 
-For EACH widget-level node, call `get_design_context` with the specific node ID. Record:
+For EACH widget-level node, call **`get_design_context`** (NOT `get_screenshot`) with the specific node ID. `get_design_context` returns structured code and component properties that you can extract exact values from. `get_screenshot` returns only visual images — do NOT use it for Figma data extraction.
+
+Record from the `get_design_context` response:
 - **Chart/element type**: what visual pattern does this node contain?
 - **All text content**: every title, subtitle, label, column header, legend item, KPI value, axis label
 - **Layout properties**: alignment, spacing, sizing from the returned code/structure
 - **Colors**: exact hex values for fills, strokes, text
 
 > **⚠ Size guard**: Never call `get_design_context` on the full page frame. Always call on individual widget/card nodes.
+> **⚠ Tool guard**: NEVER use `get_screenshot` to extract Figma design values. It gives you pixels, not properties. Use `get_design_context` — it gives you code, tokens, and structured data.
 
 ### 1c. Classify each element using the taxonomy
 
@@ -182,12 +185,51 @@ Save the full report to `.gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md`
 
 Display the summary to the user inline.
 
+## Step 6: Fix Prompt (auto-triggered if deviations found)
+
+If ANY CRITICAL or HIGH deviations were found, automatically prompt the fix workflow:
+
+```
+───────────────────────────────────────────────────────────────
+
+## ▶ Fix Deviations
+
+**{N} CRITICAL + {N} HIGH deviations found.** Fix them now?
+
+The audit report at `.gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md`
+has the exact Figma values for each deviation.
+
+`/user:gsd-t-quick fix all CRITICAL and HIGH deviations from .gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md — use the Figma values in the report as the source of truth`
+
+───────────────────────────────────────────────────────────────
+```
+
+If ONLY MEDIUM or LOW deviations remain, show:
+
+```
+───────────────────────────────────────────────────────────────
+
+## ▶ Polish (optional)
+
+**{N} MEDIUM + {N} LOW deviations.** These are minor — fix if you want pixel-perfect.
+
+`/user:gsd-t-quick fix MEDIUM and LOW deviations from .gsd-t/design-audit-{page-name}-{YYYY-MM-DD}.md`
+
+───────────────────────────────────────────────────────────────
+```
+
+If ZERO deviations → display "✅ Pixel-perfect. No fixes needed."
+
+After fixes are applied, **re-run the audit automatically** to verify. Loop until:
+- All CRITICAL and HIGH are resolved, OR
+- 2 fix cycles have been attempted (then stop and present remaining deviations to user)
+
 ## Rules
 
-- **You write ZERO code.** Report only. Fixes are a separate step.
+- **You write ZERO code during the audit phase (Steps 1-5).** Report only. Code changes happen in Step 6 via `/user:gsd-t-quick`.
 - **You do NOT "look close" at anything.** Every property gets an exact value from Figma and an exact value from the build. They match or they don't.
 - **You do NOT skip widgets.** Every widget in the Figma AND every widget in the build gets audited.
-- **You call `get_design_context` per widget node.** Do not classify from a page-level screenshot.
+- **You MUST call `get_design_context` per widget node — NOT `get_screenshot`.** `get_design_context` returns structured code, component properties, and design tokens. `get_screenshot` returns only a visual image that you cannot extract exact values from. Using `get_screenshot` for widget extraction defeats the entire purpose of structured comparison — you end up eyeballing instead of measuring. The ONLY acceptable use of `get_screenshot` is for the built page (Step 2) where you need to see what was actually rendered. For Figma source data, ALWAYS use `get_design_context`.
 - **You walk the taxonomy decision tree** for every chart element — document your reasoning.
 - **Minimum 10 rows per widget, 30+ for complex widgets.** Fewer rows means you skipped properties.
 - **If you can't determine a value** (e.g., Figma MCP unavailable for exact px), note "⚠ estimated from screenshot" — but still provide your best measurement.

package/commands/gsd-t-design-decompose.md

@@ -71,6 +71,8 @@ Node tree for page "Analytics":
 
 **Anti-pattern**: Looking at a page screenshot and writing "I see a donut chart" without calling `get_design_context` on that specific node. The MCP returns structured data about the component — use it.
 
+> **⚠ Tool guard**: NEVER use `get_screenshot` for Figma design extraction. `get_screenshot` returns pixels — you cannot extract exact property values, spacing, colors, or text from an image with confidence. `get_design_context` returns structured code, component properties, and design tokens. Always use `get_design_context` per widget node.
+
 ### 1d. Produce the flat inventory table WITH data inventory
 
 | # | Element on Design | Figma Node ID | Appears On Pages | Text Content Extracted | Visual Variant |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.69.10",
+  "version": "2.69.12",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 54 slash commands with headless CI/CD mode, graph-powered code analysis, real-time agent dashboard, execution intelligence, task telemetry, doc-ripple enforcement, backlog management, impact analysis, test sync, milestone archival, and PRD generation",
   "author": "Tekyz, Inc.",
   "license": "MIT",