@bendyline/gilde 0.1.94 → 0.2.0

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

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

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

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

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

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

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

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

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

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

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

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

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

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