Agent Reports Should Be Themes, Not One-Off Pages
Maps ShitRat/Brain report output to a reusable wzrrd theme instead of hand-styling each agent artifact.
The source page wasn’t extractable when this note was backfilled, but the Slack note has the important bit: “making this report style a wzrrd theme (adding themes).”
That’s the right move. A strong report style shouldn’t live as a bespoke one-off page. It should become a theme layer that any future wzrrd artifact can use without re-solving typography, spacing, hierarchy, and vibe every damn time.
This matters for joelclaw because agent output gets more useful when it has repeatable surfaces. A ShitRat Brain Proposal can be a single report, or it can become a reusable visual contract for review docs, discovery notes, system briefs, and public receipts.
The clever part is treating presentation as infrastructure. Not polish after the fact. Not a screenshot. A reusable publishing primitive that makes agent work easier to scan, share, and trust.
Key Ideas
- A good wzrrd report style should graduate into a theme instead of staying trapped in one page.
- Theme support turns agent-generated reports into reusable artifacts with consistent hierarchy, typography, and reading rhythm.
- The Slack backfill suggests the source was less about the specific page and more about turning the pattern into a publishing capability.
- This maps cleanly to joelclaw review surfaces: reports, proposals, discovery pages, and public receipts can share a recognizable system skin.
- Presentation belongs in the system layer when agents are expected to produce readable public work repeatedly.