@bendyline/gilde 0.1.95 → 0.2.0

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

package/data/craftbook-templates/co/codebase-ux-review/manifest.json

@@ -4,6 +4,9 @@
   "id": "codebase-ux-review",
   "role": "maintenance-review",
   "category": "design",
+  "interests": [
+    "software"
+  ],
   "name": "Codebase UX Review",
   "description": "Review the user experience implemented across a codebase and, when runnable, exercise the key flows in a real browser. Starts from the indexed UI surface rather than one screenshot, traces primary journeys and state transitions, then leaves a prioritized morning report covering information architecture, comprehension, feedback, recovery, consistency, responsive behavior, and user impact with source or runtime evidence. Use for a weekly UX sweep, product usability review, interaction review, or finding the highest-impact friction in an application.",
   "tags": [

package/data/craftbook-templates/co/cohort-analysis/manifest.json

@@ -4,6 +4,9 @@
   "id": "cohort-analysis",
   "role": "general",
   "category": "research",
+  "interests": [
+    "data"
+  ],
   "name": "Cohort / Retention Analysis",
   "description": "Analyze retention or behavior by cohort to reveal whether the product is getting stickier over time. Defines the cohort key, the activity event, and the retention window FIRST (so 'retained' has one unambiguous meaning), then builds the cohort/retention table and computes retention curves and trends as a data-analyst, then writes a readout on what the cohorts reveal. Use this for retention analysis, cohort tables, churn/stickiness analysis, a retention curve, or 'are newer users retaining better than older ones'.",
   "tags": [

package/data/craftbook-templates/co/company-research-brief/manifest.json

@@ -4,6 +4,10 @@
   "id": "company-research-brief",
   "role": "general",
   "category": "business",
+  "interests": [
+    "learning",
+    "work"
+  ],
   "name": "Company Research Brief",
   "description": "A sharp, dated, sourced brief on a company before an interview or application — what they do and how they make money, recent signals, team and role context, culture as evidenced, likely interview themes, and five specific questions to ask THEM. Skimmable in ten minutes; every claim dated or marked UNKNOWN rather than guessed. Use before any serious interview or when deciding whether to apply.",
   "tags": [

package/data/craftbook-templates/co/compat-check/manifest.json

@@ -4,6 +4,10 @@
   "id": "compat-check",
   "role": "maintenance-review",
   "category": "code-build",
+  "interests": [
+    "software",
+    "play"
+  ],
   "name": "Compatibility Check",
   "description": "Answer 'does it still work on the new version?' with a matrix, not a shrug: the datapack's files checked against each target version's format rules, every break named with the exact file and the exact fix, and the upgrade path written down in order. Locks the target version list and the compat criteria FIRST (format numbers, renamed folders, changed identifiers), then checks version by version, then writes the matrix and the fixes. Use for version compatibility checks, 'does the mod work on 1.21', update breakage sweeps, and upgrade planning.",
   "tags": [

package/data/craftbook-templates/co/competitive-analysis/manifest.json

@@ -4,6 +4,10 @@
   "id": "competitive-analysis",
   "role": "general",
   "category": "research",
+  "interests": [
+    "work",
+    "business"
+  ],
   "name": "Competitive Analysis",
   "description": "Compare a set of competitors across consistent dimensions and turn the comparison into an actionable analysis: a planner locks the competitor set and the evaluation dimensions, a researcher fills a feature/positioning matrix with evidence-backed cells, and a copywriter writes the analysis with a clear recommendation and competitive gaps. The ordering matters because dimensions chosen after the research are cherry-picked, and a write-up without a complete matrix has holes a reader will spot; locking the same dimensions for every competitor up front forces an apples-to-apples comparison. Use this for competitor teardowns, market positioning, win/loss analysis, 'how do we compare to X and Y' questions, and feature/pricing comparisons across rivals.",
   "tags": [

package/data/craftbook-templates/co/content-accuracy-review/manifest.json

@@ -4,6 +4,10 @@
   "id": "content-accuracy-review",
   "role": "maintenance-review",
   "category": "research",
+  "interests": [
+    "work",
+    "content"
+  ],
   "name": "Content Accuracy Review",
   "description": "Fact-check a piece of content for accuracy and produce a claim-by-claim verification report. First scopes the content and extracts every checkable claim (statistics, dates, quotes, attributions, causal and factual statements) and locks a verification standard, then verifies each claim against authoritative sources rating it true/false/misleading/unverifiable with the supporting evidence, then writes a report flagging every inaccuracy with the correction and source plus an overall trust rating. Use this for a fact-check, accuracy review, content verification, checking claims and statistics, source-checking an article, or vetting content before publishing — it returns a claim-level verdict backed by cited sources rather than a vague 'seems accurate'.",
   "tags": [

package/data/craftbook-templates/co/content-deck/manifest.json

@@ -4,6 +4,10 @@
   "id": "content-deck",
   "role": "general",
   "category": "design",
+  "interests": [
+    "work",
+    "content"
+  ],
   "name": "Slide Deck from Content",
   "description": "Turn a body of source content into a presentation deck. Outlines the narrative first, designs a consistent slide look, then builds the deck (HTML slides), evaluating for narrative flow and visual consistency.",
   "tags": [

package/data/craftbook-templates/co/contract-template/manifest.json

@@ -4,6 +4,10 @@
   "id": "contract-template",
   "role": "general",
   "category": "business",
+  "interests": [
+    "legal",
+    "business"
+  ],
   "name": "Contract Template (Non-Legal-Advice)",
   "description": "Draft a reusable, plain-language agreement template — service agreement, NDA, freelance contract, or terms — with clearly marked fill-in fields, structured numbered clauses, and a prominent non-legal-advice disclaimer. Scopes the parties, obligations, and risk allocation FIRST, drafts clear enforceable-style clauses with placeholders for the variable terms, then has a reviewer check completeness and flag anything that genuinely needs a lawyer. NOT legal advice — every output must say so. Use for templated agreements you will adapt and have counsel review.",
   "tags": [

package/data/craftbook-templates/co/corpus-email-digest/manifest.json

@@ -4,6 +4,9 @@
   "id": "corpus-email-digest",
   "role": "general",
   "category": "business",
+  "interests": [
+    "work"
+  ],
   "name": "Daily Email Digest from a Corpus",
   "description": "Produce an email-ready digest that summarizes a corpus of content (docs, feeds, notes) for a recurring send. Scopes what matters and the format first, drafts the digest in a consistent voice, then builds the email-ready output and evaluates for accuracy and scannability.",
   "tags": [

package/data/craftbook-templates/co/cover-letter/manifest.json

@@ -4,6 +4,9 @@
   "id": "cover-letter",
   "role": "general",
   "category": "business",
+  "interests": [
+    "learning"
+  ],
   "name": "Tailored Cover Letter",
   "description": "Write a tailored, one-page cover letter that maps a candidate's real background to a specific job's requirements: it first scopes the role's key requirements, the company hook, and the 3-4 strongest matching proof points from the applicant's experience, then drafts a focused letter with a specific opening, evidence-backed body paragraphs, and a confident close. Covers cover letter, job application letter, motivation letter, application writing, and personalized cover letter. Scoping the role-to-experience mapping before writing is the point: a small model that picks the strongest evidence for THIS job avoids the generic, one-size-fits-all letter that could be sent anywhere and lists duties instead of proving fit.",
   "tags": [

package/data/craftbook-templates/cr/crm-update-batch/manifest.json

@@ -4,6 +4,9 @@
   "id": "crm-update-batch",
   "role": "general",
   "category": "business",
+  "interests": [
+    "business"
+  ],
   "name": "Bulk CRM Update from Notes",
   "description": "Turn unstructured notes (call logs, meeting recaps, email threads) into a batch of structured CRM updates: per-contact field changes, activity logs, and next-step tasks as a validated import file. Scopes the CRM field schema and extraction rules FIRST (which objects/fields, allowed picklist values, the match-or-create key, required fields), then a developer extracts and maps every note into rows against that schema, then a reviewer validates the batch for schema-conformance and that no update mutates a field without evidence in the source. Scoping the schema before extraction is what makes the import load cleanly and prevents fabricated field values. Use for CRM data entry, bulk contact updates, importing notes into Salesforce/HubSpot, activity logging, and turning call notes into pipeline updates.",
   "tags": [

package/data/craftbook-templates/cr/crossword-forge/manifest.json

@@ -4,6 +4,10 @@
   "id": "crossword-forge",
   "role": "general",
   "category": "design",
+  "interests": [
+    "play",
+    "home"
+  ],
   "name": "Forge a Crossword",
   "description": "Construct a personalized crossword and prove it works before anyone's pencil touches it: the grid actually interlocks, every entry sits in the grid exactly where its number says, every clue is tuned to the solver — and the whole thing ships as a printable page with the solution kept decently out of sight. Locks the theme and the word list FIRST, then constructs the mechanically-verified grid, then renders the printable puzzle. Use for making a crossword, a personalized puzzle for the family, 'a crossword with the grandkids' names in it', and printable puzzle gifts.",
   "tags": [

package/data/craftbook-templates/cs/csv-transformer/manifest.json

@@ -4,6 +4,9 @@
   "id": "csv-transformer",
   "role": "general",
   "category": "code-data",
+  "interests": [
+    "data"
+  ],
   "name": "CSV / Tabular Transformer",
   "description": "Reshape and convert tabular data from one schema to another: rename and reorder columns, split or merge fields, derive new columns, pivot/unpivot, change format (CSV<->JSON<->TSV), and filter rows. Locks the input and target schema and the field-by-field mapping FIRST (so the transform is a contract, not guesswork), then builds the transform and emits the output, then verifies row counts and a sample mapping. Use this for reshaping a CSV, converting data formats, remapping columns, flattening JSON to a table, or reformatting an export for another tool.",
   "tags": [

package/data/craftbook-templates/da/dashboard-spec/manifest.json

@@ -4,6 +4,10 @@
   "id": "dashboard-spec",
   "role": "general",
   "category": "code-docs",
+  "interests": [
+    "data",
+    "work"
+  ],
   "name": "Dashboard Specification",
   "description": "Specify a dashboard from the questions it must answer, before anyone builds it — the artifact that prevents a chart-salad dashboard nobody uses. Scopes the audience, the decisions, and the questions FIRST, then designs the dashboard layout: which widgets/charts answer which question, their metric definitions, filters, refresh, and visual hierarchy. The output is a build-ready spec, not the dashboard itself. Use this for planning a dashboard, a BI/reporting spec, a metrics dashboard design, deciding what charts a dashboard needs, or a dashboard requirements doc.",
   "tags": [

package/data/craftbook-templates/da/data-dictionary/manifest.json

@@ -4,6 +4,9 @@
   "id": "data-dictionary",
   "role": "general",
   "category": "code-data",
+  "interests": [
+    "data"
+  ],
   "name": "Data Dictionary",
   "description": "Document a dataset's schema as a clear, complete data dictionary so others can use it without guessing. Inspects the data FIRST to derive each column's real type, value domain, null rate, units, and relationships from the actual values (not assumptions), then writes a readable dictionary with one entry per column plus dataset-level context. Use this for documenting a schema, building a data dictionary, a column glossary, a table reference, or onboarding docs for a dataset.",
   "tags": [

package/data/craftbook-templates/da/data-export-migrate/manifest.json

@@ -4,6 +4,10 @@
   "id": "data-export-migrate",
   "role": "general",
   "category": "code-data",
+  "interests": [
+    "data",
+    "software"
+  ],
   "name": "Migrate Data Between Tools",
   "description": "Migrate records from a source tool/format to a destination tool/format — CRM to CRM, spreadsheet to app, JSON export to a new API — with a field mapping, value transforms, and a reconciliation that proves nothing was lost or corrupted. Locks the source→destination field map, the transform/normalization rules, and the reconciliation criteria FIRST, then builds the extract-transform-load with a dry-run preview, then verifies record counts match, key fields round-trip, and a diff report flags any mismatch. Mapping-and-reconciliation-before-load is the discipline that makes a migration trustworthy rather than a one-shot leap of faith.",
   "tags": [

package/data/craftbook-templates/da/data-join-merge/manifest.json

@@ -4,6 +4,9 @@
   "id": "data-join-merge",
   "role": "general",
   "category": "code-data",
+  "interests": [
+    "data"
+  ],
   "name": "Join / Merge Two Datasets",
   "description": "Combine two datasets into one reconciled table on a shared key, correctly handling the join type, key mismatches, and duplicate fan-out. Profiles both sources and locks the join key, join type, and conflict rules FIRST (so the merge doesn't silently drop or duplicate rows), then builds the joined output, then verifies the match rate and that no row count exploded. Use this for joining two tables, merging datasets, a VLOOKUP-style match, enriching one file from another, or reconciling records across two sources.",
   "tags": [

package/data/craftbook-templates/da/data-quality-audit/manifest.json

@@ -4,6 +4,9 @@
   "id": "data-quality-audit",
   "role": "maintenance-review",
   "category": "code-data",
+  "interests": [
+    "data"
+  ],
   "name": "Data Quality Audit",
   "description": "Audit a dataset against explicit data-quality rules and produce a scorecard of where it passes and fails across completeness, validity, consistency, uniqueness, and timeliness. Defines the quality rules and dimensions FIRST (so 'quality' is measurable, not a vibe), then runs the audit to measure each rule with pass rates and failing examples, then writes a prioritized report with an overall score and remediation steps. Use this for a data quality audit, data health check, validation report, data-quality scorecard, or assessing whether a dataset is trustworthy.",
   "tags": [

package/data/craftbook-templates/da/data-to-report/manifest.json

@@ -4,6 +4,10 @@
   "id": "data-to-report",
   "role": "general",
   "category": "research",
+  "interests": [
+    "data",
+    "work"
+  ],
   "name": "Dataset to Narrative Report",
   "description": "Turn a dataset into a written, evidence-backed analytical report that a non-technical reader can act on. Analyzes the data FIRST to surface the real findings (key metrics, segments, trends, surprises) with supporting numbers, then writes a narrative that leads with the takeaway and traces every claim to a figure, then builds the polished report document with sections, a summary table, and an explicit limitations note. Use this for turning raw numbers into an insights report, executive summary, data storytelling, or a findings write-up stakeholders will read.",
   "tags": [

package/data/craftbook-templates/da/data-viz-page/manifest.json

@@ -4,6 +4,10 @@
   "id": "data-viz-page",
   "role": "project-starter",
   "category": "code-build",
+  "interests": [
+    "software",
+    "data"
+  ],
   "name": "Data Visualization Explorer",
   "description": "Build a single interactive chart or data explorer page — bar, line, scatter, or pie — driven by sample or provided data, with controls to filter, switch series, or change the dimension and a tooltip on hover. Scopes the dataset and the question the chart answers first, then the chart type and encodings, then implements a canvas or SVG chart with real interactivity. A chart that does not map data to pixels correctly is worse than a table, so the data and chart-design phases lock the encoding and the axes before any rendering code.",
   "tags": [

package/data/craftbook-templates/da/dataset-clean/manifest.json

@@ -4,6 +4,9 @@
   "id": "dataset-clean",
   "role": "general",
   "category": "code-data",
+  "interests": [
+    "data"
+  ],
   "name": "Clean a Dataset",
   "description": "Profile, clean, and validate a messy CSV/TSV/JSON dataset into an analysis-ready table. Profiles the raw data FIRST (row/column counts, types, null rates, duplicates, outliers, encoding) so cleaning decisions are evidence-based, then applies deterministic transforms (dedup, type coercion, null handling, whitespace/case normalization, value standardization), then validates the cleaned output against the same profile so nothing was silently dropped or corrupted. Use this for data wrangling, tidying, deduplication, normalizing dirty spreadsheets, and prepping raw exports for charts or modeling.",
   "tags": [

package/data/craftbook-templates/de/design-review/manifest.json

@@ -4,6 +4,10 @@
   "id": "design-review",
   "role": "maintenance-review",
   "category": "design",
+  "interests": [
+    "software",
+    "content"
+  ],
   "name": "UX & Visual Design Review",
   "description": "Critique a UI's user experience and visual design and produce a prioritized design-review report. First scopes the screens and flows and locks a heuristic checklist (visual hierarchy, spacing rhythm and alignment, typographic scale, color and contrast, consistency, affordance and feedback, empty/loading/error states, and the primary task's friction), then reviews each screen against those heuristics with a designer's eye for both polish and usability, then writes a findings report rating each issue by impact with a concrete, specific design fix. Use this for a design review, UX critique, visual QA, design feedback, a heuristic evaluation, or 'does this look and feel right' — it gives actionable, specific design fixes (exact spacing, color, hierarchy changes) rather than 'make it pop'.",
   "tags": [

package/data/craftbook-templates/de/design-system-consultation/manifest.json

@@ -4,6 +4,10 @@
   "id": "design-system-consultation",
   "role": "maintenance-review",
   "category": "design",
+  "interests": [
+    "software",
+    "content"
+  ],
   "name": "Design System Consultation",
   "description": "Interview for product context and taste, then propose a full design system — type, color, layout, motion — and capture it as a DESIGN.md with live preview pages.",
   "tags": [

package/data/craftbook-templates/di/diagram-from-text/manifest.json

@@ -4,6 +4,10 @@
   "id": "diagram-from-text",
   "role": "general",
   "category": "code-docs",
+  "interests": [
+    "software",
+    "work"
+  ],
   "name": "Diagram from Text",
   "description": "Render a clear technical diagram — flowchart, architecture, sequence, ER, or org chart — from a plain-language description, as code-defined (Mermaid/Graphviz/SVG) so it is editable and version-controllable rather than a flat picture. Spec FIRST the diagram type, the exact nodes and edges, and the layout direction, because diagrams fail when relationships are wrong or the graph is an unreadable tangle; then build the diagram so it renders, with every described entity and relationship present and labeled. Covers flowcharts, architecture diagrams, sequence diagrams, ER diagrams, org charts, mind maps, and diagram-as-code.",
   "tags": [

package/data/craftbook-templates/dr/drive-wrap-up/manifest.json

@@ -4,6 +4,10 @@
   "id": "drive-wrap-up",
   "role": "general",
   "category": "personal",
+  "interests": [
+    "home",
+    "business"
+  ],
   "name": "Fundraiser Wrap-Up",
   "description": "Close a fundraising drive properly: verify the final numbers against the donation ledger, confirm every donor was thanked (or finish the thank-yous now), and write the wrap-up story — the total, what the money does, and the people who made it happen — ready to share with the community and hand to the next organizer. Locks the wrap-up's claims and the thank-you completeness check FIRST, then verifies against the ledger, then writes the story. Use for ending a fundraiser, drive wrap-up reports, final fundraising totals, and community thank-you posts.",
   "tags": [

package/data/craftbook-templates/du/due-diligence-brief/manifest.json

@@ -4,6 +4,10 @@
   "id": "due-diligence-brief",
   "role": "general",
   "category": "research",
+  "interests": [
+    "work",
+    "business"
+  ],
   "name": "Due-Diligence Brief",
   "description": "Produce a structured due-diligence brief on an entity (company, vendor, investment, partner): a planner locks the diligence dimensions and red-flag criteria, a researcher gathers verifiable facts and risk signals per dimension with sources, and a copywriter writes a decision-oriented brief with findings, risks, and an overall read. The ordering matters because diligence without locked dimensions misses a category (e.g. legal, financial, reputational) and a brief without a red-flag rubric buries the risks; fixing the dimensions and what counts as a flag first makes the brief decision-ready and defensible. Use this for vendor/partner due diligence, investment diligence, background briefs on a company or person, risk assessments, and 'should we work with / invest in X' questions.",
   "tags": [

package/data/craftbook-templates/en/engineering-retrospective/manifest.json

@@ -4,6 +4,10 @@
   "id": "engineering-retrospective",
   "role": "maintenance-review",
   "category": "business",
+  "interests": [
+    "software",
+    "work"
+  ],
   "name": "Engineering Retrospective",
   "description": "Build a data-grounded engineering retrospective from git history: activity, hotspots, review patterns, and per-person growth notes for a given window.",
   "tags": [

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

@@ -4,6 +4,10 @@
   "id": "expense-categorize",
   "role": "general",
   "category": "business",
+  "interests": [
+    "data",
+    "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/ex/explain-code-folder/manifest.json

@@ -0,0 +1,26 @@
+{
+  "schemaVersion": 1,
+  "kind": "craftbook-template",
+  "id": "explain-code-folder",
+  "role": "general",
+  "category": "code-docs",
+  "interests": [
+    "software"
+  ],
+  "name": "Explain a code folder",
+  "description": "A plain-language tour of a folder of code: what it does, how the files are organised, how to run it, and the three files to read first. Every file and command it names comes from the folder itself. Good for a project you inherited, an open-source tool you want to understand, or your own code after a long break.",
+  "tags": [
+    "gallery",
+    "first-project",
+    "code",
+    "explain",
+    "overview",
+    "onboarding",
+    "docs"
+  ],
+  "maintainer": {
+    "name": "Gezel"
+  },
+  "license": "MIT",
+  "yankedVersions": []
+}