Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.babou.ai/llms.txt

Use this file to discover all available pages before exploring further.

These examples follow the same anchor scenario the rest of the docs use: a SaaS team shipping a new pricing tier (“Pricing Page Refresh”). Each one shows a different way agents drive Babou: from a release note, from a Figma frame, and across the full canonical output set in one shot.

Example 1: Launch ad from a release note

The simplest flow. The agent reads what shipped and builds the matching ad.
User: We just shipped the Team tier. Build the launch ad.

Claude: I'll pull the latest release notes and build a 30-second
launch ad. Setting up the project now.

[Claude uses CreateProject]
✓ Created project: "Pricing Page Refresh"

[Claude uses AddChapter]
✓ Added chapter: "Launch Ad" (30s)

[Claude uses AddPrompt]
  prompt: "30-second product launch ad for the new Team tier.
  Lead with the headline from release note v2.4. Drop in the new
  pricing screenshot. Resolve brand colors and type from the catalog.
  Close on a CTA matching the pricing page button."

[Waits up to 30 seconds for completion]
✓ Chapter content built

[Claude uses ExportProject]
✓ Export started

The launch ad is ready: https://assets.babou.ai/exports/prj_abc123xyz.mp4

Example 2: Feature demo from a Figma frame

The agent takes a Figma frame as the input surface, not a typed prompt. Useful when the design lands before the engineering does.
User: Take this Figma frame for the new Team-plan dashboard
and build a 60-second feature demo.

[Frame: figma.com/file/.../?node-id=12-345]

Claude: Reading the frame and setting up the demo.

[Claude uses CreateProject]
✓ Created project: "Team Plan Dashboard Demo"

[Claude uses AddChapter] x3
✓ Added: "Open" (10s), "Walkthrough" (40s), "CTA" (10s)

[Claude uses AddPrompt for each]
  Open:
    "10-second open. Pull the headline from the frame.
    Animate in the dashboard hero shot. Brand from catalog."

  Walkthrough:
    "40 seconds walking through the three new dashboard sections
    in the Figma frame. One section per beat. Match the type
    rhythm in the catalog."

  CTA:
    "10-second close on the primary CTA from the frame,
    matched to the pricing page button color."

✓ All chapters built

[Claude uses ExportProject]
✓ Export started, 2-5 minutes

Demo will land at the export URL when complete.

Example 3: One launch, every format

The full canonical output set, kicked off in one conversation. This is what “every release becomes a campaign” looks like end to end.
User: For the Team tier launch, build the full set: launch ad,
feature demo, and three social cuts (16:9, 9:16, 1:1).

Claude: One project per format. Pulling everything from the
release note and the catalog.

[Claude uses CreateProject] x5
✓ "Pricing Page Refresh: Launch Ad"
✓ "Pricing Page Refresh: Feature Demo"
✓ "Pricing Page Refresh: Social 16:9"
✓ "Pricing Page Refresh: Social 9:16"
✓ "Pricing Page Refresh: Social 1:1"

[For each project: AddChapter + AddPrompt]
✓ Launch Ad (30s): building
✓ Feature Demo (60s): building
✓ Social 16:9 (15s): building
✓ Social 9:16 (15s): building
✓ Social 1:1 (15s): building

[Waits, then ExportProject for each]
✓ All five exported.

Drop folder ready. Brand and message land the same in every
format because they all resolve from the same catalog.

Common patterns

Check existing projects before adding chapters

User: Add a "Why Now" chapter to my pricing launch project.

Claude: Let me find it first.

[Uses ListProjects]

I see two pricing-related projects:
1. "Pricing Page Refresh" (created today)
2. "Pricing Page Refresh: Social 9:16" (created today)

Which one?

User: The first.

[Uses AddChapter]
✓ Added "Why Now" (8s)

Iterate without starting over

User: The launch ad's hook is too soft. Lead harder on the price drop.

Claude: I'll re-prompt the Hook chapter with force: true so it
cancels the current cut and rebuilds.

[Uses AddPrompt with force: true]
✓ Hook rebuilt: leads on the price, then the headline

Handle a long-running prompt

User: Build the feature demo.

[Claude uses AddPrompt]
✓ Submitted. Polled for 30 seconds.
✓ Status: still processing. Tool returned a timeout response
  with chapter_id and a hint to poll again.

Claude: The demo is still rendering. I'll check back in a moment.

[Waits, then re-checks chapter status]
✓ Done. Moving on to export.

Troubleshooting

Export with no chapter content

User: Export the launch project.

Claude: The project has chapters but none of them have content yet.

[Uses ListChapters]

You have three chapters: Hook, Tier Breakdown, CTA.
None have completed prompts.

Want me to fill them in based on the release notes?

Status check on a running export

User: Is the launch ad export done?

[Claude uses ExportProject, same call returns the current status]

Still exporting. Started 90 seconds ago. Estimate: 1-2 minutes.

[Polls again]
✓ Done. Download link is ready.

Next steps

Set up the MCP server

Drop Babou into your MCP-aware client

Tool reference

Every tool, with parameters and examples

REST API

Drive Babou from your own application code

Workflow guide

Deep dive on the project / chapter / prompt flow