@bendyline/gilde 0.1.39 → 0.1.41

package/data/craftbook-templates/pe/perf-optimization/versions/2.0.0/test.json

@@ -0,0 +1,236 @@
+{
+  "schemaVersion": 1,
+  "title": "Measured near-linear fix for a quadratic hot path",
+  "objective": "The craftbook drives a measured optimization of a seeded O(n^2) duplicate finder: baseline numbers recorded with their method, one bottleneck fixed at the real site, the same measurement re-run to prove the gain, and an enforced review — verified mechanically via a deterministic instrumented op-count budget, reference-equal results, and a green-suite run.",
+  "tags": [
+    "code",
+    "performance",
+    "tactical-fleet"
+  ],
+  "prompt": "Use the Targeted Performance Fix craftbook for this: support says importing a 200-row sheet crawls, and profiling points at findDuplicates - a 200-item list burns about 40,000 comparisons. The brief is in source/perf-brief.md. Get findDuplicates near-linear without changing its results.",
+  "setup": {
+    "projectName": "Sheet Importer",
+    "about": "A tiny sheet-import module with an instrumented duplicate finder. Tests run with `npm run test` (node --test).",
+    "files": [
+      {
+        "path": "package.json",
+        "content": "{\n  \"name\": \"sheet-importer\",\n  \"private\": true,\n  \"version\": \"1.0.0\",\n  \"type\": \"module\",\n  \"scripts\": {\n    \"test\": \"node --test\"\n  }\n}\n"
+      },
+      {
+        "path": "src/instrument.js",
+        "content": "let comparisons = 0;\n\nexport function countComparison() {\n  comparisons += 1;\n}\n\nexport function comparisonCount() {\n  return comparisons;\n}\n\nexport function resetComparisons() {\n  comparisons = 0;\n}\n"
+      },
+      {
+        "path": "src/find-duplicates.js",
+        "content": "import { countComparison } from './instrument.js';\n\nexport function findDuplicates(items) {\n  const duplicates = [];\n  for (let i = 0; i < items.length; i += 1) {\n    let count = 0;\n    for (let j = 0; j < items.length; j += 1) {\n      countComparison();\n      if (items[j] === items[i]) count += 1;\n    }\n    if (count > 1 && !duplicates.includes(items[i])) duplicates.push(items[i]);\n  }\n  return duplicates;\n}\n"
+      },
+      {
+        "path": "tests/duplicates.test.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { test } from 'node:test';\nimport { findDuplicates } from '../src/find-duplicates.js';\n\ntest('reports each duplicate once, in first-appearance order', () => {\n  assert.deepEqual(findDuplicates(['a', 'b', 'a', 'c', 'b']), ['a', 'b']);\n});\n\ntest('returns empty for unique lists', () => {\n  assert.deepEqual(findDuplicates(['x', 'y', 'z']), []);\n});\n\ntest('order pins to first appearance, not second occurrence', () => {\n  assert.deepEqual(findDuplicates(['a', 'b', 'b', 'a']), ['a', 'b']);\n});\n"
+      },
+      {
+        "path": "source/perf-brief.md",
+        "content": "# Performance brief\n\nSupport reports that importing a 200-row sheet crawls. Profiling points at `findDuplicates` in src/find-duplicates.js: for a 200-item list it performs about 40,000 instrumented comparisons (200 x 200 full rescans). The counter lives in src/instrument.js - `comparisonCount()` reads it, `resetComparisons()` clears it.\n\nTarget: get `findDuplicates` near-linear - well under 2,000 instrumented comparisons for a 200-item list - WITHOUT changing its results. Each duplicated value is reported once, in order of FIRST appearance.\n\nRules:\n\n- src/instrument.js is measurement infrastructure; leave it exactly as it is.\n- Keep the measurement honest: keep calling `countComparison()` for every equality comparison the new implementation still performs. Deleting instrumentation instead of deleting work is measurement theater.\n- Measure with a repeatable command: a small script that builds a 200-item list, calls `findDuplicates`, and prints `comparisonCount()`.\n"
+      },
+      {
+        "path": "tests/verify-perf.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { execFileSync } from 'node:child_process';\nimport { findDuplicates } from '../src/find-duplicates.js';\nimport { comparisonCount, resetComparisons } from '../src/instrument.js';\n\n// Independent reference: each duplicated value once, first-appearance order.\nfunction referenceDuplicates(items) {\n  const counts = new Map();\n  for (const item of items) counts.set(item, (counts.get(item) ?? 0) + 1);\n  const out = [];\n  const added = new Set();\n  for (const item of items) {\n    if ((counts.get(item) ?? 0) > 1 && !added.has(item)) {\n      added.add(item);\n      out.push(item);\n    }\n  }\n  return out;\n}\n\n// 1) Results identical to reference on small pinned cases.\nassert.deepEqual(findDuplicates(['a', 'b', 'a', 'c', 'b']), ['a', 'b']);\nassert.deepEqual(findDuplicates([]), []);\nassert.deepEqual(findDuplicates(['a', 'b', 'b', 'a']), ['a', 'b']);\n\n// 2) Deterministic 200-item workload: results equal reference AND the\n// instrumented op-count is under the stated budget (seeded code: 40000).\nconst items = [];\nfor (let i = 0; i < 200; i += 1) items.push('v' + ((i * 7) % 149));\nresetComparisons();\nconst result = findDuplicates(items);\nassert.deepEqual(result, referenceDuplicates(items), 'results changed - speed that changes answers is a bug');\nconsole.log('PERF_OPTIMIZATION_ORACLE results ok');\nconst ops = comparisonCount();\nassert.ok(\n  ops <= 2000,\n  'findDuplicates on 200 items performed ' + ops + ' instrumented comparisons - the budget is 2000 and the seeded code did 40000',\n);\nconsole.log('PERF_OPTIMIZATION_ORACLE ops ' + ops + ' within budget');\n\n// 3) The whole suite is green on the optimized tree (real run).\nfunction runSuite(cwd) {\n  try {\n    execFileSync(process.execPath, ['--test'], { cwd, stdio: 'pipe', timeout: 30000 });\n    return 0;\n  } catch (err) {\n    return typeof err.status === 'number' ? err.status : 1;\n  }\n}\nassert.equal(runSuite(process.cwd()), 0, 'the suite must be green on the optimized tree');\nconsole.log('PERF_OPTIMIZATION_ORACLE suite green');\nconsole.log('PERF_OPTIMIZATION_ORACLE done');\n",
+        "surface": "harness"
+      }
+    ],
+    "craftbookParams": {
+      "workPath": "tasks/eval",
+      "scope": "findDuplicates in src/find-duplicates.js does about 40,000 instrumented comparisons for a 200-item list; get it near-linear (well under 2,000 comparisons) without changing its results. See source/perf-brief.md."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The quadratic rescan is gone, the instrumented op-count for 200 items is under budget, results are identical to the reference on a deterministic workload, the suite is green on a real run, and every fleet artifact exists with honest numbers and citations.",
+    "deliverables": [
+      {
+        "path": "tasks/eval/baseline.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/baseline.md",
+            "pattern": "^##\\s+Current behavior[\\s\\S]*^##\\s+Measurements[\\s\\S]*^##\\s+Guardrail",
+            "flags": "im",
+            "label": "baseline sections in order"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/baseline.md",
+            "pattern": "^##\\s+Measurements[\\s\\S]*\\d",
+            "flags": "im",
+            "label": "baseline numbers recorded"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/baseline.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/plan.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/plan.md",
+            "pattern": "^##\\s+Target[\\s\\S]*^##\\s+Stages[\\s\\S]*^##\\s+Acceptance criteria",
+            "flags": "im",
+            "label": "plan sections in order"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/plan.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/change-notes.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/change-notes.md",
+            "pattern": "^##\\s+Stages executed[\\s\\S]*^##\\s+Files touched[\\s\\S]*^##\\s+Deviations from plan",
+            "flags": "im",
+            "label": "change-notes sections in order"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/change-notes.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/verification.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/verification.md",
+            "pattern": "^##\\s+Before\\s*/\\s*after[\\s\\S]*^##\\s+Suite[\\s\\S]*^##\\s+Result",
+            "flags": "im",
+            "label": "verification sections in order"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/verification.md",
+            "pattern": "^##\\s+Before\\s*/\\s*after[\\s\\S]*\\d",
+            "flags": "im",
+            "label": "both numbers quoted"
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/review.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/review.md",
+            "pattern": "Verdict:\\s*(?:PASS|REVISE)",
+            "flags": "i",
+            "label": "explicit reviewer verdict"
+          }
+        ]
+      }
+    ],
+    "checks": [
+      {
+        "kind": "notContains",
+        "file": "src/find-duplicates.js",
+        "pattern": "for\\s*\\(let j = 0; j < items\\.length",
+        "label": "the seeded inner full-list rescan is gone"
+      },
+      {
+        "kind": "sourceParses",
+        "file": "src/find-duplicates.js"
+      },
+      {
+        "kind": "nodeScriptPasses",
+        "script": "tests/verify-perf.mjs",
+        "timeoutMs": 60000,
+        "requiredOutput": [
+          {
+            "pattern": "PERF_OPTIMIZATION_ORACLE results ok",
+            "label": "results identical to the reference"
+          },
+          {
+            "pattern": "PERF_OPTIMIZATION_ORACLE ops \\d+ within budget",
+            "label": "instrumented op-count under the stated budget"
+          },
+          {
+            "pattern": "PERF_OPTIMIZATION_ORACLE suite green",
+            "label": "suite green on the optimized tree"
+          }
+        ]
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 120,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\bDONE\\b[\\s\\S]*(npm\\s+run\\s+test|node\\s+--test)",
+          "flags": "i",
+          "label": "DONE note names the real test command"
+        }
+      ]
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "source/perf-brief.md",
+      "package.json",
+      "src/instrument.js"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/verification.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "Measurement honesty",
+        "description": "Baseline numbers were gathered by a stated, repeatable method before the change, and verification re-ran the identical method and quoted both figures side by side - no adjectives standing in for numbers, no swapped workload."
+      },
+      {
+        "name": "Bottleneck focus",
+        "description": "One bottleneck was named with its mechanism and fixed at the real site by that mechanism - not a synthetic proxy, a weakened measurement, or scattered micro-tweaks."
+      },
+      {
+        "name": "Correctness under speed",
+        "description": "Results stayed identical on the same inputs, the suite stayed green between stages with real receipts, and residual risk or unverified claims are labeled honestly."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "numbers with their method",
+    "same-method re-measurement",
+    "enforced review loop"
+  ]
+}

package/data/craftbook-templates/pe/pest-diagnosis/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "pest-diagnosis",
   "role": "general",
+  "category": "personal",
   "name": "Pest & Problem Diagnosis",
   "description": "Turn 'something is wrong with the tomatoes' into a ranked differential: the likely culprits with the evidence for each, the gentlest treatment first, what to watch to confirm the diagnosis, and when to call in a professional — a garden clinic visit without the guesswork. Locks the diagnostic criteria FIRST, then builds the differential from the symptom notes and the plantings, then writes the treatment and monitoring plan. Use for garden pest problems, plant disease diagnosis, 'what is eating my plants', and sick-plant triage.",
   "tags": [

package/data/craftbook-templates/ph/photo-cull/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "photo-cull",
   "role": "general",
+  "category": "media",
   "name": "Photo Cull & Rank",
   "description": "Rank and cull a set of photos by objective quality — sharpness/focus, exposure, composition, eyes-open/expression for people, and duplicate-of-a-better-shot — to surface the keepers and justify the rejects. Lock the scoring CRITERIA and weights FIRST (what 'good' means for this set: a portrait shoot weights expression, a landscape weights sharpness and horizon) because an unstated rubric makes the cull arbitrary; then score every photo and produce a ranked report with keep/reject and reasons. Covers photo culling, image quality ranking, best-shot selection, photo curation, and burst/best-of selection.",
   "tags": [

package/data/craftbook-templates/ph/physics-toy/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "physics-toy",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Interactive Physics Toy",
   "description": "Build a single-file interactive canvas physics or particle toy such as a bouncing-ball sandbox, gravity wells, springs, cloth, fluid, or a boids flock that the user can poke with the mouse. Defines the simulation model — forces, integration, collisions, and the interaction verbs — first, then implements a stable per-frame integrator. Physics toys feel magical only when the numerics are stable and the mouse interaction is responsive, so the concept phase pins the forces and integration scheme before any drawing, the ordering that keeps a small model from shipping a jittery or exploding sim.",
   "tags": [

package/data/craftbook-templates/pi/pitch-deck/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "pitch-deck",
   "role": "general",
+  "category": "marketing",
   "name": "Investor Pitch Deck",
   "description": "Build a fundraising or sales pitch deck that tells a tight investor-grade story: problem, solution, market size, product, business model, traction, go-to-market, competition, team, and the ask. Locks the NARRATIVE arc and per-slide message FIRST (a deck lives or dies on story order, not visuals), then designs a single consistent slide system, then builds a navigable HTML deck — one idea per slide, big claim plus one supporting proof, ending on a crisp ask and use-of-funds. Use for seed/Series-A raises, sales decks, demo days, and investor updates.",
   "tags": [

package/data/craftbook-templates/pl/plan/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "plan",
   "role": "general",
+  "category": "practice",
   "name": "Plan",
   "description": "Author a PLAN for a piece of work as a reviewable draft task: a strong 'about', a set of outcomes (what should be created or updated at success), an ordered series of build steps each gated on a concrete static deliverable, and a final verification step that checks the outcomes were kept. The user reviews the draft and activates it to run. Invoke via the start_plan tool. Use for 'plan this', 'make a plan', '/plan'.",
   "tags": [

package/data/craftbook-templates/pl/playtest-report/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "playtest-report",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Playtest Report",
   "description": "Playtest like it matters: a structured pass over the mechanics, the edge inputs, and the score loop, every finding written with its repro steps — a ranked fix list, not vibes. Locks the test plan FIRST — what to try and what correct looks like — then plays through it taking notes, then writes the findings with a ranked issue table. Use for playtesting a game before sharing it, 'is the game actually solid', bug hunts on an arcade page, pre-release game QA, and turning playtest feelings into a fix list.",
   "tags": [

package/data/craftbook-templates/po/podcast-chaptering/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "podcast-chaptering",
   "role": "general",
+  "category": "media",
   "name": "Podcast Chapters & Show Notes",
   "description": "Turn a podcast episode into navigable chapter markers plus publish-ready show notes — timestamped chapter titles, an episode summary, key takeaways, and linked mentions. Scopes the chapter format and show-notes structure FIRST, analyzes the transcript to find real topic boundaries with timestamps, then writes the listener-facing notes in the show's voice. Separating boundary-detection (analysis) from the write-up (copy) is what yields chapters that land on actual topic shifts and notes that read like a human wrote them.",
   "tags": [

package/data/craftbook-templates/po/portfolio-site/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "portfolio-site",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Portfolio Site",
   "description": "Build a personal or professional portfolio site that showcases projects, an about/bio, and contact links in a single polished page. Locks the content inventory — which projects, what bio, which links — first, then a clean gallery-style visual design, then builds responsive HTML with a project grid and real CSS. Scoping the content before designing prevents a small model from inventing fake projects or building a layout the real content does not fit; the portfolio's job is to present a finite set of real work cleanly.",
   "tags": [

package/data/craftbook-templates/po/powerpoint-deck/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "powerpoint-deck",
   "role": "general",
+  "category": "design",
   "name": "PowerPoint from Content",
   "description": "Turn source content into a real editable PowerPoint file (.pptx), not an HTML deck. Locks the narrative and one message per slide, writes ordinary Markdown with one H1 per slide, then uses DocBlocks for theme-aware conversion, visual preview, and artifact saving. No Developer is needed merely to export the deck.",
   "tags": [

package/data/craftbook-templates/pr/pr-security-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "pr-security-review",
   "role": "maintenance-review",
+  "category": "code-review",
   "name": "Security Review of a Diff",
   "description": "Perform a focused security review of a code change or diff and produce a vulnerability report mapped to a threat checklist. First scopes the change's attack surface and locks a security checklist (injection, authn/authz, secrets, deserialization, SSRF, crypto misuse, input validation, dependency risk), then audits the diff against each class while tracing tainted data from untrusted sources to dangerous sinks, then writes a findings report rating each issue by severity and likelihood with a concrete remediation. Use this for a security review, secure code review, vulnerability assessment of a diff, an AppSec pass, or checking a change for injection/auth/secret-leak risks before merge — it surfaces exploitable flaws tied to specific lines rather than generic security platitudes.",
   "tags": [

package/data/craftbook-templates/pr/practice-exam/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "practice-exam",
   "role": "general",
+  "category": "personal",
   "name": "Practice Exam",
   "description": "Take the exam before the exam: a timed, self-scoring practice paper blueprinted from the deck — weighted toward what the review record says is weak — with an answer key that explains, not just grades. Locks the blueprint FIRST — topic coverage, weak-spot weighting from the deck's boxes and miss counts, timing, honest scoring — then builds the interactive exam page, then writes the key. Use for practice exams, mock tests, 'test me before the test', timed practice papers, and exam-week dress rehearsals.",
   "tags": [

package/data/craftbook-templates/pr/practice-session/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "practice-session",
   "role": "general",
+  "category": "personal",
   "name": "Log the Practice Session",
   "description": "Close out today's practice properly: log what was actually worked with honest minutes and tempo marks, and set up tomorrow's session so the next sit-down starts with intent instead of noodling. Locks the honest picture of the session FIRST, then logs it into the practice record, then writes tomorrow's targeted plan. Use for logging a practice session, ending today's practice, planning tomorrow's practice, and 'log my practice'.",
   "tags": [

package/data/craftbook-templates/pr/pre-departure-countdown/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "pre-departure-countdown",
   "role": "general",
+  "category": "personal",
   "name": "Pre-Departure Countdown",
   "description": "Audit a trip's readiness in the final stretch before departure: verify documents and bookings, close the packing gaps against the packing roster, sweep home-prep tasks, and produce a day-by-day countdown checklist to the departure date — so the last week runs on a list, not on 3am worry. Locks the audit areas and the days remaining FIRST, then audits each area against the trip record, then writes the countdown. Use for pre-trip checks, departure prep, 'are we ready for the trip', and travel countdown checklists.",
   "tags": [

package/data/craftbook-templates/pr/press-release/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "press-release",
   "role": "general",
+  "category": "marketing",
   "name": "Press Release",
   "description": "Write a professional, AP-style press release ready to send to journalists: it first locks the news angle, the five W's, the approved quote(s), and the boilerplate, then drafts the release in the standard format — dateline, inverted-pyramid lede, supporting body, quotes, boilerplate, and media contact — then a review pass enforces newsworthiness, factual accuracy, and house style. Covers press release, news announcement, PR writing, media release, product launch announcement, and corporate communications. The scope-first ordering is essential: a small model that pins the angle and quotes before drafting avoids the soft, promotional release that buries the news and no editor will run.",
   "tags": [

package/data/craftbook-templates/pr/price-tracker/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "price-tracker",
   "role": "general",
+  "category": "research",
   "name": "Track Prices Over Time",
   "description": "Build a price tracker that records the price of one or more products/SKUs each time it runs, appending a timestamped history so you can see trends, drops, and the lowest price seen. Scopes the SKUs, the price-extraction rule, and the history-file schema FIRST, then builds the fetch-and-append routine that is idempotent per day and computes drop-from-previous and all-time-low. Schema-before-build keeps the history a clean append-only time series instead of a pile of inconsistent snapshots — the foundation any later chart or alert reads from.",
   "tags": [

package/data/craftbook-templates/pr/pricing-page/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "pricing-page",
   "role": "project-starter",
+  "category": "marketing",
   "name": "Pricing Page",
   "description": "Build a single pricing or plan-comparison page with tiered plan cards, a feature comparison, a highlighted recommended plan, and optionally a monthly/annual toggle that updates prices. Scopes the plans, features, and pricing model first, designs a comparison layout that makes the recommended tier obvious, writes the plan copy, then builds responsive HTML with a working billing toggle. Pricing pages fail when the toggle does not update prices or the tiers are not genuinely comparable, so the offer-scope phase locks the exact plans and feature matrix before any markup.",
   "tags": [

package/data/craftbook-templates/pr/product-descriptions/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "product-descriptions",
   "role": "general",
+  "category": "marketing",
   "name": "Bulk Product Descriptions",
   "description": "Generate consistent, on-brand product descriptions in bulk from a list of products and their attributes: it first locks the brand voice, the field schema (title, short blurb, long description, bullet features, SEO meta), and a worked exemplar, then drafts every product to that exact template so the whole catalog reads as one voice. Covers ecommerce product copy, catalog descriptions, Shopify/Amazon listings, bulk SKU copywriting, and product detail pages. Locking the voice and one exemplar before the batch is the key move: it stops a small model from drifting in tone and structure across items, which is the classic failure of bulk copy.",
   "tags": [

package/data/craftbook-templates/pr/proposal-sow/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "proposal-sow",
   "role": "general",
+  "category": "business",
   "name": "Proposal / Statement of Work",
   "description": "Draft a client proposal or statement of work that wins the deal and prevents scope creep — covering objectives, scope, deliverables, timeline/milestones, pricing, assumptions, and acceptance criteria. Scopes the engagement and the in-scope/out-of-scope boundary FIRST (the boundary is what protects both sides), writes persuasive yet precise proposal copy, then formats it into a clean client-ready document with a structured deliverables-and-pricing table. Use for freelance/agency bids, consulting SOWs, and project proposals.",
   "tags": [

package/data/craftbook-templates/pu/pull-request-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "pull-request-review",
   "role": "maintenance-review",
+  "category": "code-review",
   "name": "Pull Request Review",
   "description": "Staff-engineer-style PR review over a complete local PR corpus. Defaults to the open pull request for the project's checked-out branch when one exists, accepts an explicit PR number from any branch, reviews changed files in bounded batches with mechanical coverage accounting, verifies cross-file claims against the checkout, and produces a structured local verdict. Requires a GitHub-connected project.",
   "tags": [

package/data/craftbook-templates/pu/puzzle-pack-layout/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "puzzle-pack-layout",
   "role": "general",
+  "category": "design",
   "name": "Lay Out the Puzzle Pack",
   "description": "Bind the month's puzzles into one print-ready pack: a cover, a page per puzzle, and the solutions gathered in the back where they belong — the thing that lands on the kitchen table and disappears into pencil marks. Locks the shelf inventory and the page rules FIRST, then lays out the pack, then proofs that every puzzle made it in and no solution leaks next to its puzzle. Use for laying out the puzzle pack, binding the month's puzzles, a printable puzzle booklet, and 'put the puzzles into one pack'.",
   "tags": [

package/data/craftbook-templates/pw/pwa-offline/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "pwa-offline",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Installable Offline PWA",
   "description": "Build an installable Progressive Web App that works offline — an HTML app shell, a web app manifest, and a service worker that caches the shell so it loads with no network. Scopes the app's one job and the offline strategy first, designs the app shell, then implements the manifest, registration, and a cache-first service worker. PWAs fail at installability and the service-worker caching contract, so the scope phase locks the cached asset list and the offline behavior before coding, keeping a small model from shipping a manifest that fails the install criteria or a service worker that never caches.",
   "tags": [

package/data/craftbook-templates/qa/qa/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "qa",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "QA",
   "description": "Live UI QA pass with a real browser. Navigates the target, interacts with the golden-path flow, captures findings, fixes atomically, re-tests.",
   "tags": [
@@ -14,6 +15,8 @@
   },
   "logo": "logo.webp",
   "license": "MIT",
-  "yankedVersions": [],
+  "yankedVersions": [
+    "1.0.0"
+  ],
   "workflow": "qa"
 }

package/data/craftbook-templates/qu/quarterly-summary/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "quarterly-summary",
   "role": "general",
+  "category": "business",
   "name": "Quarterly Shoebox Summary",
   "description": "Close the quarter the way your accountant wishes everyone did: totals by category computed from the ledger entries themselves, the missing-documentation list naming each entry that lacks its paperwork, and the estimated-payment reminder in plain words. Locks the target quarter and the checks FIRST, then reconciles the numbers, then writes the summary — twenty minutes, four times a year, instead of an April archaeology dig. Use for quarterly tax summaries, 'how did the quarter shake out', estimated payment prep, and shoebox quarter closes.",
   "tags": [

package/data/craftbook-templates/re/reading-list/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "reading-list",
   "role": "general",
+  "category": "research",
   "name": "Curated Annotated Reading List",
   "description": "Curate an annotated reading list on a topic for a defined reader: a planner sets the reader, their goal, and the selection and ordering criteria, then a researcher curates and annotates each pick with why it matters, what it covers, and a suggested reading order. The ordering matters because a list assembled without a reader and a goal becomes a random link dump, and one without annotations forces the reader to guess what to read first; fixing who it is for and what 'good for this reader' means up front turns it into a guided learning path. Use this for curated reading lists, a syllabus or learning path, 'what should I read to learn X', resource roundups, and annotated bibliographies of recommended materials.",
   "tags": [

package/data/craftbook-templates/re/receipt-intake/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "receipt-intake",
   "role": "general",
+  "category": "business",
   "name": "Receipt Intake",
   "description": "Empty the shoebox inbox properly: every waiting receipt becomes a dated, categorized ledger entry that names its source file, likely duplicates get flagged instead of double-counted, and the genuinely ambiguous ones become owner questions instead of guesses. Locks the intake rules FIRST, then works the inbox receipt by receipt, then reports the totals and the question list — the year-round habit that makes April an afternoon. Use for receipt intake, emptying the receipt inbox, 'get these into the ledger', and monthly shoebox catch-ups.",
   "tags": [

package/data/craftbook-templates/re/receipt-ocr-ledger/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "receipt-ocr-ledger",
   "role": "general",
+  "category": "business",
   "name": "Receipts to Expense Ledger",
   "description": "Turn a folder of receipt photos/PDFs into a clean expense ledger: OCR each receipt, extract vendor, date, line items, tax, and total, assign an expense category, and reconcile that each extracted total matches its line items. Locks the per-receipt field schema, the category set, and the math/reconciliation rules FIRST, then OCRs and extracts each receipt into rows, then verifies every receipt was processed, totals reconcile, currencies/dates are normalized, and low-confidence reads are flagged for review. Defining the schema and the total-equals-line-items check before extraction is what keeps an expense ledger trustworthy for reimbursement or tax.",
   "tags": [

package/data/craftbook-templates/re/reception-report/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "reception-report",
   "role": "maintenance-review",
+  "category": "marketing",
   "name": "Reception Report",
   "description": "The weekly reception review for your social posting. Reconciles published posts with their live feed records (stamping the corpus reference onto any post that lost track of its live copy), builds a per-post engagement ledger of likes, reposts, and replies, compares each post against your account's recent baseline, and reports what landed, what did not, and what to post next — closing with a single one-click action that seeds the next draft from the strongest theme. Covers social media analytics, post performance review, engagement reporting, cadence tracking, Bluesky and X and Instagram metrics, and honest small-sample reading of your feeds. No connected feed? It still writes the ledger from what the workspace knows and names the gap.",
   "tags": [

package/data/craftbook-templates/re/recipe-capture/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "recipe-capture",
   "role": "general",
+  "category": "personal",
   "name": "Capture a Recipe Card",
   "description": "Rescue a handwritten recipe card without sanding off its soul: transcribe the original faithfully — spelling quirks, margin notes, and all — standardize quantities in a separate block alongside (never instead of) the original wording, and pin the provenance note: whose card, whose kitchen, what they always changed. Locks the capture rules FIRST, then captures each card into the book, then logs what needs a test-cook and what to ask the family. Use for capturing recipe cards, 'get oma's cards into the book', preserving family recipes, and recipe transcription.",
   "tags": [

package/data/craftbook-templates/re/record-a-relative/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "record-a-relative",
   "role": "general",
+  "category": "personal",
   "name": "Record a Relative",
   "description": "Bank an elder's interview while the telling is fresh: file the transcript, pull the people, places, and dates into the family record with their source, and write the follow-up questions — because the questions you didn't ask are the ones that vanish. Locks the extraction rules FIRST (every fact carries its quote, uncertain stays uncertain), then files the transcript, then updates the tree and surfaces the conflicts. Use for filing a family interview, recording a relative's stories, pulling facts into the tree, and 'we interviewed grandma'.",
   "tags": [

package/data/craftbook-templates/re/recurring-invoice-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "recurring-invoice-run",
   "role": "general",
+  "category": "business",
   "name": "Generate and Send Recurring Invoices",
   "description": "Run a recurring billing batch: for each active client/subscription due this period, generate a correctly-numbered, line-itemed invoice with taxes and totals, render it, and send it — once, idempotently, with a sent-log. Locks the invoice template, the numbering scheme, the tax/total math, and the due/idempotency rules FIRST, then builds the generate-render-send batch keyed to a billing-run log, then verifies every due client was invoiced exactly once, totals are arithmetically correct, and numbers are sequential with no gaps or dupes. Locking numbering and math up front is what keeps recurring billing audit-clean instead of producing duplicate or mis-totaled invoices.",
   "tags": [

package/data/craftbook-templates/re/refactor-module/manifest.json

@@ -3,14 +3,15 @@
   "kind": "craftbook-template",
   "id": "refactor-module",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Behavior-Preserving Refactor",
-  "description": "Refactor a module to improve its structure, readability, or design WITHOUT changing observable behavior — the defining constraint is that the tests stay green throughout. Plans the refactor FIRST — the target structure, the seams to introduce, the safe step sequence, and the green-tests guardrail — then refactors in small reversible steps, then a reviewer confirms behavior is unchanged and the code is genuinely cleaner. Covers extract-function/module, dependency seams, removing duplication, naming, and test-green-as-invariant refactoring.",
+  "description": "Restructure code without changing what it does, with proof at every stage: a green suite recorded before anything moves (characterization tests pinned first when coverage is thin), small reversible stages that keep the tests green, a re-measured structure target, and an enforced independent review.",
   "tags": [
-    "gallery",
     "refactor",
     "cleanup",
     "code-quality",
     "maintainability",
+    "duplication",
     "tests"
   ],
   "maintainer": {