Bonfires, and how to vibe code well.

A live ZABAL Gamez fireside between Zaal and Carlos (Plat0x), the Bonfires developer. It opens with the BetterCallZaal / WaveWarZ theme, then runs as half working session and half vibe-coding masterclass. The working session covers the Bonfires rewrite (hard deadline June 14), ZAO's second Bonfire agent, a CLI that auto-pushes context to the Bonfire on every git commit, and the positioning of Bonfires as a "sense-making tool" where the agent is "the librarian of a library." The masterclass is builder-track gold: plan-then-goal with a measurable threshold, Bob-and-Alice diagramming before any code, types-first prompting, documentation-as-code, the Linus Torvalds compiler analogy, and Carlos's three skills.

• Opening
• The BetterCallZaal / WaveWarZ theme
• Working session - Bonfires + ZAO
• The Bonfires rewrite and the hard June 14 deadline
• ZAO's second Bonfire agent: works in DMs, not in groups (deferred to post-June 14)
• A CLI that auto-pushes context to the Bonfire on every git commit
• Storing recordings on a subpage and pointing Bonfire episodes at the media URL
• Positioning: a "sense-making tool"; the agent as the librarian of a library
• One Bonfire, many agents: shared context, separate episode stacks (a federated crew)
• Vibe-coding masterclass
• Plan-then-goal: a plan plus one goal with a measurable threshold
• Bob and Alice: diagram the exchange and sequence before any code
• Types-first prompting and a protocol/adapter contract
• Documentation-as-code: the docs should reproduce the code 1:1
• The Linus Torvalds compiler analogy
• Punch above your weight: let AI read the papers and docs first
• Carlos's three skills: plan-making, sub-agents, adversarial agents

• Plan-then-goal: give Claude a plan plus one goal with a measurable threshold (e.g. under 5s query latency) so it runs until it hits the number, instead of stopping after "phase 1."
• Diagram Bob and Alice before any code - define the exchange and the sequence first, pick the language last.
• Prompt types-first ("define types in Python for an app that does X") and use a protocol/adapter contract, so you can swap the database later without a rewrite.
• Documentation-as-code: remove all the code and the docs alone should reproduce it 1:1.
• Carlos's three skills: plan-making (built from papers), sub-agents (the senior-dev orchestrator), and adversarial agents (one for, one against).
• One Bonfire can host many agents - they share context but keep their own episode stacks, so a federated crew stays distinct.