Docs

Craftbook gallery taxonomy

The content backlog for the gallery (Pillar 3). Each entry below maps to one ArchetypeSpec in scripts/craftbook-archetypes.ts; running pnpm --filter @bendyline/gezel-catalog generate-craftbooks turns specs into bundled craftbooks, and suggest_craftbook ranks the lot into a top-K shortlist for the voorman.

This is a menu, not 400 finished specs. The value of a specific gallery book over the generic build-loop is two things, and every entry encodes them: the right specialist role per phase, and a domain-correct ordering. Write the small spec (phases + roles + prompts); the deterministic generator guarantees a schema-valid, consistently-gated book.

How to read an entry

- id — Name. phaseA(role) → phaseB(role) → build(role)        [notes]

Shipped seed (in craftbook-archetypes.ts today): html-arcade-game, branding-website, image-set-index, content-deck, corpus-email-digest.


Two axes

  1. Outcome axis — "what the human wants." The 12 families below.
  2. Capability axis — "one craftbook per MCP." Enumerable directly from the catalog's toolset list; see the last section. These are the fastest, most reliable seed (grounded in real tools) and double as building blocks the outcome books compose.

1. Build — interactive / web

2. Build — software / code

3. Media — images

4. Media — audio / video

5. Documents & decks

6. Content & writing

7. Data & analysis

8. Knowledge & research

9. Comms & ops automation

10. Personal / biz workflows

11. Review & QA

12. Ship & release


Capability axis — one craftbook per MCP

The catalog already lists every toolset/MCP. A capability book is enumerable from that list and tool-grounded (its steps reference the MCP's real tools, so the generator can't invent capabilities). Shape:

use-<toolset> — Accomplish a task with <toolset>.
  scope(planner) → operate(developer, using <toolset>'s tools) → evaluate(reviewer)

Enumeration: read catalog.list('toolset'), and for each toolset emit a spec whose operate phase names that toolset's tools and whose scope phase locks acceptance criteria. Group by the existing toolset category (categorizeToolset) so the gallery reads sensibly — representative shapes:

Capability books are also building blocks: an outcome book like branding-website composes the image-gen capability for its hero image.


Turning an entry into a spec

  1. Pick an entry; copy its phase→role shape.
  2. In scripts/craftbook-archetypes.ts, add an ArchetypeSpec: id, name, description (what suggest_craftbook ranks on), tags, triggers, the phases (each with a concrete prompt — the first phase must lock an acceptance-criteria checklist), and evaluate (what to check; loopBackTo if not the last phase).
  3. pnpm --filter @bendyline/gezel-catalog generate-craftbooks then build-index --kind=craftbook-template.
  4. The bundled-craftbook guard test validates it; suggest_craftbook can now rank it; the meester can pin it at project creation.

Prioritization for scaling 12 → hundreds: seed the capability axis first (mechanical, grounded), then the highest-traffic outcome families (1, 2, 5, 6, 9), and eval-gate new books (Pillar 4) before trusting them — a bad book misleads a small model worse than no book.

Edit this page on GitHub