@bendyline/gilde 0.1.39 → 0.1.40

package/data/craftbook-templates/es/escalation-playbook/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "escalation-playbook",
   "role": "general",
+  "category": "code-ops",
   "name": "On-Call Escalation Playbook",
   "description": "Author an on-call escalation playbook: the severity ladder, who-to-page-when escalation tiers with timeouts, communication cadence to stakeholders, and the step-by-step actions for each severity. Scopes the severity definitions and escalation policy FIRST (SEV levels with concrete examples, tier timeouts, roles, comms channels and cadence), then a copywriter writes the playbook in clear, do-this-now imperative steps, then a reviewer validates it for completeness and that no severity dead-ends without an escalation path. Scoping the SEV ladder and timeouts before writing prose is what makes the playbook unambiguous at 3am. Use for on-call runbooks, incident escalation policy, paging tiers, severity ladders, and SRE escalation procedures.",
   "tags": [

package/data/craftbook-templates/ev/evidence-brief/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "evidence-brief",
   "role": "general",
+  "category": "research",
   "name": "Decision Evidence Brief",
   "description": "Answer a specific decision question with a weighted, confidence-rated evidence brief: a planner frames the decision and the options, locks the evidence criteria and a confidence scale, a researcher gathers evidence for and against each option and rates the strength of each piece, and a copywriter writes a decision-oriented brief that states a recommendation with explicit confidence levels and the key uncertainties. The ordering matters because evidence gathered before framing the decision is unfocused and a recommendation without a confidence scale hides how strong the case really is; fixing the question, the options, and a confidence rubric first produces an honest, decision-ready brief. Use this for evidence-based decision support, 'what does the evidence say we should do about X', recommendation memos, weighing options with confidence levels, and policy/strategy briefs grounded in sources.",
   "tags": [

package/data/craftbook-templates/ex/executive-level-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "executive-level-review",
   "role": "maintenance-review",
+  "category": "practice",
   "name": "Executive-Level Review",
   "description": "A strategic, executive-level review of a plan or scope: challenge the premise, weigh alternatives, and score each dimension before committing — the 'should we even build this' p...",
   "tags": [

package/data/craftbook-templates/ex/expense-categorize/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "expense-categorize",
   "role": "general",
+  "category": "business",
   "name": "Categorize Transactions",
   "description": "Classify a list of bank/card transactions into a fixed chart-of-accounts category set, with confidence and a review queue for the uncertain ones, producing a clean categorized ledger ready for bookkeeping or tax. Locks the category taxonomy and the matching rules (merchant patterns, amount/sign heuristics) FIRST, then categorizes every transaction deterministically-first then by inference, then reviews that the taxonomy is closed, low-confidence rows are queued not force-fit, and totals reconcile to the input. Rules-before-categorize is the wisdom: a defined taxonomy plus rule precedence makes results auditable and repeatable, not a one-off guess.",
   "tags": [

package/data/craftbook-templates/fa/fact-check/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "fact-check",
   "role": "maintenance-review",
+  "category": "research",
   "name": "Fact-Check a Set of Claims",
   "description": "Verify a set of claims one by one and produce a verdict report: a planner extracts and itemizes every checkable claim and locks the rating scale, a researcher independently verifies each claim against primary sources and logs the evidence, and a reviewer compiles a per-claim verdict report with ratings and corrections. The ordering matters because verifying before itemizing lets claims slip through unchecked, and a report without a fixed rating scale gives inconsistent verdicts; isolating each atomic claim and locking the scale first makes the check exhaustive and auditable. Use this for fact-checking articles or statements, verifying claims, debunking, accuracy passes, and 'is this true' / 'check these facts' requests.",
   "tags": [

package/data/craftbook-templates/fa/family-story-chapter/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "family-story-chapter",
   "role": "general",
+  "category": "writing",
   "name": "Family Story Chapter",
   "description": "Write one chapter of the family story from the record you actually have — interviews and tree facts woven into narrative, speculation clearly dressed as speculation — the ritual that turns an archive into the book every family means to write. Locks the chapter's arc and the sourcing rules FIRST, then drafts from the record only, with a faithfulness pass that loops until every event traces. Use for drafting a family history chapter, writing up the emigration years, turning interviews into narrative, and 'write the family story'.",
   "tags": [

package/data/craftbook-templates/fa/faq-from-docs/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "faq-from-docs",
   "role": "general",
+  "category": "writing",
   "name": "FAQ from Source Docs",
   "description": "Build a grounded FAQ page by mining real source documents for the questions users actually ask, then writing tight, accurate answers traced back to the source: it first researches the corpus to extract candidate questions, dedupes and groups them, and ranks by likely frequency, then writes clear question-and-answer pairs where every answer is supported by the docs. Covers FAQ generation, help center questions, support docs, knowledge mining, common questions, and self-service content. Mining the source before writing is the point: a small model that derives questions from the actual docs avoids inventing FAQs nobody asks and answers the docs cannot support.",
   "tags": [

package/data/craftbook-templates/fa/favicon-set/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "favicon-set",
   "role": "general",
+  "category": "design",
   "name": "Favicon & App-Icon Set",
   "description": "Generate the complete favicon and app-icon set a modern site needs — the multi-size favicon, Apple touch icon, Android/maskable icons, and the web app manifest plus the exact HTML link/meta tags — from a single source mark, ensuring the icon stays legible at 16px and the maskable variant survives platform cropping. Lock FIRST the source mark, the exact size matrix, and the safe-area/padding rules (maskable icons need extra padding or platforms clip them) because favicon sets fail when the icon is illegible tiny or gets cropped on Android; then generate every size and emit the manifest + install snippet. Covers favicons, app icons, PWA icons, touch icons, maskable icons, and the web app manifest.",
   "tags": [

package/data/craftbook-templates/fe/feature-flag-release/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "feature-flag-release",
   "role": "general",
+  "category": "code-release",
   "name": "Feature Flag Release Plan",
   "description": "Plan and document a progressive feature-flag rollout for shipping a change behind a flag — defining the flag and its default-off state, the staged ramp (internal → 1% → 10% → 50% → 100%) with the success and guardrail metrics that gate each step, the automatic rollback/kill-switch criteria, and the cleanup that removes the flag once fully rolled out. A planner scopes the flag, ramp stages, and metrics, a developer writes the rollout runbook with the exact flag changes and the kill-switch procedure, and a reviewer verifies each ramp step has a measurable gate and a safe abort. Use this for gradual rollouts, canary releases, dark launches, percentage-based ramps, and de-risking a risky change behind a toggle.",
   "tags": [

package/data/craftbook-templates/fe/feature-flag-rollout/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "feature-flag-rollout",
   "role": "maintenance-review",
+  "category": "code-release",
   "name": "Flagged Feature Rollout",
   "description": "Add a new feature behind a feature flag so it can ship dark, be toggled per-environment/user, and roll back instantly without a deploy. Plans the flag contract FIRST — the flag name/default, the toggle points, the on/off behavior, the targeting (env/percentage/user), and the cleanup plan — then implements the flagged code with both paths working, then a reviewer verifies both states behave and the off-state default is safe. Covers feature flags, toggle points, percentage/targeted rollout, default-off safety, dark launches, and flag-cleanup discipline.",
   "tags": [

package/data/craftbook-templates/fe/feedback-widget/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "feedback-widget",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Embeddable Feedback Widget",
   "description": "Build a single-file embeddable feedback, contact, or rating widget — a floating button that opens a small panel with a rating, a message field, and validation, then shows a thank-you state and persists submissions to localStorage. Scopes the fields, validation, and submission behavior first, designs the floating launcher and panel, then implements an accessible, self-contained widget that drops into any page. Feedback widgets fail when submit does nothing, validation is missing, or the panel cannot be closed, so the scope phase locks the field set and the submit-and-thank-you flow before any markup.",
   "tags": [

package/data/craftbook-templates/fo/folder-to-audio/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "folder-to-audio",
   "role": "general",
+  "category": "media",
   "name": "Text-to-Speech a Folder",
   "description": "Turn a folder of text files (articles, chapters, notes, markdown) into a set of spoken audio files using text-to-speech, so a reading list becomes a listening list. Scopes the voice, file mapping, and chunking rules FIRST so long inputs do not get truncated or mispronounced, then synthesizes one audio artifact per source file with a consistent voice, then verifies every file was rendered and is audible. The scope-before-synthesize ordering is the point: deciding chunk size, file naming, and a manifest up front is what keeps a batch TTS run complete and re-runnable instead of half-finished.",
   "tags": [

package/data/craftbook-templates/fo/forecast-model/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "forecast-model",
   "role": "general",
+  "category": "research",
   "name": "Simple Forecast / Trend Model",
   "description": "Build a simple, defensible forecast of a time series (revenue, demand, signups, usage) with the assumptions and method stated up front and the projection plus a confidence band as the output. Scopes the series, horizon, method, and assumptions FIRST (so the forecast isn't an unexplained black box), then builds the projection with a baseline and an interval, then reviews it for sanity against history and overfitting. Use this for forecasting a metric, projecting a trend, estimating future demand, a simple time-series projection, or a 'what will this be next quarter' estimate.",
   "tags": [

package/data/craftbook-templates/fo/form-fill-batch/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "form-fill-batch",
   "role": "general",
+  "category": "code-build",
   "name": "Batch-Fill Forms from a Dataset",
   "description": "Automate filling a web or PDF form once per row of an input dataset — registrations, applications, data-entry portals, mail-merge into a form. Scopes the field-to-column mapping and a per-row success signal FIRST, then builds a loop that loads each record, maps it onto the form fields, submits, and records the outcome, then verifies every row was attempted, each submission was confirmed, and failures are logged with the reason. Mapping-before-build is the wisdom: lock the column→field map and the 'submitted OK' signal so the run is idempotent, resumable, and auditable rather than a blind click-through.",
   "tags": [

package/data/craftbook-templates/fo/form-wizard/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "form-wizard",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Multi-Step Form Wizard",
   "description": "Build a single-file multi-step form wizard — a signup, checkout, survey, or onboarding form split across steps with a progress indicator, per-step validation, back/next navigation, and a final review-and-submit. Designs the step flow, fields per step, and validation rules first, then implements stateful navigation that preserves entered data across steps. Wizards break when going back loses data or a step advances with invalid input, so the flow-design phase locks the field-per-step map and validation before any markup.",
   "tags": [

package/data/craftbook-templates/fr/freeze-scope/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "freeze-scope",
   "role": "general",
+  "category": "practice",
   "name": "Freeze Scope",
   "description": "Confine all workspace writes to one directory",
   "tags": [

package/data/craftbook-templates/ga/game-with-screens/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "game-with-screens",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Full Game with Title & Game-Over Screens",
   "description": "Build a complete single-file HTML game with the full screen flow — a title/start screen, the gameplay screen, a game-over screen showing the score, and a restart back to a fresh game — wrapping any core arcade or survival mechanic. Designs the mechanic and the screen-state machine first, a cohesive visual look across all screens, then implements a screen manager so transitions are clean and restart truly resets. Many small models nail gameplay but ship with no start or game-over screen; this archetype makes the screen flow a first-class, gated requirement.",
   "tags": [

package/data/craftbook-templates/gl/glossary-build/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "glossary-build",
   "role": "general",
+  "category": "code-docs",
   "name": "Domain Glossary",
   "description": "Build a consistent, accurate glossary for a domain: a planner sets the domain scope, the term-selection criteria, and the entry template, a researcher gathers the canonical definition and usage for each term with sources, and a copywriter writes the alphabetized glossary with cross-references and consistent entries. The ordering matters because terms picked ad hoc leave gaps and inconsistent entries confuse readers; locking the scope, what makes a term in-scope, and a fixed entry template first guarantees coverage and a uniform, cross-linked glossary. Use this for building a domain or product glossary, a terms/definitions reference, an acronym list, onboarding vocabulary, and 'define all the key terms in X' requests.",
   "tags": [

package/data/craftbook-templates/gr/graphql-api/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "graphql-api",
   "role": "project-starter",
+  "category": "code-data",
   "name": "GraphQL API",
   "description": "Build a GraphQL API with a typed schema (SDL), resolvers, queries, mutations, and input validation. Designs the schema FIRST — types, fields, nullability, query/mutation operations, and the resolver-to-data mapping — because in GraphQL the schema IS the contract, then implements resolvers, then writes operation tests covering each query, mutation, and error. Covers GraphQL schema definition language, resolvers, nullable vs non-null fields, mutations, query arguments, N+1 awareness, and error handling.",
   "tags": [

package/data/craftbook-templates/gr/grpc-service/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "grpc-service",
   "role": "project-starter",
+  "category": "code-data",
   "name": "gRPC Service",
   "description": "Build a gRPC service from a Protocol Buffers contract — define the .proto service and messages, implement the server handlers, and verify with client calls including streaming and status codes. Designs the proto contract FIRST — the service, RPC methods, request/response messages, field numbers, and the streaming kinds — because the .proto is the binding contract across languages, then implements the handlers, then tests unary/streaming calls and gRPC status codes. Covers protobuf service/message definitions, field numbering, unary vs server/client/bidi streaming, gRPC status codes, deadlines, and a client-driven test.",
   "tags": [

package/data/craftbook-templates/ha/handbook-section/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "handbook-section",
   "role": "general",
+  "category": "writing",
   "name": "Team Handbook Section",
   "description": "Write a clear, reference-grade section of a team/company handbook — a policy, process, or how-we-work doc that a new hire can read once and act on correctly. Scopes the policy's intent, audience, and edge cases FIRST, writes unambiguous prose with concrete examples, a quick-reference summary, and FAQ, then has a reviewer check it for ambiguity and contradictions with how things actually work. Use for onboarding docs, policy pages, process documentation, and internal wikis.",
   "tags": [

package/data/craftbook-templates/he/hero-image/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "hero-image",
   "role": "general",
+  "category": "media",
   "name": "Marketing Hero Image",
   "description": "Create a single high-impact marketing hero image from a brief and place it into a working hero section. Lock the brief FIRST — aspect ratio, subject, mood, palette, focal point, and crucially the safe zone where headline and CTA text will overlay — because a beautiful hero that has no room for copy (or whose focal point sits under the button) is useless. Then generate the image to the brief and place it behind real overlaid text to prove it works. Covers hero banners, marketing imagery, landing-page art, website headers, and key visuals.",
   "tags": [

package/data/craftbook-templates/ho/holiday-card-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "holiday-card-run",
   "role": "general",
+  "category": "personal",
   "name": "Holiday Card Run",
   "description": "Make the December run a pleasure instead of a panic: sweep the address list while there is still time to fix it, settle the card message, and produce the print-ready card and the address sheet in one sitting. Locks the roster sweep and the message criteria FIRST, then builds the card, then the address sheet, then reports the gaps that still need a human. Use for holiday cards, the annual card run, 'time for the holiday cards', address list cleanup before card season, and the December mailing.",
   "tags": [

package/data/craftbook-templates/ho/hotfix-flow/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "hotfix-flow",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Hotfix Flow",
   "description": "Drive an expedited production hotfix from red to green: reproduce the live defect with a failing test, apply the smallest safe fix that makes it pass without scope-creeping into a refactor, and verify the fix plus a clean regression check before it ships out-of-band. The ordering is the whole discipline — reproduce FIRST (a failing test that captures the bug is the contract the fix must satisfy), then fix minimally, then verify the new test passes and nothing else broke. Use this for urgent production bugs, expedited patch releases, and out-of-band fixes where speed matters but a regression would be worse than the original bug.",
   "tags": [

package/data/craftbook-templates/ht/html-arcade-game/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "html-arcade-game",
   "role": "project-starter",
+  "category": "code-build",
   "name": "HTML Arcade Game",
   "description": "Build a playable single-file HTML/canvas arcade game (shooter, runner, dodger, etc.). Splits design into game-mechanics and visual look, builds, then evaluates against a playability bar and loops until it is actually fun and bug-free.",
   "tags": [

package/data/craftbook-templates/ht/html-puzzle-game/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "html-puzzle-game",
   "role": "project-starter",
+  "category": "code-build",
   "name": "HTML Puzzle Game",
   "description": "Build a single-file HTML logic or puzzle game such as a match-3, sliding tile, Sokoban, 2048, minesweeper, or sudoku. Locks the rule system, the solve/fail condition, and the win detection first, then a clean grid visual language, then implements deterministic board state with valid-move enforcement. Puzzle games live or die on correct rules and reliable win detection, so the design phase pins the exact legal-move and victory logic before any rendering — the ordering that prevents a small model from shipping a grid that looks right but never registers a win.",
   "tags": [

package/data/craftbook-templates/ic/icon-pack/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "icon-pack",
   "role": "general",
+  "category": "design",
   "name": "Coherent Icon Pack",
   "description": "Produce a coherent set of UI icons that look like they belong to one family — consistent grid, stroke weight, corner radius, optical sizing, and metaphor language — from a named list of concepts. Lock the style system (grid, stroke, padding, keyline shapes) BEFORE drawing any icon, because icon-set quality is almost entirely about consistency: a pack of individually-nice icons with mismatched strokes looks broken. Then generate every icon to the system and assemble a previewable sheet. Covers icon sets, UI icons, SVG icon libraries, glyph packs, and design systems.",
   "tags": [

package/data/craftbook-templates/id/idea-office-hours/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "idea-office-hours",
   "role": "general",
+  "category": "practice",
   "name": "Idea Office Hours",
   "description": "Pressure-test a product idea with forcing questions before jumping to solutions, then capture the decision in a short design doc — a structured 'office hours' diagnostic.",
   "tags": [

package/data/craftbook-templates/id/idle-clicker-game/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "idle-clicker-game",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Idle / Incremental Game",
   "description": "Build a single-file idle or incremental clicker game such as a cookie/factory clicker with upgrades, generators, and exponential growth. Designs the resource economy — base click yield, generator costs, cost-scaling factor, and per-second production — first, then the layout, then implements a tick loop with persistent-feeling progression. Idle games are an economy problem before a UI problem: if costs and yields are not tuned the game is boring in 10 seconds or unwinnable, so the economy phase locks the exact numbers and growth curve before any rendering.",
   "tags": [

package/data/craftbook-templates/im/image-batch-edit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-batch-edit",
   "role": "general",
+  "category": "media",
   "name": "Batch Image Transform",
   "description": "Apply a consistent transform across a whole folder of images — resize, crop to a ratio, convert format, compress, watermark, or recolor — and verify every file came out correct. Scope the exact transform and a verification rule FIRST (target dimensions, format, quality, naming) so the batch is deterministic and reproducible, then process every file and prove the output count, dimensions, and format match the spec. Covers bulk image processing, resizing, format conversion, compression, watermarking, and folder-wide edits.",
   "tags": [

package/data/craftbook-templates/im/image-dedup-cluster/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-dedup-cluster",
   "role": "general",
+  "category": "media",
   "name": "Image Dedup & Cluster",
   "description": "Find and group near-duplicate images across a folder — exact dupes, resized/re-encoded copies, and visually similar shots from the same burst — using perceptual hashing or visual similarity, then report clusters with a recommended keeper per group. Lock the similarity definition and thresholds FIRST (what counts as a duplicate vs merely similar) because the whole result hinges on that line; then analyze pairwise, cluster, and produce a human-reviewable report. Covers deduplication, near-duplicate detection, perceptual hashing, image clustering, burst grouping, and library cleanup.",
   "tags": [

package/data/craftbook-templates/im/image-palette-extract/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-palette-extract",
   "role": "general",
+  "category": "design",
   "name": "Image Palette Extraction",
   "description": "Extract a usable color palette from an image or a set of images — the dominant and accent colors as hex/RGB with proportions — and emit it as design tokens (CSS variables / JSON) plus a swatch preview, so a brand or theme can be built from a reference photo. Lock FIRST how many colors, the color space and clustering method, and accessibility constraints (e.g. text/background pairs must meet a contrast ratio) because a raw dominant-color dump is rarely directly usable as a theme; then extract, name, and present the palette. Covers color extraction, palette generation, design tokens, theme-from-image, dominant colors, and brand color sampling.",
   "tags": [

package/data/craftbook-templates/im/image-seo-rename/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-seo-rename",
   "role": "general",
+  "category": "media",
   "name": "Image SEO Rename & Tag",
   "description": "Rename and tag a folder of images for SEO and findability — descriptive, hyphenated, keyword-rich filenames plus consistent metadata (title, caption, keyword tags) — driven by what each image actually depicts, while preserving a mapping back to the originals so links don't break silently. Scope FIRST the naming convention, keyword strategy, and collision/mapping rules, because bulk-renaming without a plan creates duplicate-name clashes and broken references; then process the folder and emit the rename map. Covers image SEO, filename optimization, descriptive renaming, alt/metadata tagging, and asset findability.",
   "tags": [

package/data/craftbook-templates/im/image-set-index/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-set-index",
   "role": "general",
+  "category": "media",
   "name": "Index & Describe an Image Set",
   "description": "Given a folder of images, produce a structured index that describes each one (caption, tags, notable content) in a consistent schema, then validates coverage and consistency. For cataloguing, search, or alt-text generation over an image collection.",
   "tags": [

package/data/craftbook-templates/in/inbox-triage/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "inbox-triage",
   "role": "general",
+  "category": "business",
   "name": "Inbox Triage & Reply Drafts",
   "description": "Triage a batch of incoming emails or messages into priority buckets and draft replies for the ones that need them. Locks the triage rules and bucket taxonomy FIRST (urgent / needs-reply / FYI / archive, plus the criteria for each and a reply policy), then classifies every message deterministically against those rules, then a copywriter drafts on-voice replies only for the messages flagged needs-reply. The rules-before-triage ordering is what stops a small model from inventing ad-hoc categories and gives the reviewer something to grade. Use for inbox zero, support-queue triage, email sorting, message prioritization, and auto-drafting responses.",
   "tags": [

package/data/craftbook-templates/in/incident-comms-templates/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "incident-comms-templates",
   "role": "general",
+  "category": "code-ops",
   "name": "Incident Communication Templates",
   "description": "Author a reusable set of incident communication templates: status-page posts and stakeholder update messages for each phase of an incident (Investigating, Identified, Monitoring, Resolved) across severities, with fill-in variables and a cadence guide. Scopes the audiences, phases, and tone rules FIRST (who reads each channel, the phase ladder, what may and may not be said, the variable set), then a copywriter writes the on-brand templates with bracketed placeholders, then a reviewer checks coverage, tone, and that no template over-promises or leaks blame. Scoping audiences and phases before drafting is what produces calm, honest, copy-paste-ready updates instead of ad-hoc panic posts. Use for incident comms, status page templates, customer incident updates, outage communication, and stakeholder messaging during an incident.",
   "tags": [

package/data/craftbook-templates/in/incident-postmortem/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "incident-postmortem",
   "role": "maintenance-review",
+  "category": "code-ops",
   "name": "Incident Postmortem",
   "description": "Write a blameless incident postmortem after a production outage or degradation — a structured, factual document covering the impact, a precise timeline (detection → diagnosis → mitigation → resolution), the root cause and contributing factors via a five-whys analysis, what went well and what went poorly, and concrete, owned, dated action items that prevent recurrence. A researcher assembles the verified timeline and evidence from logs/alerts/chat, a copywriter writes the blameless narrative and root-cause analysis, and a reviewer checks the timeline is accurate, the analysis reaches a true root cause, and every action item is specific and owned. Use this for outage retrospectives, severity-incident reviews, and any 'what happened and how do we prevent it' writeup.",
   "tags": [

package/data/craftbook-templates/in/insurance-inventory/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "insurance-inventory",
   "role": "general",
+  "category": "business",
   "name": "Insurance Inventory",
   "description": "Compile the inventory nobody has until the day they desperately need it: every cataloged item with its value, photo reference, and acquisition info in one document, the gaps (no photo, no value) named instead of papered over, and the total stated with its basis. Locks the completeness criteria FIRST, then compiles the full table, then writes the cover note — the quiet payoff of keeping the catalog honest. Use for insurance inventories, 'our agent wants a full inventory', documenting the collection for coverage, and preparing a collection record for a claim.",
   "tags": [

package/data/craftbook-templates/in/interactive-quiz/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "interactive-quiz",
   "role": "project-starter",
+  "category": "personal",
   "name": "Interactive Quiz Widget",
   "description": "Build a single-file interactive quiz or assessment — multiple-choice, true/false, or a scored personality quiz — that asks questions one at a time, tracks the score, gives feedback, and shows a results screen. Authors the question bank, answer keys, and scoring logic first, designs the question and results UI, then implements stateful question flow with correct scoring. Quizzes break when the score is miscounted or the results screen never appears, so the content phase locks the answer key and the score-to-result mapping before any markup.",
   "tags": [

package/data/craftbook-templates/in/investigate/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "investigate",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Investigate",
   "description": "Systematic root-cause debugging procedure. Iron Law: no fixes without investigation. Gathers symptoms, reproduces, traces, finds root cause, saves the learning.",
   "tags": [

package/data/craftbook-templates/in/investigate-root-cause/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "investigate-root-cause",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Root-Cause Investigation",
   "description": "Debug a defect or production incident down to its true root cause and document the diagnosis with evidence, instead of patching the first symptom. First reproduces the failure reliably and locks what 'understood' means (a confirmed repro, the failing assertion, the exact trigger condition), then narrows the cause by forming and testing hypotheses, bisecting, reading stack traces and logs, and tracing the data path until one hypothesis is proven, then writes a root-cause report with the evidence chain, the smallest fix, and how to prevent recurrence. Use this for debugging, root-cause analysis, investigating a bug or flaky test, diagnosing an incident, or figuring out why something breaks — it produces a proven cause backed by evidence, not a guess.",
   "tags": [

package/data/craftbook-templates/in/invitation-design/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "invitation-design",
   "role": "general",
+  "category": "personal",
   "name": "Design the Invitations",
   "description": "Produce the invitation the day deserves and get the facts beyond doubt: the date, time, venue, and RSVP instructions checked letter-for-letter against the event record — because a beautiful card with the wrong date is the classic disaster. Locks the fact checklist and the look brief FIRST, then designs the print-ready invitation, then proofs every fact against the record before anything reaches a printer. Use for party invitations, designing the invites, birthday and anniversary invitations, and 'make the invitation printable'.",
   "tags": [

package/data/craftbook-templates/in/invoice-generator/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "invoice-generator",
   "role": "general",
+  "category": "business",
   "name": "Invoice Generator",
   "description": "Generate a clean, professional, print-ready invoice from billing details — sender/recipient, line items with quantity and rate, subtotal, tax, total, invoice number, dates, and payment instructions. Scopes the required fields and the tax/total math FIRST (a wrong total is the one unforgivable invoice bug), then builds a polished single-file HTML invoice with an itemized table and correctly computed totals. Use for freelancer/contractor billing, one-off invoices, and invoice templates.",
   "tags": [

package/data/craftbook-templates/in/invoice-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "invoice-run",
   "role": "general",
+  "category": "business",
   "name": "Monthly Invoice Run",
   "description": "Run the month's invoicing in one calm pass from the office's own books: an invoice per client built from the tracked work in the ledger, numbering that continues the sequence without a skip or a repeat, due dates per each client's terms, everything recorded as sent — plus a one-page summary of what went out. Unlike a one-off invoice generator, this is the standing monthly ritual over the client roster and ledger, ending in print-ready invoices and updated books. Use for the monthly invoice run, end-of-month invoicing, 'bill the clients for this month', and closing the billing month.",
   "tags": [