@bendyline/gilde 0.1.38 → 0.1.39

package/data/craftbook-templates/de/design-review/versions/1.0.2/craftbook.json

@@ -0,0 +1,153 @@
+{
+  "id": "design-review",
+  "name": "UX & Visual Design Review",
+  "description": "Critique a UI's user experience and visual design and produce a prioritized design-review report. First scopes the screens and flows and locks a heuristic checklist (visual hierarchy, spacing rhythm and alignment, typographic scale, color and contrast, consistency, affordance and feedback, empty/loading/error states, and the primary task's friction), then reviews each screen against those heuristics with a designer's eye for both polish and usability, then writes a findings report rating each issue by impact with a concrete, specific design fix. Use this for a design review, UX critique, visual QA, design feedback, a heuristic evaluation, or 'does this look and feel right' — it gives actionable, specific design fixes (exact spacing, color, hierarchy changes) rather than 'make it pop'.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Scope the design review (reviewer) — enumerate screens + lock UX/visual heuristics → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Review the design (visual-designer) — critique each screen against the heuristics → gated on artifact `{{workPath}}/review.md` (markdown-notes)\n3. Write the design report (reviewer) — prioritized findings with concrete fixes → gated on artifact `{{workPath}}/design-review.md` (markdown-report)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "design review",
+    "ux critique",
+    "review the design",
+    "give design feedback",
+    "visual QA",
+    "does this look right"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the design review",
+      "description": "enumerate screens + lock UX/visual heuristics",
+      "prompt": "Step 1: Identify the screens/components and the primary user task the design serves. Step 2: Write a design acceptance-criteria checklist covering UX and visual heuristics: clear visual hierarchy (the most important element reads first), consistent spacing rhythm and alignment to a grid, a coherent typographic scale (limited sizes/weights), sufficient color contrast and a disciplined palette, consistency of components/patterns across screens, obvious affordances and immediate feedback on actions, presence and quality of empty/loading/error/success states, and low friction on the primary task (minimal steps, no dead-ends). Step 3: For each heuristic state the pass condition for THIS UI (e.g. 'spacing uses a 4/8px scale, no arbitrary gaps', 'one accent color used only for primary actions'). Step 4: Note how you will evaluate (screenshots via the existing automation if available, else reading the markup/CSS and reasoning about the rendered result). Write the screen list + heuristic checklist to `write_task_note` AND `{{workPath}}/scope.md`. No critique yet.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "reviewer",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "review"
+    },
+    {
+      "id": "review",
+      "name": "Review the design",
+      "description": "critique each screen against the heuristics",
+      "prompt": "Step 1: View each screen (capture/screenshot via the existing Playwright specs or browser if available; otherwise render the CSS in your head from the source and reason precisely). Step 2: For EACH heuristic, assess the screen and note specific issues: where the hierarchy is flat or competing, where spacing/alignment is inconsistent (cite the elements and the px values), where type or color breaks the system, where an affordance is missing or feedback is absent, and which states are unhandled. Step 3: For every finding capture: the screen/element, the heuristic violated, the user/visual impact, severity (high = hurts the task or looks broken / medium / low polish), and a CONCRETE fix with values ('increase the card padding from 8px to 16px', 'demote the secondary button to a text link', 'add a skeleton loading state'). Step 4: Note what works well too — a good review reinforces the strong patterns. Good looks like: specific, valued-anchored fixes, never 'make it cleaner'. Stage findings to `write_task_note`. Do not write the report yet.\n\nThe deliverable `{{workPath}}/review.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "visual-designer",
+      "advanceWhen": {
+        "file": "{{workPath}}/review.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/review.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/review.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "review",
+        "maxAttempts": 3
+      },
+      "next": "report"
+    },
+    {
+      "id": "report",
+      "name": "Write the design report",
+      "description": "prioritized findings with concrete fixes",
+      "prompt": "Step 1: Open `{{workPath}}/design-review.md` and write a 2-3 sentence overall impression: what works, and the single biggest opportunity. Step 2: Add a '## High impact' section (issues that hurt usability or look broken), '## Medium', and '## Polish' — each finding as `screen/element — problem — concrete fix (with values)`. Step 3: Add a '## What's working' section reinforcing the strong patterns to keep. Step 4: If screenshots were captured, reference them per finding. Every fix must be specific and actionable (values, not adjectives). On a loop-back, fix only the named gaps without dropping valid findings. `write_task_note` the report path and the count of findings by impact.\n\nThe deliverable `{{workPath}}/design-review.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "reviewer",
+      "advanceWhen": {
+        "file": "{{workPath}}/design-review.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/design-review.md",
+            "bytes": 1500,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/design-review.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "report",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Open `{{workPath}}/design-review.md` and grade it against the scope heuristic checklist. Check EACH criterion and write PASS/FAIL with a one-line reason: (1) every heuristic in the checklist was assessed; (2) findings are prioritized by impact (high/medium/polish); (3) each finding names the screen/element and gives a concrete fix with values, not adjectives; (4) empty/loading/error states were evaluated; (5) the primary task's friction was assessed; (6) a What's-working section exists; (7) no vague 'make it pop' filler. If any criterion fails, name the exact gap and loop back.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/design-review.md` with `read_artifact`, not `read_file`.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"report\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "{{workPath}}/design-review.md",
+          "artifact": true
+        }
+      ],
+      "next": "report"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/de/design-review/versions/1.0.2/test.json

@@ -0,0 +1,121 @@
+{
+  "schemaVersion": 1,
+  "title": "Design review from seeded dashboard markup",
+  "objective": "Measure whether the design-review craftbook scopes heuristics and produces prioritized, concrete UX/visual findings.",
+  "tags": [
+    "media"
+  ],
+  "prompt": "In the `Design Review Eval` project, read `source/dashboard.html` and write `tasks/eval/design-review.md`. Review the Orders dashboard for visual hierarchy, spacing/alignment, type scale, contrast, consistency, affordance/feedback, empty/loading/error/success states, and primary-task friction. Every finding needs screen/element, impact, severity, and a concrete fix with values.",
+  "setup": {
+    "projectName": "Design Review Eval",
+    "about": "Self-contained eval project for design-review. A compact dashboard HTML fixture is in workspace/source/dashboard.html.",
+    "missionObjectives": "Produce a prioritized design review with specific, value-anchored fixes and no vague filler.",
+    "files": [
+      {
+        "path": "source/dashboard.html",
+        "content": "<!doctype html><html><head><style>body{font-family:Arial;color:#777;background:#fff}.toolbar{display:flex;gap:3px}.primary,.secondary{background:#777;color:#777;padding:4px}.card{margin:13px;padding:6px;border:1px solid #eee}.empty{display:none}</style></head><body><h1>Orders</h1><div class=\"toolbar\"><button class=\"primary\">Export</button><button class=\"secondary\">Filter</button></div><section class=\"card\"><h2>Open returns</h2><p>97 waiting for review</p></section><section class=\"card\"><h2>Queue</h2><table><tr><td>Acme</td><td>Needs photo</td></tr></table></section></body></html>\n"
+      }
+    ],
+    "worker": {
+      "name": "Quinten",
+      "role": "UX Reviewer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "workspace/design-review.md prioritizes concrete design findings against the seeded dashboard markup with values and state coverage.",
+    "deliverables": [
+      {
+        "path": "tasks/eval/design-review.md",
+        "kind": "markdown-report",
+        "minBytes": 2200,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/design-review.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/design-review.md",
+            "pattern": "High impact|Medium|Polish|What.?s working",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/design-review.md",
+            "pattern": "contrast|spacing|alignment|typographic|hierarchy",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/design-review.md",
+            "pattern": "empty|loading|error|success|feedback",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/design-review.md",
+            "pattern": "button|toolbar|card|Orders|Open returns",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/design-review.md",
+            "pattern": "px|4/8|16px|specific|concrete",
+            "flags": "i"
+          },
+          {
+            "kind": "notContains",
+            "file": "tasks/eval/design-review.md",
+            "pattern": "make it pop|cleaner|nice|modernize it",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/design-review.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "completeness",
+        "description": "The manifest covers sources, outputs, and processing steps end to end."
+      },
+      {
+        "name": "grounding",
+        "description": "Only seeded media fixtures are referenced, with faithful metadata."
+      },
+      {
+        "name": "accessibility",
+        "description": "Alt text, captions, or transcripts are planned wherever the class requires."
+      },
+      {
+        "name": "precision",
+        "description": "Timestamps, crops, and cues are specific enough to execute."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "heuristic checklist",
+    "specific fixes",
+    "prioritized findings"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "design-review-media-fixtures",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local media index replacing real audio, video, image generation, and external media metadata services."
+      }
+    ]
+  }
+}