@bendyline/gilde 0.1.39 → 0.1.40

package/data/craftbook-templates/it/item-intake/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "item-intake",
   "role": "general",
+  "category": "personal",
   "name": "Catalog an Item",
   "description": "Take new arrivals from shoebox to catalog: identify each item from its photo notes, record it with condition and an honest value basis, and flag what needs a better photo or an expert eye — uncertain identification stays uncertain in the record instead of becoming confident fiction. Locks the record fields and the honesty rule FIRST, then catalogs each item, then reports confidence and follow-ups. Use for cataloging new items, collection intake, 'catalog these arrivals', and adding finds to the collection.",
   "tags": [

package/data/craftbook-templates/ju/juice-pass/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "juice-pass",
   "role": "general",
+  "category": "code-build",
   "name": "Juice Pass",
   "description": "Make the game feel alive without breaking it: feedback on every player action — hit-flash, screenshake, sound hooks, particles, score pops — added with restraint and verified playable after every change. Locks the juice checklist FIRST — every player action gets visible feedback, effects stay tasteful, nothing regresses — then edits the game in place, re-checking that it still runs and still ends. Use for 'the game feels dead', game feel passes, adding screenshake and particles, polishing an arcade game, and making hits feel like hits.",
   "tags": [

package/data/craftbook-templates/kn/knowledge-base-article/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "knowledge-base-article",
   "role": "general",
+  "category": "writing",
   "name": "Knowledge Base Article",
   "description": "Write a support knowledge-base article that lets a user solve their problem without contacting support: it first scopes the exact user problem, the search terms they would use, prerequisites, and the success outcome, then writes a task-oriented article with a clear title, a short overview, numbered steps with expected results, screenshots/placeholders where needed, and a troubleshooting section, then a review pass verifies accuracy and self-service completeness. Covers help center article, support documentation, how-to article, KB article, self-service docs, and product help. Scoping the precise problem and search terms before writing is the point: a small model that pins the one job-to-be-done writes a findable, followable article instead of a vague overview that leaves the user still stuck.",
   "tags": [

package/data/craftbook-templates/kp/kpi-scorecard/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "kpi-scorecard",
   "role": "general",
+  "category": "business",
   "name": "KPI Scorecard Page",
   "description": "Build a single-page KPI scorecard that rolls a dataset up into the handful of numbers a team tracks, each shown with its current value, target, and period-over-period change. Defines the KPIs and their exact formulas and targets FIRST (so a number is never ambiguous), then computes the rollups, then builds a clean self-contained HTML scorecard with KPI tiles, deltas, and a tiny trend sparkline each. Use this for a KPI dashboard, a metrics scorecard, an executive summary page, a North Star metrics view, or rolling raw data into headline numbers.",
   "tags": [

package/data/craftbook-templates/la/landing-copy/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "landing-copy",
   "role": "general",
+  "category": "marketing",
   "name": "Landing Page Copy",
   "description": "Write conversion-focused copy for a single landing page: it first locks the offer, the one primary audience, the single desired action, and the core promise, then drafts a full message hierarchy — hero headline and subhead, value props, social proof, objection handling, and one repeated CTA — then edits ruthlessly for clarity, specificity, and persuasive flow. Covers landing page copy, sales copy, conversion copywriting, hero copy, CTA copy, and value proposition writing. Offer-first ordering matters: a small model that nails the single offer and one CTA before writing avoids the diluted page that lists ten features, hedges the promise, and offers three competing actions.",
   "tags": [

package/data/craftbook-templates/la/landing-page/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "landing-page",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Landing Page",
   "description": "Build a single high-conversion landing page for one offer — a product, signup, waitlist, or download — with a focused hero, benefits, social proof, and one primary call to action above and below the fold. Locks the offer, audience, and single CTA first, then a conversion-oriented visual design, then the persuasive copy, then builds responsive HTML with real CSS. The scope-then-design-then-copy ordering keeps the page ruthlessly focused on one conversion goal instead of becoming a sprawling site.",
   "tags": [

package/data/craftbook-templates/le/lead-enrichment/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "lead-enrichment",
   "role": "general",
+  "category": "marketing",
   "name": "Enrich a Leads List",
   "description": "Take a raw leads or contacts list and enrich each row with derived and looked-up attributes — company domain, industry, size band, role seniority, normalized location, and a quality/score flag — into a clean CRM-ready file. Scopes the enrichment fields, their sources, and the dedup/normalization rules FIRST, then enriches each lead row-by-row, then verifies coverage, that nothing was fabricated when a source had no data, and that duplicates are merged. Defining 'what each field means and where it comes from' before enriching is what stops a small model from inventing plausible-but-false company data.",
   "tags": [

package/data/craftbook-templates/li/library-package/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "library-package",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Reusable Library Package",
   "description": "Build a reusable library/SDK with a clean public API surface, sensible defaults, and published documentation. Designs the public API FIRST — exported functions/classes, signatures, types, error contract, and what stays internal — because a library's API is a long-lived promise, then implements it, then writes user-facing docs with installation, quickstart, and a worked example per public function. Covers public-vs-private surface, function signatures, JSDoc/typedoc, README, semantic versioning posture, and usage examples.",
   "tags": [

package/data/craftbook-templates/li/literature-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "literature-review",
   "role": "general",
+  "category": "research",
   "name": "Literature Review",
   "description": "Survey the existing literature on a topic and synthesize it into a structured review: a planner sets the scope, inclusion criteria, and the themes to organize around, then a researcher gathers and characterizes each source (method, finding, quality), then a copywriter synthesizes them thematically rather than source-by-source, surfacing consensus, disagreement, and gaps. The ordering matters because a review written without inclusion criteria becomes an arbitrary pile, and one written source-by-source reads like a list of summaries instead of a synthesis; locking themes and a source matrix first forces the comparative analysis that makes a real lit review. Use this for academic-style literature surveys, state-of-the-art reviews, 'what does the research say' questions, and synthesizing a body of papers or articles.",
   "tags": [

package/data/craftbook-templates/li/live-browser-qa/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "live-browser-qa",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Live Browser QA Pass",
   "description": "Run a hands-on quality-assurance pass on a running web app or page by actually exercising it in a browser, then emit a defect report with reproduction steps and severity. First derives a test plan and acceptance criteria from the app's intended behavior (happy paths, edge cases, error states, responsive/console health), then drives the UI step-by-step clicking and typing through each flow while watching the console and network for errors, then writes a bug report where every defect has numbered repro steps, expected vs actual, and severity. Use this for QA, manual testing, smoke testing, exploratory testing, click-testing a build, or verifying a feature works in the real browser before shipping — it finds broken flows, console errors, and visual breakage that unit tests miss.",
   "tags": [

package/data/craftbook-templates/lo/localize-content/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "localize-content",
   "role": "general",
+  "category": "writing",
   "name": "Localize Content",
   "description": "Localize and translate content into a target language and locale with cultural adaptation, not just word-for-word translation: it first scopes the target locale, glossary of do-not-translate and must-translate-consistently terms, formatting conventions (dates, currency, units), and tone register, then translates preserving meaning and structure, then a native-level review pass checks fluency, terminology consistency, and cultural fit. Covers translation, localization, i18n content, multilingual copy, translate to Spanish/French/German, and locale adaptation. Scoping the glossary and conventions before translating is the point: a small model that locks terminology and date/currency rules avoids inconsistent term translations and locale-wrong formatting that mark content as machine-translated.",
   "tags": [

package/data/craftbook-templates/lo/logo-set/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "logo-set",
   "role": "general",
+  "category": "design",
   "name": "Logo & Variant Set",
   "description": "Generate a coherent logo and the full set of variants a real brand needs — primary mark, horizontal lockup, stacked lockup, icon-only/favicon, plus light-on-dark and monochrome versions — from a written brief. Lock the brief (concept, geometry, palette, typography, do/don'ts) BEFORE generating pixels so every variant shares one visual DNA instead of looking like five unrelated logos; then assemble them into a delivered folder with a contact sheet. Covers logo design, brand mark, wordmark, logo variations, and brand-asset packs.",
   "tags": [

package/data/craftbook-templates/ma/market-scan/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "market-scan",
   "role": "general",
+  "category": "research",
   "name": "Market & Landscape Scan",
   "description": "Survey a market or landscape and write a scan that sizes it, maps the players, and surfaces trends: a planner scopes the market boundary and the lenses (size, segments, players, trends, drivers, risks), a researcher gathers sized figures and landscape facts with sources, and a copywriter writes a structured landscape report. The ordering matters because a scan without a defined boundary mixes adjacent markets and inflates numbers, and one without locked lenses skips the dimensions a decision-maker needs; fixing boundary and lenses first keeps the scan focused and comparable. Use this for market landscape scans, industry overviews, TAM/segmentation reads, trend analyses, and 'give me the lay of the land in X' requests.",
   "tags": [

package/data/craftbook-templates/me/meeting-minutes/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "meeting-minutes",
   "role": "general",
+  "category": "business",
   "name": "Meeting Minutes & Actions",
   "description": "Turn a meeting transcript, recording notes, or rough scratch into clean, distributable meeting minutes — attendees, agenda topics discussed, decisions made, and (most importantly) action items with owners and due dates. Scopes the minutes structure and what counts as a decision vs an action FIRST, then writes accurate, neutral minutes where every decision is recorded and every action has an owner and a date — the action table is the part people actually use. Use for board/team meeting minutes, project status meetings, and decision logs.",
   "tags": [

package/data/craftbook-templates/me/meeting-notes-to-actions/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "meeting-notes-to-actions",
   "role": "general",
+  "category": "business",
   "name": "Meeting Notes to Action Items",
   "description": "Convert raw meeting notes or a transcript into a clean, assigned action-item list with owners, due dates, and the decisions that drove them. Extracts the actions and decisions FIRST (every commitment, ask, and decision lifted verbatim-ish into a structured list with source quotes), then a planner assigns owners and due dates and prioritizes — separating extraction from assignment so nothing said in the meeting is lost before triage. The extract-then-assign ordering is what stops a small model from silently dropping commitments or inventing owners. Use for meeting follow-ups, action-item extraction, turning transcripts into to-dos, decision logs, and post-meeting recaps.",
   "tags": [

package/data/craftbook-templates/me/meeting-prep-brief/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "meeting-prep-brief",
   "role": "general",
+  "category": "business",
   "name": "Meeting Prep Brief",
   "description": "Walk into the meeting already warm: who's in the room, what was promised last time, what you want out of this one, and the two questions worth asking — one page, read in the elevator. Locks the target meeting and the one-page criteria FIRST, then compiles from the calendar and the prior notes, so every claim in the brief traces to something real instead of memory. Use for meeting prep, 'prep me for the meeting', pre-meeting briefs, vendor and client syncs, and walking in warm.",
   "tags": [

package/data/craftbook-templates/me/meeting-summary-audio/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "meeting-summary-audio",
   "role": "general",
+  "category": "business",
   "name": "Meeting Recording to Minutes & Actions",
   "description": "Turn a meeting recording into structured minutes plus a clear action-item list — who agreed to do what by when — derived from the audio. Transcribes the recording FIRST (with speaker labels so attribution is possible), then summarizes into decisions, discussion, and assigned action items with owners and due dates. The transcribe-then-summarize ordering is essential: you cannot reliably attribute decisions and owners without first knowing who said what, and minutes without owners are useless.",
   "tags": [

package/data/craftbook-templates/me/memory-prompt-session/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "memory-prompt-session",
   "role": "general",
+  "category": "writing",
   "name": "Memory Session",
   "description": "Run one guided memory session and bank it properly: pick the theme the timeline is hungriest for, follow the thread of feeling through the recorded conversation, and file the session with the follow-up questions that keep the next one alive. Locks the theme and question set FIRST, then captures the session in the teller's own words, then files it in the store with the threads to pull next time. Use for memory sessions, filing an interview with a parent or grandparent, memoir capture, and 'what should I ask next time'.",
   "tags": [

package/data/craftbook-templates/me/message-queue-consumer/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "message-queue-consumer",
   "role": "project-starter",
+  "category": "code-data",
   "name": "Message Queue Consumer / Worker",
   "description": "Build a queue consumer/worker that pulls messages off a queue, processes them reliably, and handles failures with retries and a dead-letter path — at-least-once delivery done right. Scopes the messaging contract FIRST — the message schema, ack/nack semantics, idempotency key, retry/backoff policy, dead-letter rules, and concurrency — then implements the consumer loop with ack-after-success and DLQ routing, then tests success, retry, poison-message, and duplicate-delivery handling. Covers queue consumers, at-least-once vs at-most-once, ack/nack, idempotent processing, retry with backoff, dead-letter queues, and poison-message isolation.",
   "tags": [

package/data/craftbook-templates/mi/micro-game-jam/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "micro-game-jam",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Micro Game Jam",
   "description": "Build a tiny, complete, themed micro-game from a one-word or one-line prompt — a 60-second arcade or one-mechanic toy that fully fits in a single HTML file with a clear goal and a win/lose. Interprets the theme into one tight mechanic and a scope you can actually finish first, then builds the whole game in one pass. The jam discipline is ruthless scope: pick ONE mechanic that expresses the theme, lock a tiny acceptance bar, and ship it playable rather than sprawling — the ordering that gets a small model to a finished game instead of an unfinished engine.",
   "tags": [

package/data/craftbook-templates/mo/mock-interview/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "mock-interview",
   "role": "general",
+  "category": "business",
   "name": "Mock Interview",
   "description": "A realistic practice interview run live with the candidate — planned questions calibrated to the target role and round, a real-time interview with pressure follow-ups, and a kind, specific debrief: strengths in the candidate's own words, fixes with sketched stronger answers, one drill, and an honest readiness read. The debrief is the deliverable. Use before any real interview round.",
   "tags": [

package/data/craftbook-templates/mo/mod-scaffold/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "mod-scaffold",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Scaffold a Mod",
   "description": "Start the mod right: a correctly-shaped Minecraft datapack — pack.mcmeta carrying the right format number for the target game version, namespaced folders laid out properly, and one working example of the mod's core idea — plus install steps a twelve-year-old can follow. Locks the idea and the version's structure rules FIRST, then scaffolds the tree, then writes the README. Use for starting a datapack, scaffolding a mod, 'my kid wants a mod that…', datapack setup, and first-mod projects.",
   "tags": [

package/data/craftbook-templates/mo/monitor-and-alert/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "monitor-and-alert",
   "role": "general",
+  "category": "code-ops",
   "name": "Watch a Page or API and Alert",
   "description": "Build a watcher that polls a web page or API endpoint on a schedule, detects a meaningful change or threshold breach, and fires an alert (and only alerts on real changes, not noise). Scopes the watched target, the exact change/threshold condition, and the dedup/cooldown policy FIRST, then builds the poll-diff-notify loop with persisted state, then tests it against simulated change and no-change inputs so it neither misses a real change nor spams on every poll. Condition-and-cooldown-before-build is the wisdom that separates a useful monitor from an alert-fatigue generator.",
   "tags": [

package/data/craftbook-templates/mo/month-close/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "month-close",
   "role": "general",
+  "category": "business",
   "name": "Close the Month",
   "description": "Close out a month of household spending against the project's ledger: sweep the month's entries for category strays and surprises, compute the in/out/net totals and category breakdown, compare against the prior month, and write a short honest month summary with one concrete action for next month. Locks the target month and the reconciliation checks FIRST, then reconciles the entries, then writes the summary — so the close is a repeatable ritual with the same shape every month, not an ad-hoc glance at the numbers. Use for monthly budget close, month-end money review, 'how did we do this month', and household spending retrospectives.",
   "tags": [

package/data/craftbook-templates/mo/monthly-recording-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "monthly-recording-review",
   "role": "maintenance-review",
+  "category": "personal",
   "name": "Monthly Recording Review",
   "description": "Sit with the month's recordings the way a teacher would: compare each against last month's marks, hear the progress your own ears stopped noticing, and pick next month's one focus — proof over impression, once a month. Locks the review criteria FIRST (every recording assessed, deltas versus last month, exactly one focus), then assesses each recording with evidence, then writes the month's review. Use for monthly practice reviews, listening back to recordings, progress checks, and 'how did this month go'.",
   "tags": [

package/data/craftbook-templates/mo/moodboard/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "moodboard",
   "role": "general",
+  "category": "design",
   "name": "Visual Moodboard",
   "description": "Compose a visual moodboard that captures a direction — palette, textures, type vibe, imagery, and reference tiles — from a written brief, so a team can align on a look before any production work begins. Lock the brief and the explicit dimensions of the mood (e.g. 'warm/editorial/handmade' vs 'cool/technical/precise') FIRST, then assemble a coherent grid of generated or sourced tiles plus a swatch strip and keyword callouts. Covers moodboards, style boards, visual direction, design inspiration, brand mood, and look-and-feel exploration.",
   "tags": [

package/data/craftbook-templates/mo/morning-brief/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "morning-brief",
   "role": "general",
+  "category": "research",
   "name": "Morning Topic Brief",
   "description": "Be informed without the doomscroll: this morning's items per watched topic, each with its source named, rumor separated from reporting, and yesterday's noise skipped — five minutes that replace an hour of feeds. Locks the brief rules FIRST, then gathers from the feeds, then writes the dated brief into the archive next to the previous ones. Use for morning briefs, daily topic digests, 'what happened overnight', news catch-ups on watched topics, and staying informed without the scroll.",
   "tags": [

package/data/craftbook-templates/mo/morning-report/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "morning-report",
   "role": "general",
+  "category": "personal",
   "name": "Morning House Report",
   "description": "The house says good morning properly: every zone's state read through the device tools, anything unusual surfaced first with one suggested action apiece, and the boring rest compressed to a line or two — glanceable before the first coffee. Locks the report criteria FIRST (every zone covered, anomalies before normals, a suggested action per oddity, short enough to read standing up), then polls the house, then writes the report — so the one morning the garage door stayed open all night is the morning it gets noticed. Use for morning house checks, daily home status, 'anything wrong with the house', overnight anomaly sweeps, and a glanceable device roundup.",
   "tags": [

package/data/craftbook-templates/mu/music-metadata-tag/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "music-metadata-tag",
   "role": "general",
+  "category": "media",
   "name": "Music Library Metadata Tagging",
   "description": "Tag and organize a folder of audio files with consistent, correct metadata — title, artist, album, track number, year, genre — so the library is clean, sortable, and player-friendly. Locks the tag schema and naming/foldering convention FIRST, applies tags and a consistent file/folder layout across the whole library, then verifies every file is fully and consistently tagged. Defining the schema and the source of truth before touching files is what prevents a half-tagged, inconsistently-named mess.",
   "tags": [

package/data/craftbook-templates/na/narrated-slideshow/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "narrated-slideshow",
   "role": "general",
+  "category": "media",
   "name": "Animated Content Slideshow",
   "description": "Turn written content into a real MP4 video and animated GIF with DocBlocks. Locks the story and one message per scene, writes one H1 per scene in slideshow.md, then performs one multi-target conversion, previews the frames, and saves both rendered files in the artifacts drawer — no hand-built HTML player.",
   "tags": [

package/data/craftbook-templates/ne/newsletter-issue/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "newsletter-issue",
   "role": "general",
+  "category": "marketing",
   "name": "Newsletter Issue",
   "description": "Produce a single polished, email-client-safe newsletter issue — intro, a few curated stories with links, a featured section, and a CTA — that renders correctly across email clients. Outlines the issue's theme and section lineup FIRST, writes scannable, personable copy with working links, then builds the email-safe HTML using inline styles and table layout so it survives Gmail/Outlook. Use for recurring email newsletters, product updates, and curated digests sent to subscribers.",
   "tags": [

package/data/craftbook-templates/no/notification-router/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "notification-router",
   "role": "general",
+  "category": "code-build",
   "name": "Notification Router",
   "description": "Build an event-to-channel notification router: a small module that takes incoming events and routes each to the right destination (Slack channel, email, PagerDuty, webhook) based on type, severity, and quiet-hours rules — with dedupe, throttling, and a fallback channel. Scopes the routing matrix and policy FIRST (event taxonomy, channel map, severity→destination rules, dedupe key, rate limits, fallback), then a developer implements the router module to that matrix, then writes tests covering each routing branch. Scoping the matrix before coding is what guarantees every event type has a defined destination and that critical events can never be silently dropped. Use for notification routing, alert fan-out, event dispatch, webhook routing, and on-call/Slack notification systems.",
   "tags": [

package/data/craftbook-templates/oc/ocr-extract/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "ocr-extract",
   "role": "general",
+  "category": "media",
   "name": "OCR a Folder of Scans",
   "description": "Extract the text from a folder of scanned documents or photographed pages into clean, structured text — preserving reading order, paragraph breaks, and per-file provenance — then verify the extraction against the source images. Scope FIRST the languages, output structure (one file per scan vs a combined doc), and how to handle tables/columns/low-confidence regions, because OCR quality is dominated by handling layout and flagging uncertainty; then run extraction and verify a sample reads correctly. Covers OCR, text extraction, scanned documents, digitizing paper, receipt/invoice text, and image-to-text.",
   "tags": [

package/data/craftbook-templates/of/offer-compare/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "offer-compare",
   "role": "general",
+  "category": "business",
   "name": "Offer Comparison",
   "description": "Turn competing job offers into one honest decision sheet — every offer normalized into the same fact grid (comp, equity with vesting caveats, benefits, level, location, growth, deadlines), unknowns marked UNKNOWN instead of guessed, computed year-1 and 4-year views under stated assumptions, a weighted read against the candidate's OWN priorities, and a recommendation that separates arithmetic from judgment. Use when any second offer (or a strong counter) lands.",
   "tags": [

package/data/craftbook-templates/of/office-hours/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "office-hours",
   "role": "general",
+  "category": "practice",
   "name": "Office Hours",
   "description": "YC-style office-hours diagnostic. Surfaces forcing questions, challenges premises, lands on a sharper problem statement before any code is written.",
   "tags": [

package/data/craftbook-templates/on/onboarding-checklist/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "onboarding-checklist",
   "role": "general",
+  "category": "business",
   "name": "Generate an Onboarding Checklist",
   "description": "Produce a clear, role-specific onboarding checklist for a new hire, customer, or user — grouped by phase (before day one, week one, first 30 days), with each item owned, actionable, and verifiable. Scopes the audience, the phases, and a 'good item' rule FIRST so the checklist is complete and non-overlapping, then writes the actual checklist as a clean markdown document with grouped, owner-tagged, checkbox items. Scoping the phases and item-quality bar before writing is what turns a vague to-do dump into a sequenced, accountable onboarding plan.",
   "tags": [

package/data/craftbook-templates/on/onboarding-flow/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "onboarding-flow",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Product Onboarding Tour",
   "description": "Build a single-file product onboarding tour or coachmark walkthrough that guides a new user through key features with sequential tooltips, a highlighted target, next/back/skip controls, and a finish state. Designs the step sequence, what each step points at, and the copy strategy first, writes the step copy, then implements the spotlight overlay and step navigation. Tours break when a step points at the wrong element or skip/finish does not dismiss, so the flow-design phase locks the step-to-target map before any code.",
   "tags": [

package/data/craftbook-templates/on/oncall-handoff/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "oncall-handoff",
   "role": "general",
+  "category": "code-ops",
   "name": "On-Call Shift Handoff",
   "description": "Produce a clean end-of-shift on-call handoff: open incidents and their state, watch-items and known-flapping alerts, deferred actions, and anything the next on-call must do in the first hour. Scopes the handoff template and the carry-over rule FIRST (sections, what counts as an open item, the must-not-drop list), then a developer gathers the shift's signals (active incidents, recent pages, deferred follow-ups) and assembles the handoff so the incoming engineer can pick up cold. Scoping the template and carry-over rule before assembling is what guarantees no live incident or hot watch-item is dropped at the shift boundary. Use for on-call handoffs, shift handover notes, pager handoff, SRE shift change, and end-of-shift summaries.",
   "tags": [

package/data/craftbook-templates/on/one-pager/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "one-pager",
   "role": "general",
+  "category": "marketing",
   "name": "One-Pager Brief",
   "description": "Create a single-page brief or summary that fits one printed page and lands one message fast — a product one-pager, executive summary, project brief, or leave-behind. Scopes the single audience + the one thing they must remember FIRST, then designs a tight one-page layout (headline, scannable sections, a sidebar of facts), then writes punchy copy that fits the page — ruthless about cutting anything that pushes past one page. Use when the answer must be skimmable in 60 seconds on a single sheet.",
   "tags": [

package/data/craftbook-templates/op/ops-runbook/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "ops-runbook",
   "role": "maintenance-review",
+  "category": "code-ops",
   "name": "Execute an Ops Runbook",
   "description": "Execute a written operational procedure step by step with verification and a stop-on-anomaly rule. Inventories the runbook and its preconditions FIRST, then executes each step in order — act, verify the step's own check, record verbatim evidence in a run log — halting immediately when observed state does not match what the procedure expects, then writes an outcome report (clean completion, or a halt report naming the failing step, expected vs. observed, and the steps deliberately not executed). Recording verbatim evidence and refusing to run past an anomaly is the wisdom that separates a trustworthy operator from one who papers over broken state.",
   "tags": [

package/data/craftbook-templates/pa/page-spread/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "page-spread",
   "role": "general",
+  "category": "media",
   "name": "Page Spread",
   "description": "Produce one page spread from script to panels: beats planned, panel art generated against the character sheets — never freehand from memory — lettered and laid out as the page the reader turns to. Locks the panel plan FIRST — each panel naming the sheet references that anchor it and the caption text it carries — then generates the panels from those anchors, then assembles the lettered spread. Use for producing a comic page, 'let's do page three', panel-and-letter passes, turning a script page into art, and the per-page ritual of a whole book.",
   "tags": [

package/data/craftbook-templates/pa/parser-grammar/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "parser-grammar",
   "role": "project-starter",
+  "category": "code-data",
   "name": "Parser / DSL for a Small Grammar",
   "description": "Build a parser for a small domain-specific language or data format — tokenize, parse to an AST, and report clear errors on malformed input. Designs the grammar FIRST — the token set, the grammar rules (BNF-style), operator precedence, the AST node shapes, and the error strategy — then implements lexer + parser producing the AST, then tests valid inputs parse to the right AST and invalid inputs fail with useful errors. Covers tokenization/lexing, recursive-descent parsing, grammar rules, operator precedence, AST construction, and helpful parse-error messages.",
   "tags": [

package/data/craftbook-templates/pe/perf-audit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "perf-audit",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Performance Audit",
   "description": "Audit an application or page for performance problems with measurements, then produce a report of the highest-impact optimizations. First scopes the workloads and locks a performance budget and checklist (load time and Core Web Vitals, bundle/asset weight, render and main-thread cost, network waterfall and request count, server/query latency, memory and re-render churn), then MEASURES each against a baseline using real profiling rather than guessing, then writes a report that ranks bottlenecks by impact-vs-effort with a specific fix and the expected gain for each. Use this for a performance audit, speed optimization, finding bottlenecks, a Lighthouse-style review, reducing load time, or profiling slowness — it grounds every recommendation in a measured number and an estimated payoff, not 'it feels slow'.",
   "tags": [

package/data/craftbook-templates/pe/perf-optimization/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "perf-optimization",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Targeted Performance Fix",
   "description": "Make a measured, targeted performance improvement — profile to find the real bottleneck, optimize it, then prove the speedup with before/after numbers while keeping behavior correct. Profiles FIRST and locks a measurable target, because optimizing without measuring is guessing, then applies the focused change, then a reviewer confirms the improvement is real, behavior is unchanged, and the code is not needlessly obfuscated. Covers profiling/benchmarking, hotspot identification, algorithmic vs micro optimization, before/after measurement, and correctness-preserving speedups.",
   "tags": [

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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