@bendyline/gilde 0.1.39 → 0.1.40

package/data/chat-models/qw/qwen3.8-27b-q2/manifest.json

@@ -0,0 +1,194 @@
+{
+  "schemaVersion": 1,
+  "kind": "chat-model",
+  "id": "qwen3.8-27b-q2",
+  "name": "Qwen 3.8 (27B, Q2)",
+  "description": "Alibaba's Qwen 3.8 at 27B parameters: a dense, multimodal agentic model with native text, image, and video understanding, 262K context, flexible reasoning effort, MTP, and native tool calling. Unsloth's dynamic UD-Q2_K_XL brings the 27B within reach of machines with 16GB+ usable memory while retaining more fidelity than the extreme IQ1_S build.",
+  "tags": [
+    "alibaba",
+    "agentic",
+    "coding",
+    "multimodal",
+    "vision",
+    "video",
+    "tools",
+    "reasoning",
+    "long-context"
+  ],
+  "category": "general",
+  "maintainer": {
+    "name": "Alibaba",
+    "url": "https://huggingface.co/Qwen/Qwen3.8-27B"
+  },
+  "version": "1.0.0",
+  "updatedAt": "2026-08-23T00:00:00Z",
+  "license": "Apache-2.0",
+  "licenseClass": "open",
+  "licenseShortName": "Apache 2.0",
+  "recoScore": 20,
+  "parameterSize": "27B",
+  "approxSizeBytes": 9828981664,
+  "supportsTools": true,
+  "contextWindow": 262144,
+  "upstream": "https://huggingface.co/Qwen/Qwen3.8-27B",
+  "style": {
+    "family": "qwen",
+    "reasoningFormat": "think",
+    "toolCallFormat": "function-call"
+  },
+  "behaviors": [
+    "reasoning.strip-think-tags",
+    "provider.merge-system-messages",
+    "mcp.compact-tool-schemas",
+    "provider.compact-write-transcript",
+    "fabrication.detect-past-tense-no-tools",
+    "turn.ollama-num-predict-bumped",
+    "turn.preamble-folding",
+    "turn.ramble-detection",
+    "tools.mlx-grammar",
+    "prompt.retrieval-first",
+    "prompt.workspace-gestalt",
+    "prompt.derive-by-execution"
+  ],
+  "tuning": {
+    "sampling": {
+      "temperature": 1,
+      "topP": 0.95,
+      "topK": 20,
+      "minP": 0,
+      "presencePenalty": 0,
+      "repetitionPenalty": 1,
+      "maxTokens": 12288
+    },
+    "samplingWhenThinking": {
+      "temperature": 1,
+      "topP": 0.95
+    },
+    "reasoning": {
+      "enableThinking": true,
+      "thinkingBudget": 4096,
+      "templateKwargs": {
+        "reasoning_effort": "medium"
+      }
+    },
+    "promptTags": {
+      "enableThinkingTag": "/think",
+      "disableThinkingTag": "/no_think"
+    },
+    "profiles": {
+      "thinking-general": {
+        "sampling": {
+          "temperature": 1,
+          "topP": 0.95,
+          "topK": 20,
+          "minP": 0,
+          "presencePenalty": 0,
+          "repetitionPenalty": 1,
+          "maxTokens": 12288
+        },
+        "reasoning": {
+          "enableThinking": true,
+          "thinkingBudget": 4096,
+          "templateKwargs": {
+            "reasoning_effort": "medium"
+          }
+        }
+      },
+      "thinking-deep": {
+        "reasoning": {
+          "enableThinking": true,
+          "thinkingBudget": 4096,
+          "templateKwargs": {
+            "reasoning_effort": "xhigh"
+          }
+        }
+      },
+      "thinking-coding": {
+        "sampling": {
+          "temperature": 1,
+          "topP": 0.95,
+          "topK": 20,
+          "minP": 0,
+          "presencePenalty": 0,
+          "repetitionPenalty": 1,
+          "maxTokens": 16384
+        },
+        "reasoning": {
+          "enableThinking": true,
+          "thinkingBudget": 4096,
+          "templateKwargs": {
+            "reasoning_effort": "medium"
+          }
+        }
+      },
+      "thinking-precise": {
+        "sampling": {
+          "temperature": 0.6,
+          "topP": 0.95,
+          "topK": 20,
+          "minP": 0,
+          "presencePenalty": 0,
+          "repetitionPenalty": 1,
+          "seed": 0,
+          "maxTokens": 6144
+        },
+        "reasoning": {
+          "enableThinking": true,
+          "thinkingBudget": 4096,
+          "templateKwargs": {
+            "reasoning_effort": "medium"
+          }
+        }
+      },
+      "instruct": {
+        "sampling": {
+          "temperature": 0.7,
+          "topP": 0.8,
+          "topK": 20,
+          "minP": 0,
+          "presencePenalty": 1.5,
+          "repetitionPenalty": 1,
+          "maxTokens": 4096
+        },
+        "reasoning": {
+          "enableThinking": false
+        }
+      },
+      "creative": {
+        "sampling": {
+          "temperature": 1,
+          "topP": 0.95,
+          "topK": 40,
+          "minP": 0,
+          "presencePenalty": 1.5,
+          "repetitionPenalty": 1,
+          "maxTokens": 8192
+        },
+        "reasoning": {
+          "enableThinking": false
+        }
+      }
+    },
+    "engine": {
+      "llamaCpp": {
+        "spec": {
+          "mtp": true,
+          "nMax": 4
+        }
+      }
+    }
+  },
+  "llamaCpp": {
+    "huggingfaceRepo": "unsloth/Qwen3.8-27B-GGUF",
+    "revision": "4ca720788d1e01f1bff70c033e0d0028fd02e502",
+    "filename": "Qwen3.8-27B-UD-Q2_K_XL.gguf",
+    "sha256": "fd4730dd8aad070517978752b63d530aeb1740d2283cab9fa24f1e404032ddb0",
+    "approxSizeBytes": 9828981664,
+    "quantization": "UD-Q2_K_XL",
+    "mmproj": {
+      "filename": "mmproj-F16.gguf",
+      "sha256": "cbb841a9ee0636b2ec172f5bb8df2ea8dfeb01e90fe7c6126581d662a0b4e43e",
+      "sizeBytes": 927607488
+    }
+  }
+}

package/data/chat-models/qw/qwen3.8-27b-q2/versions/1.0.0/manifest.json

@@ -0,0 +1,19 @@
+{
+  "schemaVersion": 1,
+  "version": "1.0.0",
+  "releasedAt": "2026-08-23T00:00:00Z",
+  "approxSizeBytes": 9828981664,
+  "llamaCpp": {
+    "huggingfaceRepo": "unsloth/Qwen3.8-27B-GGUF",
+    "revision": "4ca720788d1e01f1bff70c033e0d0028fd02e502",
+    "filename": "Qwen3.8-27B-UD-Q2_K_XL.gguf",
+    "sha256": "fd4730dd8aad070517978752b63d530aeb1740d2283cab9fa24f1e404032ddb0",
+    "approxSizeBytes": 9828981664,
+    "quantization": "UD-Q2_K_XL",
+    "mmproj": {
+      "filename": "mmproj-F16.gguf",
+      "sha256": "cbb841a9ee0636b2ec172f5bb8df2ea8dfeb01e90fe7c6126581d662a0b4e43e",
+      "sizeBytes": 927607488
+    }
+  }
+}

package/data/craftbook-templates/a1/a11y-audit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "a11y-audit",
   "role": "maintenance-review",
+  "category": "code-review",
   "name": "Accessibility Audit",
   "description": "Audit a web page or UI for accessibility against WCAG 2.1 AA and produce a prioritized remediation report. First scopes the components and flows in play and locks a WCAG checklist (semantic structure, keyboard operability, focus management, color contrast, alt text, form labels, ARIA correctness, motion/reflow), then audits each criterion by inspecting the markup, simulating keyboard and screen-reader use, and measuring contrast, then writes a findings report citing the failing WCAG success criterion, the affected element, and the fix. Use this for an accessibility audit, a11y review, WCAG compliance check, screen-reader or keyboard-navigation testing, or making a page accessible — it ties each defect to a numbered WCAG criterion with a concrete code remedy rather than vague 'improve accessibility' notes.",
   "tags": [

package/data/craftbook-templates/ab/ab-test-readout/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "ab-test-readout",
   "role": "general",
+  "category": "research",
   "name": "A/B Test Readout",
   "description": "Analyze a controlled experiment and produce a decision-ready readout: does the variant beat control, by how much, and is it real? States the hypothesis, the primary metric, and the decision rule FIRST (to avoid p-hacking and metric-shopping), then computes lift, statistical significance, and confidence intervals as a data-analyst, then writes a plain-language ship/no-ship recommendation. Use this for an experiment analysis, A/B test results, significance testing, conversion-lift readout, or an experiment decision memo.",
   "tags": [

package/data/craftbook-templates/ac/accessibility-retrofit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "accessibility-retrofit",
   "role": "maintenance-review",
+  "category": "code-review",
   "name": "Accessibility Retrofit (WCAG AA)",
   "description": "Take an existing HTML page and retrofit it to WCAG 2.1 AA — fixing semantic structure, alt text, color contrast, keyboard operability, focus visibility, form labels, ARIA, and landmarks — without changing the visual design. Audits the page against the AA success criteria first to produce a prioritized findings list, then applies the fixes in place. Accessibility work fails when fixes are guessed rather than measured, so the audit phase enumerates the concrete violations and the target criteria before any edit, and the loop runs back to the FIX phase until every finding is resolved.",
   "tags": [

package/data/craftbook-templates/ad/ad-variations/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "ad-variations",
   "role": "general",
+  "category": "marketing",
   "name": "A/B Ad Copy Variations",
   "description": "Generate a set of distinct, testable ad-copy variations for one offer across the angles worth A/B testing: it first locks the platform and its constraints (headline/description character limits), the offer, audience, and the distinct messaging angles to test (benefit, pain, social proof, urgency, curiosity), then drafts multiple complete variants per angle so each is a genuine test of a hypothesis rather than a trivial reword. Covers ad copy, A/B testing, Google/Facebook/LinkedIn ads, PPC copy, ad variations, and marketing experiments. Locking the angles and limits before writing is the point: a small model that commits to distinct hypotheses produces variants that actually test something, not ten near-duplicates that teach the advertiser nothing.",
   "tags": [

package/data/craftbook-templates/al/album-curate/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "album-curate",
   "role": "general",
+  "category": "media",
   "name": "Curate an Album",
   "description": "Turn a thousand camera-roll photos into the forty that tell the story: cull the near-duplicates, keep the keepers for honest reasons, caption what matters, and leave an album manifest the family will actually revisit. Locks the occasion and the selection criteria FIRST, then curates the manifest one moment at a time, then writes the album's short story. Use for curating an album, photo culling, 'make an album from the weekend', picking the keepers, and turning imports into albums.",
   "tags": [

package/data/craftbook-templates/al/alert-rules/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "alert-rules",
   "role": "general",
+  "category": "code-ops",
   "name": "Monitoring Alert Rules",
   "description": "Author a set of monitoring/alerting rules as a deployable config (Prometheus alerting rules, Grafana/Alertmanager YAML, or a CloudWatch-style spec): the right signals, thresholds, severities, for-durations, and routing labels. Scopes the SLOs and alert philosophy FIRST (what to alert on, symptom-vs-cause, thresholds and burn windows, severity ladder, noise budget), then a developer writes the rules config to that spec, then a reviewer validates for completeness, dedupe, and anti-flapping. Scoping thresholds and severities before writing YAML is what produces actionable, low-noise alerts instead of a wall of CPU-over-80% pages. Use for alerting rules, Prometheus alerts, SLO monitoring, on-call paging rules, and reducing alert fatigue.",
   "tags": [

package/data/craftbook-templates/al/alt-text-pass/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "alt-text-pass",
   "role": "general",
+  "category": "code-review",
   "name": "Alt-Text Pass",
   "description": "Generate accurate, WCAG-appropriate alt text for every image referenced by a site or folder and apply it back into the markup. Scope FIRST which images are content vs decorative (decorative images get empty alt, not a description) and the voice/length rules, because the most common alt-text failure is verbose, redundant, or wrong-purpose descriptions. Then caption each content image from what is actually visible and write the alt attributes back into the HTML. Covers accessibility, alt text, image descriptions, WCAG compliance, screen-reader support, and a11y retrofits.",
   "tags": [

package/data/craftbook-templates/an/anniversary-cut/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "anniversary-cut",
   "role": "general",
+  "category": "media",
   "name": "Anniversary Cut",
   "description": "Build the highlight reel for the occasion: the archive queried for the person and the years that matter, clips chosen with stated reasons, assembled through the project's media pipeline with a run log, and delivered with a chapter list and a dedication — the reel that makes the birthday. Locks the occasion and the selection criteria FIRST (era coverage, the famous moments in, a length budget), then selects from the archive with no invented footage, then assembles, then writes the presentation notes. Use for birthday reels, anniversary videos, memorial montages, 'make a highlight reel', and milestone tributes.",
   "tags": [

package/data/craftbook-templates/an/annotated-bibliography/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "annotated-bibliography",
   "role": "general",
+  "category": "research",
   "name": "Annotated Bibliography",
   "description": "Build a formal annotated bibliography for a research topic: a planner locks the scope, the citation style, and the annotation rubric (summary + evaluation + relevance), then a researcher locates each source and writes a consistent, properly-formatted annotation that summarizes, critically evaluates, and situates it for the research question. The ordering matters because annotations written without a fixed rubric vary wildly in depth and a bibliography assembled without a citation style is inconsistent; locking style and the three-part annotation rubric first yields a uniform, scholarly, reusable artifact. Use this for annotated bibliographies, a sourced reference list with summaries, research source logs, literature foundations for a paper, and 'list and evaluate my sources' requests.",
   "tags": [

package/data/craftbook-templates/an/annual-document-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "annual-document-review",
   "role": "maintenance-review",
+  "category": "personal",
   "name": "Annual Document Review",
   "description": "Walk a life binder's document roster once a year: inventory what is present and missing, confirm each present document is still current (right beneficiaries, right address, not expired), record the review so staleness tracking resets, and produce a prioritized to-do for the gaps. Locks the currency criteria per document kind FIRST, then verifies each record, then reports — so the binder's completeness claim is re-earned annually instead of rotting silently. Use for annual life-binder reviews, estate document checkups, 'is our paperwork still right', and insurance/beneficiary reviews.",
   "tags": [

package/data/craftbook-templates/an/anomaly-scan/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "anomaly-scan",
   "role": "general",
+  "category": "research",
   "name": "Anomaly / Outlier Scan",
   "description": "Scan a dataset for anomalies and outliers and report what is genuinely unusual versus expected noise. Defines the detection criteria and thresholds FIRST (statistical and rule-based, with an explicit definition of 'anomalous') so findings are reproducible, then runs the scan to flag and rank suspect records, then writes a prioritized report a human can triage. Use this for outlier detection, anomaly scanning, finding bad records, fraud/error spotting, or surfacing data points that don't fit.",
   "tags": [

package/data/craftbook-templates/ap/api-contract-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "api-contract-review",
   "role": "maintenance-review",
+  "category": "code-data",
   "name": "API Contract Review",
   "description": "Review an API contract or specification (OpenAPI/REST/GraphQL) for correctness, consistency, and developer ergonomics, then produce a findings report. First scopes the surface and locks an API design checklist (resource naming and HTTP semantics, status codes, pagination and filtering, error schema consistency, auth, versioning and backward compatibility, idempotency, and schema/type rigor), then reviews each endpoint and type against those rules and REST/GraphQL best practices, then writes a findings report rating each issue and giving the corrected contract snippet. Use this for an API design review, reviewing an OpenAPI/Swagger spec, a REST or GraphQL contract review, endpoint/schema critique, or checking an API for consistency and backward compatibility before it ships — it returns specific, spec-anchored fixes rather than 'make the API cleaner'.",
   "tags": [

package/data/craftbook-templates/ar/artifact-integrity-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "artifact-integrity-review",
   "role": "maintenance-review",
+  "category": "code-release",
   "name": "Artifact Integrity & Ship Review",
   "description": "Perform an isolated ship-readiness review of the actual built artifacts of a project—sites, npm packages, archives, CLIs, binaries, installers, checksums, signatures, and release bundles—rather than trusting source or CI status. Inventories expected versus present assets, stages immutable copies, inspects archive contents and metadata, runs safe sandboxed smoke checks where possible, and leaves per-artifact GO/NO-GO verdicts plus a release-wide decision. Can review locally staged assets or public-release evidence supplied to the project. Use before shipping a release or as a recurring artifact-integrity night-shift audit.",
   "tags": [

package/data/craftbook-templates/au/audio-ad-spot/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "audio-ad-spot",
   "role": "general",
+  "category": "media",
   "name": "Audio Ad Spot",
   "description": "Produce a short broadcast/podcast audio ad spot (15s/30s/60s) — a tightly-timed script with a hook, value, and a single call-to-action, synthesized into a finished, runtime-accurate voiced spot with optional music bed cue. Scopes the offer, exact runtime, and mandatory disclaimers FIRST, then synthesizes a voiced spot that hits the time target. Locking the runtime and CTA before recording is what makes a spot land in its slot and drive one action instead of overrunning or rambling.",
   "tags": [

package/data/craftbook-templates/au/audio-highlight-reel/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "audio-highlight-reel",
   "role": "general",
+  "category": "media",
   "name": "Audio Highlight Reel",
   "description": "Cut a long recording (podcast, interview, talk, stream) down to a short highlight reel of its best moments, delivered as a single stitched audio clip plus a cue sheet of the segments used. Locks selection criteria and target length FIRST, selects the strongest timestamped segments against those criteria, then assembles them into one clean reel with smooth joins. Defining 'what makes a highlight' and the runtime budget before cutting is what keeps the reel tight and on-theme instead of a random montage.",
   "tags": [

package/data/craftbook-templates/au/audiobook-master-pack/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "audiobook-master-pack",
   "role": "general",
+  "category": "media",
   "name": "Master the Audiobook",
   "description": "Assemble the finished chapters into a release: completeness swept against the manuscript first, the metadata manifest built and verified chapter by chapter, the master assembled through the project's media pipeline with a run log, and the listener-facing description written — the moment the folder of takes becomes a book. Locks the packaging rules FIRST (order, metadata fields, total duration), then the manifest, then the master, then the release copy. Use for mastering an audiobook, packaging the chapters, audiobook release prep, and 'all the chapters are rendered, now what'.",
   "tags": [

package/data/craftbook-templates/au/auth-flow/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "auth-flow",
   "role": "general",
+  "category": "code-build",
   "name": "Auth / Session Implementation",
   "description": "Implement an authentication and session flow — login, session/token issuance, verification, and logout — with the security fundamentals baked in. Threat-models FIRST to lock the security requirements — credential hashing, token/session strategy, expiry, CSRF/XSS posture, and the attacks in scope — then implements registration/login/verify/logout to those requirements, then a security-minded reviewer audits for the classic auth pitfalls. Covers password hashing (bcrypt/argon2), session vs JWT, token expiry/refresh, secure cookie flags, timing-safe comparison, CSRF protection, and brute-force throttling.",
   "tags": [

package/data/craftbook-templates/au/automation-recipe/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "automation-recipe",
   "role": "general",
+  "category": "personal",
   "name": "Write an Automation Recipe",
   "description": "Turn 'I wish the house would...' into an inspectable, versioned automation: triggers and actions that name real devices from the house's own inventory, a dry run through the device tools before anything is armed, and a manual override always written in. Locks the owner's intent and the safety rules FIRST (nothing that heats or locks runs unattended without a failsafe, an override path is mandatory, dry-run before arm), then drafts the recipe, then proves it against the devices — so the house only ever does what was actually asked, and never anything it cannot be talked out of. Use for home automations, 'make the lights do X', schedules and scenes, sensor-triggered routines, and wiring up a new smart-home behavior.",
   "tags": [

package/data/craftbook-templates/ba/backup-routine/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "backup-routine",
   "role": "general",
+  "category": "code-ops",
   "name": "Scheduled Backup or Export",
   "description": "Build a scheduled, idempotent backup/export routine that snapshots data (files, a database, or an app export) to a timestamped, optionally compressed destination, prunes old backups by a retention policy, and verifies each backup is restorable. Locks what to back up, the destination layout, the retention policy, and the integrity check FIRST, then builds the snapshot-write-verify-prune routine, then verifies a fresh backup is created, integrity-checked, and that retention deletes only what it should. Defining retention and an integrity check up front is the wisdom that turns backups from a false sense of safety into a tested recovery path.",
   "tags": [

package/data/craftbook-templates/bl/blog-post/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "blog-post",
   "role": "general",
+  "category": "marketing",
   "name": "SEO Blog Post",
   "description": "Write a complete, SEO-aware blog post that ranks and reads well: it locks the primary keyword, search intent, target reader, and a heading-by-heading outline FIRST, then drafts the full article in a single human voice with the keyword woven naturally into the title, intro, and H2s, and finally runs an editorial pass for clarity, flow, factual accuracy, and on-page SEO. Covers blog article, SEO content, how-to guide, listicle, thought-leadership post, content marketing, and organic-traffic writing. The scope-first ordering is the point: a small model that picks the keyword and outline before drafting avoids the classic failure of a rambling post that buries its topic and never satisfies the searcher's intent.",
   "tags": [

package/data/craftbook-templates/bo/board-deck/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "board-deck",
   "role": "general",
+  "category": "business",
   "name": "Board Meeting Deck",
   "description": "Build a board-meeting deck that briefs directors efficiently — an executive summary up top, KPI dashboard, financials, progress against goals, key risks/asks, and an appendix — structured so a director gets the state of the business in minutes. Locks the standard board narrative and the metrics that matter FIRST (boards want a consistent dashboard, not a redesign every quarter), designs a dense data-forward slide system, then builds a navigable HTML deck where every slide leads with its number and the asks are unmistakable. Use for quarterly board meetings, board updates, and investor board reports.",
   "tags": [

package/data/craftbook-templates/bo/board-game-web/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "board-game-web",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Digital Board Game",
   "description": "Build a single-file web version of a turn-based board game such as tic-tac-toe, checkers, connect-four, reversi, or a simple chess variant, with two-player hotseat or a basic AI opponent. Locks the rules, turn order, legal-move set, and win/draw detection first, then the board visual language, then implements an authoritative turn state machine. Board games demand correct turn alternation and exhaustive win/draw detection, so the rules phase enumerates every terminal condition before rendering — the ordering that stops a small model from shipping a board where turns desync or a win goes unnoticed.",
   "tags": [

package/data/craftbook-templates/bo/booking-automation/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "booking-automation",
   "role": "general",
+  "category": "code-build",
   "name": "Automate a Booking or Checkout Flow",
   "description": "Automate a multi-step booking, reservation, or checkout flow end-to-end — select, fill details, choose options, confirm — with a hard dry-run/confirmation guard so it never accidentally commits a real transaction during development. Maps the step-by-step flow, the success/failure signals, and the safety guard FIRST, then builds the resilient step driver with waits and retries, then tests both the happy path and the failure/abort paths against a stub or dry-run. Mapping-the-flow-and-guard-before-build is what makes booking automation safe and reliable instead of a brittle, money-spending click bot.",
   "tags": [

package/data/craftbook-templates/br/branding-website/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "branding-website",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Branding Website",
   "description": "Build a small brand/marketing website where the visual identity leads. Locks a visual language and mockups FIRST, then writes the copy, then builds the HTML to the locked design — the ordering that makes brand sites feel designed rather than templated.",
   "tags": [

package/data/craftbook-templates/br/broadcast-announcement/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "broadcast-announcement",
   "role": "general",
+  "category": "marketing",
   "name": "Multi-Channel Broadcast Announcement",
   "description": "Adapt a single announcement (launch, policy change, maintenance window, org news) into channel-tailored variants — email, Slack/Teams post, status-page note, and a short SMS/push — that carry one consistent core message at the right length and tone for each surface. Scopes the core message and the per-channel constraints FIRST (the single source of truth, the CTA, character/format limits and tone per channel, the must-include facts), then a copywriter writes every variant from that locked core so nothing contradicts across channels. Scoping the core before adapting is what keeps the facts, dates, and CTA identical everywhere while the voice fits each surface. Use for announcements, multi-channel comms, launch messaging, maintenance notices, and broadcasting one message everywhere.",
   "tags": [

package/data/craftbook-templates/br/browser-qa-audit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "browser-qa-audit",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Browser QA Audit",
   "description": "Exercise a running app in a real browser, triage what breaks, and produce a report-only QA findings list with a health score — no code changes.",
   "tags": [

package/data/craftbook-templates/bu/bug-fix-tdd/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "bug-fix-tdd",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Reproduce-Then-Fix a Bug",
   "description": "Fix a bug the disciplined way: first write a failing test that reproduces it, then make the smallest change that turns the test green without breaking others, then verify and guard against regression. Reproduces FIRST with a red test that captures the exact wrong behavior — because a bug you cannot reproduce you cannot prove fixed — then applies the minimal fix, then a reviewer confirms the new test passes, root cause is addressed, and the suite is green. Covers test-driven bug fixing, regression tests, minimal diffs, root-cause vs symptom, and red-green verification.",
   "tags": [

package/data/craftbook-templates/bu/build-loop/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "build-loop",
   "role": "general",
+  "category": "practice",
   "name": "Build Loop",
   "description": "Generic make-something procedure: scope the work and lock concrete acceptance criteria, build it, evaluate the result against those criteria, and loop back to building until every criterion is met — then finish. The fallback structure when no domain-specific craftbook fits.",
   "tags": [

package/data/craftbook-templates/ca/calendar-brief/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "calendar-brief",
   "role": "general",
+  "category": "business",
   "name": "Daily Calendar & Prep Brief",
   "description": "Assemble a morning brief from the day's calendar: a chronological agenda with per-meeting prep notes, conflicts flagged, and a short focus-time/priorities summary. Scopes the brief layout and prep rules FIRST (which meetings need prep, what prep means, how to flag conflicts and back-to-backs), then a developer pulls the day's events and assembles the brief deterministically against those rules. The scope-first ordering ensures the brief always flags double-bookings and attaches the right context (attendees, agenda, links) instead of just dumping a raw event list. Use for daily agenda briefs, meeting prep, morning planning, schedule rundowns, and turning a calendar into an actionable day plan.",
   "tags": [

package/data/craftbook-templates/ca/canvas-generative-art/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "canvas-generative-art",
   "role": "project-starter",
+  "category": "design",
   "name": "Canvas Generative Art",
   "description": "Build a single-file generative art piece on canvas — flow fields, particle systems, recursive trees, Voronoi, noise terrain, or geometric tilings — that produces a fresh composition each run from a seed, with parameters the viewer can tweak. Defines the aesthetic and the generative algorithm first, then implements a seeded, reproducible renderer with a regenerate control. Generative art is an algorithm-and-aesthetic problem, so the aesthetic-scope phase locks the visual rules and the seedable randomness before any drawing, the ordering that yields a deliberate piece rather than random noise.",
   "tags": [

package/data/craftbook-templates/ca/careful-mode/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "careful-mode",
   "role": "general",
+  "category": "practice",
   "name": "Careful Mode",
   "description": "Safety guardrails for destructive commands",
   "tags": [

package/data/craftbook-templates/ca/case-study/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "case-study",
   "role": "general",
+  "category": "marketing",
   "name": "Customer Case Study",
   "description": "Write a persuasive, evidence-backed customer success story in the classic challenge-solution-results arc: it first scopes the customer, the quantified before/after metrics, the approved customer quotes, and the single takeaway for prospects, then writes the case study with a results-forward summary, a relatable challenge, the solution narrative, and a measurable results section, then a review pass verifies every number and quote and the persuasive flow. Covers case study, customer success story, customer testimonial, success story, proof point, and B2B marketing content. Scoping the metrics and quotes before writing is the point: a small model that locks the quantified results first writes a credible story buyers trust, instead of a vague testimonial with adjectives but no proof.",
   "tags": [

package/data/craftbook-templates/ca/case-study-writeup/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "case-study-writeup",
   "role": "general",
+  "category": "marketing",
   "name": "Customer Case Study",
   "description": "Write a persuasive customer/case-study writeup that turns a customer's results into a credible marketing asset — challenge, solution, and quantified results in the classic before/after arc, with a pull-quote and a clear CTA. Scopes the customer story and the hard metrics FIRST (results without numbers are not a case study), writes the narrative copy in the proven challenge-solution-results structure, then builds a clean, branded single-page HTML asset with a results-highlight band and quote callout. Use for marketing case studies, customer success stories, and sales proof assets.",
   "tags": [

package/data/craftbook-templates/ch/changelog-cut/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "changelog-cut",
   "role": "general",
+  "category": "code-release",
   "name": "Changelog Cut",
   "description": "Cut a new versioned section into a Keep a Changelog / CHANGELOG.md style file for a release — moving entries out of the Unreleased section into a dated, semver-stamped version block under the standard Added / Changed / Deprecated / Removed / Fixed / Security headings, with a fresh empty Unreleased section left behind. A developer gathers the unreleased entries and reconciles them against actual merged changes before a copywriter normalizes them into terse, consistent changelog lines and stamps the version block. Use this whenever you 'cut a release', 'update the changelog', or roll the Unreleased section into a tagged version while keeping the file append-only and machine-comparable.",
   "tags": [

package/data/craftbook-templates/ch/changelog-writeup/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "changelog-writeup",
   "role": "general",
+  "category": "code-release",
   "name": "Human-Readable Changelog",
   "description": "Turn raw commit/PR history into a human-readable changelog that users actually understand: a developer first gathers and triages the merged changes since the last release into user-facing buckets (Added, Changed, Fixed, Deprecated, Removed, Security), filtering out noise like internal refactors, then a copywriter rewrites each entry in plain, benefit-oriented language with breaking changes called out. Covers changelog, release notes, what's new, version notes, and Keep a Changelog format. Gathering and triaging before writing is the point: a small model that first separates user-facing changes from internal churn avoids the changelog that lists 'bump deps' next to a breaking API change with equal weight.",
   "tags": [

package/data/craftbook-templates/ch/chapter-narration-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chapter-narration-run",
   "role": "general",
+  "category": "media",
   "name": "Narrate a Chapter",
   "description": "Take one chapter from manuscript to narrated audio, deliberately: a narration script with pronunciations and pauses marked before anything renders, the audio driven through the project's narration capabilities with a run log, and a listen-check against the text — no skipped paragraphs, no mangled names. Locks the chapter and the style sheet FIRST (voice, pace, every proper noun's pronunciation), then preps the script, then renders, then checks coverage. Use for narrating a chapter, audiobook recording runs, text-to-speech passes, and 'read chapter two aloud'.",
   "tags": [

package/data/craftbook-templates/ch/chapter-weave/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chapter-weave",
   "role": "general",
+  "category": "writing",
   "name": "Weave a Chapter",
   "description": "Weave the banked sessions into one memoir chapter in the teller's voice: every scene traceable to something actually said, gaps marked for a future session instead of invented — the ritual that turns interviews into a book. Locks the chapter's arc and the no-invention rules FIRST, then drafts from session material only, with a faithfulness pass that loops until every detail traces. Use for drafting a memoir chapter, weaving sessions into a story, and 'turn the interviews into a chapter'.",
   "tags": [

package/data/craftbook-templates/ch/character-sheet/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "character-sheet",
   "role": "general",
+  "category": "media",
   "name": "Character Sheet",
   "description": "Lock a character before the pages need them: reference images across the poses and expressions the story calls for, the palette and silhouette written down, and every seed and prompt persisted in a manifest — so page twelve's hero is page one's hero. Locks the character brief FIRST — silhouette, palette, expression and pose list — then generates the reference set with its manifest, then lays the contact sheet anyone can draw from. Use for character sheets, locking a character's look, reference sets before more pages, 'keep them looking the same', and building a comic's cast bible.",
   "tags": [

package/data/craftbook-templates/ch/character-turnaround/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "character-turnaround",
   "role": "general",
+  "category": "media",
   "name": "Character Turnaround",
   "description": "Give one character the full turnaround treatment: front, side, back, and three-quarter views generated against the same style anchor, every view manifest-recorded with the seed and prompt that made it — the reference every future sprite leans on. Locks the angle list and the style anchor FIRST, then generates the views as one consistent figure, then writes the records and the summary. Use for character turnarounds, 'we need the knight from all sides', sprite reference sets, model sheets for game characters, and locking a character before animation work.",
   "tags": [

package/data/craftbook-templates/ch/chart-pack/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chart-pack",
   "role": "general",
+  "category": "research",
   "name": "Chart Pack from Data",
   "description": "Build a single interactive HTML page of charts that answers a defined set of questions about a dataset. Scopes the questions and the right chart type per question FIRST (so you don't make a pretty chart that answers nothing), then analyzes the data into chart-ready series, then builds one self-contained HTML page rendering every chart with titles, axis labels, and a one-line takeaway caption each. Use this for a dashboard of charts, a visualization pack, a metrics page, or turning a CSV into graphs and plots.",
   "tags": [

package/data/craftbook-templates/ch/chrome-extension/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chrome-extension",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Browser Extension",
   "description": "Build a Manifest V3 browser extension scaffold — a popup, a content script, and the manifest — that does one concrete thing on the current page (highlight, count, extract, or toggle). Scopes the single capability and the required permissions first, designs the popup UI, then builds a valid manifest.json plus popup and content-script files wired by messaging. Extensions fail at the manifest and the popup↔content messaging boundary, so the scope phase pins the exact MV3 permissions and message contract before any code, keeping a small model from producing a manifest the browser rejects.",
   "tags": [