@bendyline/gilde 0.1.39 → 0.1.40

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": [

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,6 +3,7 @@
   "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.",
   "tags": [

package/data/craftbook-templates/re/regex-builder/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "regex-builder",
   "role": "general",
+  "category": "code-data",
   "name": "Build + Test a Tricky Regex",
   "description": "Build a regular expression that matches exactly the right strings and rejects the wrong ones — specified with concrete should-match and should-NOT-match cases before a single character is written. Specs the cases FIRST — the positive examples, the tricky negative examples, edge cases, and the anchoring/flags — then builds the regex incrementally against those cases, then tests the full matrix including catastrophic-backtracking safety. Covers character classes, quantifiers, anchors, groups/captures, lookahead/behind, escaping, flags, and ReDoS-safe patterns validated by a should-match / should-not-match table.",
   "tags": [

package/data/craftbook-templates/re/release-announcement/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "release-announcement",
   "role": "general",
+  "category": "marketing",
   "name": "Release Announcement",
   "description": "Write a public-facing release announcement that turns a shipped version into a compelling story for users — a blog-post / email-style piece that leads with the headline value, shows the marquee features with concrete before/after benefits, links to the full release notes and upgrade path, and ends with a clear call to action. A planner picks the 2-4 things actually worth announcing and the audience/channel, a copywriter writes the benefit-led announcement in the brand voice, and a reviewer checks it is accurate, on-message, and that every claim traces to a real shipped change. Use this for product launch posts, 'what's new' announcements, version launch emails, and changelog-to-marketing translations.",
   "tags": [

package/data/craftbook-templates/re/release-artifact-sanity-check/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "release-artifact-sanity-check",
   "role": "maintenance-review",
+  "category": "code-release",
   "name": "Release Artifact Sanity Check",
   "description": "Sanity-check a folder of release artifacts without executing them: inventory every package, verify hashes and signatures against trusted evidence, safely inspect every file inside archives and application bundles, scan for suspicious or secret-bearing content, and produce an evidence-backed ship or no-ship report. Use this for release artifact verification, installer signing checks, package integrity audits, supply-chain inspection, or a pre-publish binary review.",
   "tags": [

package/data/craftbook-templates/re/release-notes/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "release-notes",
   "role": "general",
+  "category": "code-release",
   "name": "Release Notes",
   "description": "Turn a raw set of merged commits, pull requests, and ticket IDs into polished, human-readable release notes for a versioned release — grouped by theme (Features, Improvements, Bug Fixes, Breaking Changes), written for users rather than engineers, with upgrade/migration callouts surfaced first. The ordering is deliberate: a developer gathers and de-noises the change inventory before any prose is written, a copywriter turns that inventory into benefit-led notes in a consistent voice, and a reviewer verifies every shipped change is represented and nothing internal-only or unreleased leaked in. Use this for GitHub Releases, product announcement posts, or the user-facing notes that ship alongside a tagged version.",
   "tags": [

package/data/craftbook-templates/re/release-pipeline-ci/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "release-pipeline-ci",
   "role": "maintenance-review",
+  "category": "code-release",
   "name": "Release Pipeline (CI/CD)",
   "description": "Author a CI/CD release workflow as a YAML pipeline (GitHub Actions style) that takes a tagged commit and turns it into a published release — running tests and build as gates, then on a version tag building the artifact, generating release notes, publishing the package/image, and creating the GitHub Release, with the dangerous publish steps gated behind the green test/build stages and the tag trigger. A planner scopes the trigger, stages, secrets, and the publish target, a developer writes the valid pipeline YAML wiring the stages in the safe order, and a reviewer validates the syntax and that publishing cannot run before tests pass. Use this to set up automated releases, a publish-on-tag workflow, or a deploy pipeline from scratch.",
   "tags": [

package/data/craftbook-templates/re/release-readiness-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "release-readiness-review",
   "role": "maintenance-review",
+  "category": "code-release",
   "name": "Release Readiness Review",
   "description": "Run a go/no-go release readiness review against a structured pre-launch checklist and produce a sign-off report with a clear ship decision. First scopes the release and locks a readiness checklist (acceptance criteria met, tests and CI green, no open blockers, migrations and rollback ready, monitoring and alerts in place, docs and changelog updated, feature flags and config set, and on-call/comms prepared), then verifies each item by inspecting the actual state rather than assuming, then writes a go/no-go report listing every blocker that must clear before ship and the residual risks. Use this for a release readiness review, a go/no-go decision, a pre-launch checklist, a ship-readiness gate, a launch review, or deciding if a change is safe to deploy — it produces an evidence-backed ship decision rather than a gut-feel 'looks good'.",
   "tags": [

package/data/craftbook-templates/re/reliability-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "reliability-review",
   "role": "maintenance-review",
+  "category": "code-ops",
   "name": "Reliability & Resilience Review",
   "description": "Review a codebase for production reliability and resilience risks across asynchronous work, external dependencies, state transitions, resource lifecycles, and recovery paths. Uses the repository and per-file indexes to map failure domains, verifies likely issues in source and tests, and leaves a prioritized morning report covering timeouts, retries, idempotency, cancellation, concurrency, backpressure, cleanup, graceful shutdown, observability, and disaster recovery. Use for a weekly reliability sweep, resilience review, failure-mode audit, or pre-production hardening review.",
   "tags": [

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

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "report-pdf",
   "role": "general",
+  "category": "writing",
   "name": "Formatted Report",
   "description": "Produce a polished, print-ready PDF report from Markdown with DocBlocks — no hand-built HTML or browser print translator. Locks the audience, source facts, structure, and acceptance criteria first; writes the complete report as report.md; then converts, previews, and saves report.pdf in the project's artifacts drawer.",
   "tags": [

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

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "research-report",
   "role": "general",
+  "category": "research",
   "name": "Cited Research Report",
   "description": "Produce a rigorously cited research report that answers a specific question end to end: a planner first decomposes the question into sub-questions and locks the scope, then a researcher gathers and logs primary and secondary sources with inline citations, then a copywriter writes a structured markdown report (executive summary, findings, evidence, limitations, references). The ordering matters because a small model that writes before scoping rambles and a model that writes without a source log fabricates citations; locking sub-questions and a source table first turns the report into a fill-in-the-evidence exercise. Use this for literature-backed analysis, deep dives, investigative write-ups, background research, and any 'find out and write it up with sources' task where every claim must trace to a citation.",
   "tags": [

package/data/craftbook-templates/re/research-to-document/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "research-to-document",
   "role": "general",
+  "category": "writing",
   "name": "Word Document from Content or Research",
   "description": "Turn supplied content or a researched question into a real Word document (.docx, plus PDF on request) with DocBlocks. The workflow inventories sources, writes the reviewed source as Markdown, then converts, previews, and saves the finished file without hand-built document XML or an HTML intermediary.",
   "tags": [

package/data/craftbook-templates/re/rest-api/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "rest-api",
   "role": "project-starter",
+  "category": "code-data",
   "name": "REST API Service",
   "description": "Build a RESTful HTTP API service with resource endpoints, JSON request/response bodies, status codes, validation, and error handling. Locks the contract FIRST — resources, routes, verbs, request/response shapes, status-code map, auth, and pagination — so the implementation has a fixed target, then builds the server, then writes endpoint tests that exercise every route and error case. Covers CRUD endpoints, RESTful routing, OpenAPI-style contract, HTTP status codes, input validation, JSON serialization, and integration tests against the running handler.",
   "tags": [

package/data/craftbook-templates/re/resume-cv/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "resume-cv",
   "role": "general",
+  "category": "business",
   "name": "Résumé / CV",
   "description": "Build a clean, ATS-friendly résumé or CV from a person's background, tailored to a target role. Scopes the target role and the highlight reel of achievements FIRST (so the résumé is targeted, not a life history), then designs a single-column, parser-safe layout, then writes impact-led bullets with metrics that fit one to two pages. Use for job applications, LinkedIn-to-résumé conversions, and role-targeted CV rewrites.",
   "tags": [

package/data/craftbook-templates/re/reviewer-loop/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "reviewer-loop",
   "role": "maintenance-review",
+  "category": "practice",
   "name": "Reviewer Loop",
   "description": "Draft → critique → revise (looped until approved) → publish. A repeatable critique-and-revise pattern with explicit branching.",
   "tags": [

package/data/craftbook-templates/ro/rollback-plan/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "rollback-plan",
   "role": "general",
+  "category": "code-release",
   "name": "Rollback Plan",
   "description": "Author a concrete, tested rollback plan for a release so that when a deploy goes wrong the team can revert FAST and safely without improvising under pressure — covering the trigger conditions that mean 'roll back', the exact reversal steps (redeploy previous artifact, down-migrations, flag flips, cache/CDN invalidation), data-safety and forward/backward-compatibility considerations, the recovery-time estimate, and a post-rollback verification. A planner scopes the failure modes and triggers, a developer writes the precise step-by-step runbook with real commands, and a reviewer dry-runs it for correctness and irreversible-data hazards. Use this alongside any risky deploy, migration, or feature launch where 'how do we undo this' must be answered before, not during, an incident.",
   "tags": [

package/data/craftbook-templates/ro/root-cause-investigation/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "root-cause-investigation",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Root-Cause Investigation",
   "description": "Debug systematically: reproduce the failure and find the true root cause before changing any code, then fix and verify.",
   "tags": [

package/data/craftbook-templates/ro/rough-cut-assembly/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "rough-cut-assembly",
   "role": "general",
+  "category": "media",
   "name": "Rough Cut Assembly",
   "description": "Execute the cut list and prove it ran: every clip verified against the media index before anything renders, the assembly driven through the project's media pipeline with a run log, and the result checked against the expected duration — an assembly you can trust unwatched. Locks the pre-flight checks FIRST (clips exist, in and out points sit inside their durations, failure handling decided), then runs the assembly, then verifies and reports. Use for rough cuts, assembling a cutlist, executing an edit pass, render runs, and 'put the cut together'.",
   "tags": [

package/data/craftbook-templates/ru/runbook/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "runbook",
   "role": "general",
+  "category": "code-ops",
   "name": "Ops Runbook",
   "description": "Write an operational runbook or playbook a tired on-call engineer can follow at 3am without thinking — covering when to use it, prerequisites, numbered step-by-step procedures, verification, rollback, and escalation. Scopes the exact scenarios and prerequisites FIRST, writes unambiguous copy-pasteable steps with expected output and verification at each stage, then has a reviewer pressure-test it for gaps and dangerous ambiguity. Use for incident response, deploy/rollback procedures, and recurring ops tasks.",
   "tags": [

package/data/craftbook-templates/sc/schema-migration/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "schema-migration",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Schema / Type Migration",
   "description": "Plan and execute a multi-file schema or type migration safely — changing a data model, type definition, or interface across the codebase while keeping everything compiling and consistent. Plans the migration FIRST — the before/after shape, every call-site and file touched, the ordering that never leaves the tree broken, and the backout — then applies the change file-by-file, then a reviewer verifies the tree still builds and nothing referencing the old shape remains. Covers find-all-references, safe edit ordering, backward-compatibility shims, codemod-style changes, and compile/test-green verification.",
   "tags": [

package/data/craftbook-templates/sc/scrape-to-structured/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "scrape-to-structured",
   "role": "general",
+  "category": "code-data",
   "name": "Scrape a Site to Structured Data",
   "description": "Turn one or more web pages into a clean, structured dataset (JSON or CSV) with a fixed schema — product listings, directory entries, articles, tables, or job posts. Scopes the exact fields and a sample-row target FIRST so extraction is verifiable, then crawls and parses each page into rows, then validates that every row matches the schema, types are coerced, required fields are non-empty, and there are no duplicates. The scope-before-scrape ordering is the point: a small model that locks the field list and one hand-written sample row extracts consistently instead of inventing keys per page.",
   "tags": [

package/data/craftbook-templates/sc/script-automation/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "script-automation",
   "role": "general",
+  "category": "code-build",
   "name": "One-Off Automation Script",
   "description": "Write a one-off automation script that reliably does a repetitive task — process files, call an API, transform data — with arguments, a dry-run, idempotency, and clear logging so it is safe to run. Scopes the task FIRST — inputs/outputs, side-effects, the dry-run, idempotency, and failure handling — then implements the runnable script with args and a dry-run mode, then a reviewer confirms it does the job, is safe to re-run, and fails loudly. Covers argument handling, dry-run/preview mode, idempotent side-effects, progress logging, error handling, and safe-to-rerun automation.",
   "tags": [

package/data/craftbook-templates/sd/sdk-wrapper/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "sdk-wrapper",
   "role": "project-starter",
+  "category": "code-data",
   "name": "Typed SDK Wrapper for an External API",
   "description": "Wrap a third-party HTTP API as a clean, typed client library — studying the real API surface first so the wrapper matches reality, not guesses. Studies the API FIRST — endpoints, auth, request/response shapes, rate limits, error formats, and pagination from the actual docs — then builds a typed client with sensible methods and error handling, then tests each method against a mocked API including auth and error paths. Covers reading API docs, typed request/response models, auth handling, retry/rate-limit awareness, pagination helpers, error mapping, and a mockable client.",
   "tags": [

package/data/craftbook-templates/se/seasonal-maintenance-sweep/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "seasonal-maintenance-sweep",
   "role": "maintenance-review",
+  "category": "personal",
   "name": "Seasonal Maintenance Sweep",
   "description": "Run a season's home-care sweep against the project's systems roster: work out what care is due or overdue from each system's interval, plan the walkthrough in a sensible order with supplies, then log the completed care and flag what needs a professional — leaving the roster's due-tracking reset and a short sweep report. Locks the season's scope and the due list FIRST, then plans, then logs — so seasonal care becomes a checklist ritual instead of a vague worry. Use for spring/fall home maintenance, seasonal checkups, 'what does the house need', and pre-winter prep.",
   "tags": [

package/data/craftbook-templates/se/security-architecture-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "security-architecture-review",
   "role": "maintenance-review",
+  "category": "code-review",
   "name": "Security Architecture Review",
   "description": "A structured security architecture review: walk the stack for secrets, dependencies, auth, and common vulnerability classes, then report findings ranked by severity and confidence.",
   "tags": [

package/data/craftbook-templates/se/seo-meta-pack/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "seo-meta-pack",
   "role": "general",
+  "category": "marketing",
   "name": "SEO Metadata Pack",
   "description": "Generate a complete on-page SEO metadata pack for a set of pages: it first scopes each page's primary keyword and search intent and the length/format rules (title tag, meta description, Open Graph, Twitter card, slug), then writes optimized, unique metadata for every page that respects pixel/character limits and front-loads the keyword, producing a structured JSON file ready to drop into a CMS or templating layer. Covers SEO metadata, meta tags, title tags, meta descriptions, Open Graph tags, social cards, and on-page SEO. Scoping the keyword and limits per page before writing is the point: a small model that fixes the rules first produces unique, limit-respecting tags across the whole set, instead of duplicate titles and descriptions that get truncated in the SERP.",
   "tags": [

package/data/craftbook-templates/sh/ship/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "ship",
   "role": "general",
+  "category": "code-release",
   "name": "Ship",
   "description": "End-to-end release procedure: run tests, run a review pass, commit/push, open the PR, wait for CI to come back green, hand off for merge. Requires a GitHub-connected project on a feature branch.",
   "tags": [

package/data/craftbook-templates/so/social-digest/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "social-digest",
   "role": "maintenance-review",
+  "category": "marketing",
   "name": "Social Digest",
   "description": "The overnight read of your social feeds. Scans the synced Bluesky, X, and Instagram corpus records since the last look plus your own post index, then leaves a morning digest: what happened on each feed, notable mentions and replies with the people who wrote them, which posts moved on likes, reposts, and replies, and suggested next moves — each carrying a one-click action to draft the follow-up post or a reply task. Covers social media monitoring, engagement tracking, mention triage, and a nightly social summary grounded entirely in real synced records. No connected feed? It still runs, reports what the workspace knows, and names the gap instead of inventing activity.",
   "tags": [

package/data/craftbook-templates/so/social-thread/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "social-thread",
   "role": "general",
+  "category": "marketing",
   "name": "Social Media Thread",
   "description": "Write a multi-post social thread (X/Twitter, LinkedIn, Threads) that hooks, delivers, and converts: it first locks the single angle/big idea, the platform and its character limits, the target reader, and the CTA, then drafts the thread as numbered posts with a scroll-stopping hook, one idea per post, and a clear close. Covers Twitter thread, LinkedIn carousel copy, viral thread, social content, thought-leadership posts, and engagement hooks. Locking one angle and the hook before writing is the point: a small model that commits to a single big idea avoids the meandering thread that tries to say five things and stops no scroll.",
   "tags": [

package/data/craftbook-templates/so/source-quality-audit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "source-quality-audit",
   "role": "maintenance-review",
+  "category": "research",
   "name": "Source Quality Audit",
   "description": "Once a month, make the reading list earn its place: score each source on what it actually delivered — accuracy, originality, noise — and keep, demote, or drop with evidence, so the brief stays sharp as the feeds drift. Locks the audit criteria FIRST, then builds the per-source scorecard from the month's briefs, then writes the verdict table with the changes to make. Use for source audits, pruning the feed list, 'the brief feels noisy', monthly reading-list reviews, and deciding which feeds to drop.",
   "tags": [

package/data/craftbook-templates/sp/spa-dashboard/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "spa-dashboard",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Metrics / Admin Dashboard",
   "description": "Build a single-page metrics or admin dashboard with KPI summary cards, at least one chart, and a data table, rendered from sample or provided data. Locks the data model and which metrics matter first, then a scannable dashboard layout (grid of cards, chart placement, table), then builds the interactive HTML with a lightweight charting approach and a sortable/filterable table. Deciding the metrics and layout before coding prevents a small model from dumping raw data with no hierarchy; a dashboard's value is the at-a-glance summary up top.",
   "tags": [

package/data/craftbook-templates/sp/spec-authoring/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "spec-authoring",
   "role": "general",
+  "category": "code-docs",
   "name": "Spec Authoring",
   "description": "Turn a rough intent into a backlog-ready spec: interrogate scope and requirements against the real code, then file a well-formed, unambiguous issue.",
   "tags": [

package/data/craftbook-templates/sp/spec-doc/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "spec-doc",
   "role": "general",
+  "category": "code-docs",
   "name": "Technical Design Doc",
   "description": "Write a technical design document (RFC / engineering design doc) that gets a system change reviewed and approved — covering context and problem, goals and non-goals, the proposed design, alternatives considered, trade-offs, risks, and a rollout plan. Scopes the problem, goals, and explicit non-goals FIRST (non-goals prevent reviewer scope-creep), writes the detailed design with diagrams and alternatives, then has a reviewer check it for completeness and unjustified decisions. Use for RFCs, architecture proposals, and pre-implementation design reviews.",
   "tags": [

package/data/craftbook-templates/sp/spreadsheet-model/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "spreadsheet-model",
   "role": "general",
+  "category": "business",
   "name": "Spreadsheet / Financial Model",
   "description": "Build a working spreadsheet-style model (budget, forecast, unit economics, pricing, or scenario calculator) with clearly separated inputs, calculations, and outputs. Scopes the model's purpose, drivers, and assumptions FIRST so the formulas have a contract, then builds the model with live formulas and labeled assumption cells, then verifies the math by hand-checking key outputs and a sanity scenario. Use this for a financial model, budget calculator, ROI/forecast spreadsheet, unit-economics model, or any input-driven calculator.",
   "tags": [

package/data/craftbook-templates/sp/sprite-sheet/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "sprite-sheet",
   "role": "general",
+  "category": "media",
   "name": "Game Sprite Sheet",
   "description": "Produce a game-ready sprite sheet — a character or object with its animation frames (idle, walk, jump, attack) on a uniform grid — plus the frame metadata (JSON atlas) a game engine needs to slice it. Lock the style and the frame inventory FIRST (cell size, pivot, palette, which animations and how many frames each) because a sprite sheet is only usable if every cell is the same size and the pivot is consistent; then generate the frames and pack them into a sheet with a matching atlas. Covers sprite sheets, game art, animation frames, texture atlases, pixel-art characters, and 2D game assets.",
   "tags": [

package/data/craftbook-templates/sq/sql-analysis/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "sql-analysis",
   "role": "general",
+  "category": "code-data",
   "name": "Answer a Question with SQL",
   "description": "Answer a specific business question against a database or table set with a correct, readable SQL query and a short written answer. Scopes the question, the tables/columns, and the grain FIRST (so the query measures the right thing at the right level), then writes and runs the query as a data-analyst, then verifies the result with a sanity check and an explanation. Use this for SQL analysis, querying a database, writing a report query, computing a metric in SQL, or answering 'how many / what's the trend' from tables.",
   "tags": [

package/data/craftbook-templates/st/standup-summary/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "standup-summary",
   "role": "general",
+  "category": "business",
   "name": "Standup / Team Update Summary",
   "description": "Condense a pile of raw team updates (standup messages, async check-ins, channel dumps) into one clean summary grouped by person or workstream, surfacing blockers and decisions. Scopes the grouping axis and summary shape FIRST (by-person vs by-project, what counts as a blocker, the yesterday/today/blockers frame), then a copywriter compresses every raw update into that frame without dropping anyone. The scope-first step prevents a 4B model from rambling and guarantees blockers get their own callout section instead of being buried. Use for daily standup summaries, async update rollups, team check-in digests, and turning Slack threads into a readable recap.",
   "tags": [

package/data/craftbook-templates/st/state-machine/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "state-machine",
   "role": "project-starter",
+  "category": "code-data",
   "name": "Model a Flow as a State Machine",
   "description": "Model a stateful flow (checkout, order lifecycle, connection, wizard) as an explicit finite state machine with named states, guarded transitions, and rejected illegal moves — making impossible states impossible. Models the machine FIRST — the full state set, the events, the legal transition table, guards, and entry/exit effects — then implements a transition function that rejects illegal events, then tests every legal path and that illegal transitions are refused. Covers states/events/transitions, transition tables, guards, side-effects on entry, illegal-transition rejection, and exhaustive path testing.",
   "tags": [

package/data/craftbook-templates/st/status-report/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "status-report",
   "role": "general",
+  "category": "business",
   "name": "Recurring Status Report",
   "description": "Produce a recurring (weekly/biweekly) status report by gathering signals from the team's tools and writing a tight, skimmable update for stakeholders. Scopes the report template and the exact data sources FIRST (sections, audience, reporting window, RAG/health convention), then a developer gathers the raw signals from issue trackers, PRs, metrics, and notes into a facts file, then a copywriter writes the polished report strictly from those gathered facts. Scoping the template before gathering is what keeps every recurring issue consistent and prevents the model from padding with prose. Use for weekly status updates, sprint reports, project health reports, stakeholder updates, and exec summaries.",
   "tags": [

package/data/craftbook-templates/su/subscription-audit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "subscription-audit",
   "role": "maintenance-review",
+  "category": "business",
   "name": "Audit Recurring Subscriptions",
   "description": "Audit a set of transactions or a vendor list to find every recurring subscription, normalize each to a monthly cost, surface duplicates, price hikes, and zombie/unused services, and produce a prioritized cancel/keep recommendation report. Locks the recurrence-detection rule, the normalization (to monthly), and the recommendation criteria FIRST, then detects and analyzes the recurring charges, then writes a clear report whose every recommendation is backed by the evidence in the data. Defining what counts as 'recurring' and how to rank cancel candidates before analyzing is what makes the audit actionable rather than a list of guesses.",
   "tags": [

package/data/craftbook-templates/su/subtitle-generator/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "subtitle-generator",
   "role": "general",
+  "category": "media",
   "name": "Subtitle & Caption Generator",
   "description": "Generate time-synced subtitles/captions for a video in a standard caption format (SRT or WebVTT), so the video is accessible and watchable without sound. Scopes the caption format and timing/reading-speed rules FIRST, transcribes the audio with precise word timings, then formats those into properly cued, line-length-limited caption cues. The transcribe-then-format split is deliberate: getting accurate text and timings is a different skill from chunking them into readable, on-screen-friendly cues that respect reading speed and never overlap.",
   "tags": [

package/data/craftbook-templates/su/summarize-long/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "summarize-long",
   "role": "general",
+  "category": "writing",
   "name": "Summarize a Long Document",
   "description": "Distill a long document into a faithful, well-structured summary at a chosen depth: it first scopes the audience, the target length and format (TL;DR line, executive summary, or bulleted key points), and what the reader must take away, then writes the summary capturing every major point and decision in proportion, with nothing invented and nothing critical dropped. Covers summarize, TL;DR, executive summary, condense a document, key takeaways, and abstract writing. Scoping audience and depth before summarizing is the point: a small model that knows who it is for and how long it should be avoids both the bloated near-copy and the lossy summary that omits the document's actual conclusion.",
   "tags": [

package/data/craftbook-templates/su/survey-analysis/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "survey-analysis",
   "role": "general",
+  "category": "research",
   "name": "Survey Analysis",
   "description": "Analyze survey responses into a clear summary of what respondents actually said, across both quantitative (rating/multiple-choice) and open-text questions. Scopes the questions, response types, and segments FIRST, then analyzes — tallying closed questions and theming open-text comments as a data-analyst, then writes a findings summary with the headline results, segment differences, and representative quotes. Use this for analyzing survey results, summarizing a questionnaire, NPS/feedback analysis, theming open-ended responses, or a survey readout.",
   "tags": [

package/data/craftbook-templates/sv/svg-animation/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "svg-animation",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Animated SVG / CSS Hero",
   "description": "Build a single-file animated SVG or CSS hero section — a looping illustrated scene, an animated logo, or a motion banner driven by CSS keyframes or SMIL with no JavaScript animation library. Storyboards the motion (what moves, the timing, easing, and loop) first, then implements clean, performant, GPU-friendly animation. Motion looks amateur when timing and easing are unconsidered, so the motion-design phase locks the keyframe storyboard and respects prefers-reduced-motion before any markup, the ordering that yields a polished, smooth hero instead of janky tweens.",
   "tags": [

package/data/craftbook-templates/ta/tailor-resume/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "tailor-resume",
   "role": "general",
+  "category": "business",
   "name": "Tailor Résumé to a Posting",
   "description": "Adapt an EXISTING résumé to a specific job posting — a fit map of must-hit requirements first, then a tailored variant that re-orders and re-words real experience without inventing any. Distinct from building a résumé from scratch (see Résumé / CV): this book starts from a base résumé plus a posting and produces the targeted variant along with honest gap notes for the cover letter and interview. Use per serious application in a job search.",
   "tags": [