yesod.work

Room 01 · Idea Capture

The registry teaches your agents what you have already built.

Yesod is not only a software factory — it is a registry of your projects and tools, so agents can discover capabilities instead of reinventing them.

Stop rewriting the same utility

How many times have you written a “split this PDF into a list of PNG chunks” program? You build utilities, then forget their features. The registry is the answer: every project onboarded into Yesod becomes something your agents can discover, query, and use.

Onboarding a project registers what it is, what it does, and how to invoke it. From then on, knowledge accumulates through usage notes — durable, timestamped observations that stay attached to the tool.

Watch an agent discover a tool

A coding agent needs page images of a PDF for a layout review. Instead of writing that utility for the fifth time, it asks the registry. This is a real session:

$ yesod search pdf

Tools matching 'pdf'
  ppg-pdf    internal   Renders branded PDFs from Markdown via
                        Pandoc + XeLaTeX. Per-brand LaTeX templates…
  canva      external   …produce the 3-page title/main/final background
                        designs that become ppg-pdf themes.
  chunkpdf   internal   Convert a PDF into one low-res PNG per page for
                        LLM layout review. Deliberately cheap: 72 DPI…

$ yesod ask "how do I split a PDF into PNG images for an LLM to look at?"

Use chunkpdf.

 1. chunkpdf: run `chunkpdf input.pdf`. It emits one PNG per page
    into input_pages/ as input_p01.png, input_p02.png, etc.,
    zero-padded so they sort lexicographically in page order.
 2. Tune with -d and -w if the defaults (72 DPI, 1024 px max width)
    are too low-res or too large. These defaults are deliberately
    cheap for VLM review.
 3. Pass the generated page images to your VLM in filename order.

Sources
  • chunkpdf (internal) — converts PDF pages to low-res PNGs for VLM review

One search, one question, one cited answer — the agent runs chunkpdf input.pdf and moves on. The utility got written once, months ago; the registry made sure it never gets written again.

The registry ends where the factory begins: when a capability is missing or broken, the observation becomes a feature request or a bug report — the factory’s input.

A full station guide arrives with the new edition of the book.