@bendyline/gilde 0.1.39 → 0.1.40

package/data/craftbook-templates/te/technical-documentation/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "technical-documentation",
   "role": "general",
+  "category": "code-docs",
   "name": "Technical Documentation",
   "description": "Generate a coherent documentation set from a codebase, organized by the Diataxis model (tutorials, how-to guides, reference, explanation), with cross-links and a coverage pass.",
   "tags": [

package/data/craftbook-templates/te/test-coverage-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "test-coverage-review",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Test Coverage Review",
   "description": "Review a codebase or module's test suite for real coverage and quality, then produce a gap report and a prioritized backlog of tests to add. First scopes the units under review and locks a coverage standard distinguishing line coverage from behavioral coverage (critical paths, branches, edge cases, error handling, and regression protection), then audits the existing tests for what they actually assert and which behaviors and branches are untested or weakly tested, then writes a report ranking the highest-value missing or low-quality tests with a concrete description of each. Use this for a test coverage review, finding test gaps, auditing test quality, deciding what to test next, or assessing whether a module is well-tested — it distinguishes meaningful behavioral coverage from a green coverage number and returns a prioritized testing backlog rather than 'add more tests'.",
   "tags": [

package/data/craftbook-templates/te/test-suite-backfill/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "test-suite-backfill",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Test Suite Backfill",
   "description": "Add a meaningful test suite to existing untested (or under-tested) code, prioritizing the highest-risk behavior and edge cases over vanity coverage. Scopes coverage FIRST — the public surface, the critical paths, the edge/error cases, and the target the tests must hit — then writes characterization and edge-case tests that pin real behavior and would catch real regressions. Covers test prioritization, characterization tests, edge/error-case coverage, arrange-act-assert structure, and coverage-that-matters over line-count chasing.",
   "tags": [

package/data/craftbook-templates/th/thank-you-batch/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "thank-you-batch",
   "role": "general",
+  "category": "personal",
   "name": "Thank-You Note Batch",
   "description": "Clear the owed-thanks list with notes that sound like you: read who is owed and for what from the correspondence roster, draft one note per person that names the actual gift or kindness — no template smell — then log every note so nobody who mattered goes unanswered. Locks the household voice and the coverage rules FIRST, then drafts the batch, then records it in the roster with a short run summary. Use for thank-you notes, clearing the owed-thanks list, 'we owe thank yous from the party', and post-holiday gratitude sweeps.",
   "tags": [

package/data/craftbook-templates/th/thank-you-sweep/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "thank-you-sweep",
   "role": "general",
+  "category": "personal",
   "name": "Post-Event Thank-You Sweep",
   "description": "Close the event the way it deserves: every gift-giver and every helper matched to a personal note, drafted in one sitting and tracked to sent — so 'the thank-yous actually go out' becomes a checklist instead of a lingering guilt. Locks the coverage rule FIRST — every giver, every helper, one personal detail each — then drafts the batch, then records each note to sent in the event's books. Use for post-event thank-yous, thanking the helpers after a party, gift thank-you notes, and 'the party's done, sweep the thank yous'.",
   "tags": [

package/data/craftbook-templates/th/threat-model/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "threat-model",
   "role": "general",
+  "category": "code-review",
   "name": "Lightweight Threat Model",
   "description": "Produce a lightweight threat model for a feature or system using a structured method (STRIDE over a simple data-flow diagram) and output a prioritized mitigation plan. First scopes the system by drawing its data-flow — actors, processes, data stores, and trust boundaries — and locks what is in scope, then enumerates threats per element using STRIDE (spoofing, tampering, repudiation, info-disclosure, denial-of-service, elevation-of-privilege) and rates each by likelihood and impact, then writes a threat-model report mapping each credible threat to a concrete mitigation and an owner. Use this for a threat model, security design review, STRIDE analysis, attack-surface mapping, or thinking through what could go wrong before building a feature — it yields a structured, prioritized set of threats and mitigations rather than an ad-hoc list of worries.",
   "tags": [

package/data/craftbook-templates/th/thumbnail-generator/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "thumbnail-generator",
   "role": "general",
+  "category": "media",
   "name": "Thumbnail Generator",
   "description": "Derive a consistent set of thumbnails or responsive size-variants from a folder of source images — square crops for grids, srcset widths for the web, smart-cropped to keep the subject centered — and emit them with predictable names. Scope the target sizes, crop strategy, and naming convention FIRST so the output plugs straight into a gallery or srcset, then build every variant and confirm the matrix is complete. Covers thumbnails, responsive images, srcset, image variants, gallery tiles, and preview generation.",
   "tags": [

package/data/craftbook-templates/ti/tileset-batch/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "tileset-batch",
   "role": "general",
+  "category": "media",
   "name": "Tileset Batch",
   "description": "Produce a style-locked batch of tiles and account for every one: named to the convention, sized to spec, generated against the library's style anchor, and appended to the manifest with tags — an asset library a game engine can trust, not a folder of maybes. Locks the tile list and the naming convention FIRST, then generates the batch in the house style, then writes the manifest records and the batch summary. Use for tile batches, 'we need forest tiles', growing a game's asset library, style-consistent tilesets, and keeping the asset manifest honest.",
   "tags": [

package/data/craftbook-templates/to/tone-rewrite/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "tone-rewrite",
   "role": "general",
+  "category": "marketing",
   "name": "Brand Tone Rewrite",
   "description": "Re-voice existing content to a specific brand tone while preserving every fact and the original structure: it first codifies the target voice into a concrete style guide — adjectives, do's and don'ts, banned and preferred words, sentence-length feel, point of view — then rewrites the content line by line to that voice without changing what it says. Covers tone of voice rewrite, rebranding copy, voice and tone, brand voice, re-voice content, and style adaptation. Codifying the voice into checkable rules before rewriting is the point: a small model that has explicit do/don't rules applies the tone consistently, instead of a vague 'make it friendlier' that drifts paragraph to paragraph.",
   "tags": [

package/data/craftbook-templates/to/topic-explainer/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "topic-explainer",
   "role": "general",
+  "category": "writing",
   "name": "Topic Explainer",
   "description": "Explain a complex topic clearly for a defined audience: a planner pins the audience, their assumed prior knowledge, and the concepts that must be taught, a researcher gathers accurate facts and good analogies with sources, and a copywriter writes a progressively-structured explainer that builds from fundamentals to the full picture. The ordering matters because an explainer written without a fixed audience either condescends or loses people, and one written without a concept map skips a prerequisite; locking the audience and a concept dependency order first guarantees the explanation actually lands. Use this for 'explain X like I'm a beginner/expert', concept explainers, how-it-works guides, ELI5/ELI-expert pieces, and turning a hard topic into an accessible read.",
   "tags": [

package/data/craftbook-templates/tr/transcribe-and-shownotes/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "transcribe-and-shownotes",
   "role": "general",
+  "category": "media",
   "name": "Transcript to Shownotes",
   "description": "Take a finished recording from raw transcript to publishable shownotes: a clean transcript on file, timestamped chapters, a summary listeners actually read, and the links mentioned — the per-episode ritual that turns audio into an archive. Locks the shownotes checklist FIRST (chapters timestamped, every link captured, names spelled right), then gets the transcript on file, then writes the shownotes from it. Use for episode shownotes, transcribing an episode, chapter timestamps, and 'turn this recording into shownotes'.",
   "tags": [

package/data/craftbook-templates/tr/transcribe-audio/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "transcribe-audio",
   "role": "general",
+  "category": "media",
   "name": "Transcribe Audio or Video",
   "description": "Convert an audio or video recording into an accurate, readable transcript using speech-to-text, with speaker labels and timestamps. Scopes the output format, speaker-labeling, and timestamp granularity FIRST so the transcript is usable downstream (search, subtitles, minutes), then transcribes the full recording end-to-end, then verifies coverage against the recording's duration and checks for dropped segments. The scope-first ordering matters because deciding timestamp cadence and speaker handling up front is what separates a clean, searchable transcript from a wall of unattributed text.",
   "tags": [

package/data/craftbook-templates/tr/transcribe-index/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "transcribe-index",
   "role": "general",
+  "category": "media",
   "name": "Transcribe and Index a Tape",
   "description": "Give one tape the ten-second-findability treatment: transcript on file, then every moment worth finding indexed with its timecode and people tags — so 'the clip of Opa's 80th toast' becomes a query, not an afternoon of scrubbing. Locks the tape's metadata and the indexing rules FIRST (timecoded moments, people tags drawn from the family roster, searchable descriptions), then lands the transcript, then the clip records, then a tape summary with the highlights. Use for indexing a digitized tape, making home videos searchable, cataloging family footage, and 'what is on this tape'.",
   "tags": [

package/data/craftbook-templates/tr/translate-content/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "translate-content",
   "role": "general",
+  "category": "writing",
   "name": "Translate Content",
   "description": "Translate the project's new and changed content into the designated language as sidecar files under translations/<language>/, mirroring the source structure and never modifying originals. Incremental: unchanged files are skipped, and each run ends with a short run note listing what was covered. Suited to the Night Shift so the translated shadow never falls far behind.",
   "tags": [

package/data/craftbook-templates/ty/type-safety-pass/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "type-safety-pass",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Type-Safety Pass",
   "description": "Tighten the types of a module — eliminate `any`/implicit-any, add precise annotations, narrow unions, and make illegal states unrepresentable — without changing runtime behavior. Audits FIRST to inventory every loose type, unsafe cast, and missing annotation, then replaces them with precise types, then a reviewer confirms the type-checker is clean under strict settings and behavior is unchanged. Covers killing `any`, strict null checks, discriminated unions, generics, type narrowing, removing unsafe casts, and compile-clean-under-strict verification.",
   "tags": [

package/data/craftbook-templates/ve/version-bump/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "version-bump",
   "role": "general",
+  "category": "code-release",
   "name": "Version Bump",
   "description": "Perform a coordinated, semver-correct version bump across a project — deciding MAJOR/MINOR/PATCH from the actual change set, then updating every place the version is stamped in lockstep (package manifest(s), version constant, lockfile, badges, docs) plus the changelog header, so nothing drifts out of sync. A planner determines the correct semver level and enumerates every file that carries the version, a developer applies the bump everywhere consistently, and a reviewer verifies no location was missed and the new version is internally consistent. Use this when 'bumping the version', preparing a tag, or releasing a new package version where a half-applied bump (manifest says 2.0.0 but the constant says 1.9.0) is a classic ship bug.",
   "tags": [

package/data/craftbook-templates/vi/video-storyboard/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "video-storyboard",
   "role": "general",
+  "category": "media",
   "name": "Video Storyboard from a Script",
   "description": "Turn a video script into a shot-by-shot storyboard — each scene broken into shots with a framing sketch/description, camera direction, on-screen action, the matching script line, and timing — so a shoot or animation has a clear visual plan. Scopes the script into scenes and shot list FIRST, then designs each storyboard panel visually. The script-scope-then-storyboard ordering ensures every shot maps to a real script beat and the timing adds up to the script's runtime, instead of pretty panels that drift from the words.",
   "tags": [

package/data/craftbook-templates/vi/visit-prep/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "visit-prep",
   "role": "general",
+  "category": "personal",
   "name": "Care Visit Prep",
   "description": "Prepare a one-page brief for a medical or care appointment from the project's care record: compile everything logged since the last visit, the current medication list with doses, the changes and symptoms worth raising, and a prioritized question list — so the ten minutes in the room get spent on what matters. Locks the target appointment and the brief's sections FIRST, then compiles from the record, then writes the brief. Use for doctor visit prep, specialist appointments, care-team check-ins, and 'what do we need to tell the doctor'.",
   "tags": [

package/data/craftbook-templates/vo/voiceover-script/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "voiceover-script",
   "role": "general",
+  "category": "media",
   "name": "Voiceover / TTS Script",
   "description": "Write a voiceover script tuned for spoken delivery — by a human VO artist or a text-to-speech engine — for a video, ad, explainer, or narration, with pacing, pronunciation, and timing baked in. Briefs the audience, runtime, and voice FIRST, then drafts a performance-ready script with scene/segment breaks, [pause] and emphasis cues, phonetic spellings for tricky words, and a per-segment word count that fits the target seconds. The brief-then-draft ordering ensures the script is written for the EAR and the clock, not the page — short sentences, read-aloud rhythm, and a runtime that actually fits.",
   "tags": [

package/data/craftbook-templates/we/weak-spot-drill/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "weak-spot-drill",
   "role": "general",
+  "category": "personal",
   "name": "Weak-Spot Drill",
   "description": "Stop practicing what you already know: read the review record, name the actual weak spots with the numbers as evidence, and build a short targeted drill plus the follow-up schedule that closes them. Locks the ranked weak list FIRST — from the deck's boxes and miss counts, not vibes — then builds the drill page around only that material, then writes the plan that says when the spot counts as closed. Use for targeted practice, 'I keep missing the same ones', closing weak spots, drilling trouble topics, and study sessions that skip what already sticks.",
   "tags": [

package/data/craftbook-templates/we/web-app-crud/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "web-app-crud",
   "role": "project-starter",
+  "category": "code-build",
   "name": "CRUD Web App",
   "description": "Build a small single-file CRUD web app — a todo list, notes, contacts, or inventory manager — with create, read, update, and delete plus localStorage persistence so data survives a reload. Locks the data model and the four operations first, then a clean list-plus-form UI design, then builds vanilla JS with real state and persistence. CRUD apps fail when delete or edit silently does nothing or data vanishes on reload, so the model phase pins every operation's behavior before coding, the ordering that gets a small model to a genuinely working app.",
   "tags": [

package/data/craftbook-templates/we/web-component/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "web-component",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Reusable Web Component",
   "description": "Build a reusable custom element as a standards-based Web Component — a rating widget, toggle, accordion, modal, or color-picker — using the Custom Elements API and Shadow DOM with encapsulated styles, attributes, properties, and custom events. Designs the component's public API (tag name, observed attributes, properties, events, slots) first, then implements the class with a demo page proving it works. Components fail when the API is inconsistent or styles leak, so the api-design phase locks the contract before any code, the ordering that yields a genuinely reusable element rather than a one-off.",
   "tags": [

package/data/craftbook-templates/we/webhook-handler/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "webhook-handler",
   "role": "project-starter",
+  "category": "code-data",
   "name": "Inbound Webhook Handler",
   "description": "Build a handler that receives inbound webhook events, verifies their authenticity, parses the payload, and dispatches by event type — idempotently and resiliently. Locks the webhook contract FIRST — the event types, payload shapes, signature-verification scheme, idempotency key, and required 2xx-fast-ack behavior — then implements verification + routing + handlers, then tests valid/invalid signatures, each event type, replays, and malformed payloads. Covers HMAC signature verification, payload parsing, event-type dispatch, idempotency/dedupe, fast 2xx acknowledgement, and retry-safe processing.",
   "tags": [

package/data/craftbook-templates/we/week-plan/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "week-plan",
   "role": "general",
+  "category": "business",
   "name": "Plan the Week",
   "description": "Start Monday with the week already shaped: every meeting seen, the ones needing prep flagged, the conflicts and overload called out, and real focus blocks defended — a plan you made once, on purpose, instead of a calendar you react to all week. Locks the week's events and the planning rules FIRST, then shapes the days, then writes the plan with its prep queue. Use for weekly planning, monday morning planning, 'what does my week look like', calendar reviews, and defending focus time.",
   "tags": [

package/data/craftbook-templates/we/weekly-menu-plan/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "weekly-menu-plan",
   "role": "general",
+  "category": "personal",
   "name": "Plan the Week's Dinners",
   "description": "Turn the pantry's real state into a planned week of dinners and one grocery list: check what is stocked, low, and out, plan seven dinners that use what is on hand and fit the household's tastes and schedule, write the menu onto the week, and produce a grocery list that covers the gaps. Locks the household constraints and the pantry picture FIRST, then plans the menu, then writes the list — so the weekly food question is answered once, on purpose, instead of nightly at 5pm. Use for weekly meal planning, menu planning, grocery list making, and 'what are we eating this week'.",
   "tags": [

package/data/craftbook-templates/we/weekly-pipeline-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "weekly-pipeline-review",
   "role": "maintenance-review",
+  "category": "business",
   "name": "Weekly Pipeline Review",
   "description": "The weekly walk of a job-search pipeline — a grounded snapshot of every application (what moved in the last seven days, what went stale, which follow-ups are due), then a review that chases or consciously parks every stalled item and commits to exactly three concrete priorities for next week. Built for the Job Hunt project's weekly cadence; also runs on demand whenever the pipeline feels foggy.",
   "tags": [

package/data/craftbook-templates/we/weekly-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "weekly-review",
   "role": "maintenance-review",
+  "category": "business",
   "name": "Personal / Team Weekly Review",
   "description": "Assemble a reflective weekly review that pulls the week's done-list, metrics, and open loops into a structured retrospective with wins, misses, lessons, and next-week priorities. Scopes the review template and the inputs FIRST (the GTD-style sections, what data feeds each, the carry-over rule for unfinished items), then a copywriter writes the honest, concise review against that template. The scope-first ordering keeps the review consistent week over week and ensures open loops are carried forward rather than forgotten. Use for weekly reviews, personal retrospectives, GTD weekly review, end-of-week wrap-ups, and team retros.",
   "tags": [

package/data/craftbook-templates/we/weekly-walkthrough/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "weekly-walkthrough",
   "role": "general",
+  "category": "personal",
   "name": "Weekly Garden Walkthrough",
   "description": "Walk the beds once a week with a plan instead of a vague worry: what each bed needs this week derived from the plantings and the season, the walkthrough ordered so it actually gets done, and the observations and harvests logged so the almanac accrues. Locks the week's due list FIRST, then plans the route, then logs what happened and seeds next week. Use for weekly garden walkthroughs, 'what does the garden need this week', weekend garden sessions, and garden check-ins.",
   "tags": [

package/data/craftbook-templates/wh/whitepaper/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "whitepaper",
   "role": "general",
+  "category": "writing",
   "name": "Whitepaper",
   "description": "Author a long-form, authoritative whitepaper that makes a researched argument — a technical position paper, industry analysis, or thought-leadership piece with citations. Does the RESEARCH first to ground every claim, then locks a logical section outline and thesis, then writes the full long-form document with an abstract, numbered sections, evidence, figures, and a references list. Use when the deliverable must be credible, sourced, and substantial rather than a quick blog post.",
   "tags": [

package/data/craftbook-templates/ye/year-in-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "year-in-review",
   "role": "general",
+  "category": "media",
   "name": "Year in Review",
   "description": "Build the year-in-review that makes someone cry the good way: every month represented or its gap acknowledged, the people balanced, the closing image chosen on purpose — the annual ritual the whole photo archive exists for. Locks the year and the coverage criteria FIRST, then curates the selection month by month, then narrates the year's thread. Use for year-in-review albums, annual photo retrospectives, 'the year in photos', December album rituals, and closing out the year's archive.",
   "tags": [

package/data/craftbook-templates/yo/youtube-chapters-seo/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "youtube-chapters-seo",
   "role": "general",
+  "category": "marketing",
   "name": "YouTube Chapters & SEO Metadata",
   "description": "Turn a video (or its transcript) into a complete, paste-ready YouTube publishing kit — SEO title options, an optimized description with timestamped chapters, tags/keywords, and thumbnail text ideas — so an upload ranks and is navigable. Scopes the target keyword and metadata limits FIRST, analyzes the transcript for chapter boundaries, then writes the SEO-optimized metadata kit. Doing keyword research and pulling real chapter timestamps before writing is what makes the description both discoverable and accurate, instead of clickbait that doesn't match the video.",
   "tags": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bendyline/gilde",
-  "version": "0.1.39",
+  "version": "0.1.40",
   "description": "The gilde catalog: model manifests, toolsets, craftbooks, roles, and project types for gezel.",
   "license": "MIT",
   "private": false,

package/schemas/craftbook-template-identity.schema.json

@@ -92,6 +92,27 @@
         "general"
       ]
     },
+    "category": {
+      "type": "string",
+      "enum": [
+        "code-build",
+        "code-quality",
+        "code-review",
+        "code-data",
+        "code-release",
+        "code-ops",
+        "code-docs",
+        "writing",
+        "media",
+        "design",
+        "marketing",
+        "research",
+        "business",
+        "personal",
+        "practice",
+        "other"
+      ]
+    },
     "workflow": {
       "type": "string"
     }

package/schemas/craftbook-test.schema.json

@@ -4823,6 +4823,9 @@
                   "project.github.synced",
                   "project.review.requested",
                   "project.review.settled",
+                  "project.diffpack.sealed",
+                  "project.diffpack.applied",
+                  "project.diffpack.dismissed",
                   "project.connector.bound",
                   "project.connector.unbound",
                   "project.connector.synced",
@@ -4852,6 +4855,13 @@
                   "boekwachter.changed",
                   "keurmeester.changed",
                   "gilde.updated",
+                  "ai-app.installed",
+                  "ai-app.removed",
+                  "ai-app.enabled",
+                  "ai-app.disabled",
+                  "ai-app.applied",
+                  "app-serve.started",
+                  "app-serve.stopped",
                   "v1.chat.completion",
                   "keurmeester.intervention",
                   "keurmeester.digest.generated",