Skip to main content

Playbook Creative Apps Platform

Your agent builds the app.
Playbook runs it.

Ask Claude for a gallery, a portfolio or a catalogue of one of your boards. It writes the app, deploys it with one MCP call, and Playbook hosts it at its own address. Your board is the database.

Read the guideConnect Claude
waves.playbookapps.cloudOpen in a new tab

Waves: 48 photos on one Playbook board, turned into an app by Claude. Every feature below is running in it.

How this one was made

  1. You ask
    Build a public gallery of my Waves board: a chapter for each sub-board, filters by mood, search by meaning, a lightbox with each photo's palette, and a slideshow.
  2. Claude deploys
    deploy_app(
  board_token: "czRe3d…",
  slug: "waves",
  name: "Waves",
  files: {
    "index.html": …,
    "app.js": …,
    "styles.css": …,
    "favicon.svg": …
  }
)
  3. It is live

    waves.playbookapps.cloud

    Add a photo to the board and the app shows it on the next visit. Nothing is copied out of Playbook.

What the app reads from Playbook

The app is four static files and a small backend. Everything it knows about the photos comes from the board, over the same REST API you can call yourself.

Search by meaning

“Someone riding inside a barrel” finds barrels, though no title says so.

AI search

Colors you can click

The wave across the top is every color in the board. Pick one to see the photos that share it.

Extracted colors

Chapters

Breakers, Surf, Golden Hour and From Above are the board's own sub-boards.

Board hierarchy

Moods and tags

Calm, Playful, Glowing and Wild come from a custom field; tags filter the grid from the lightbox.

Custom fields and tags

More like this

One click turns a photo into a search for its neighbours.

AI search

A slideshow and a print sheet

The slideshow fades over each photo's darkest color. The sheet is rendered by the app's own backend.

Previews and a backend

How it works

  • Static files, no build. HTML, CSS and JavaScript, plus an optional worker.js for anything the browser cannot do.
  • No keys in the code. The page reads the board through its own address, and Playbook adds a read-only credential that covers one board.
  • Your board is the database. Titles, tags, custom fields, colors and previews stay in Playbook and stay current.
  • Its own address. Each app gets a subdomain of playbookapps.cloud, away from your Playbook session.

What to know first

  • Public. Anyone with the address sees everything on the board, so put the app on a board you mean to publish.
  • Coming soon. Uploads from visitors, comments and approvals, approved-only boards, and your own domain.
  • Small by design. Up to 50 files and 1 MB per app, and 10 apps per workspace. Visits count toward the workspace's API allowance.
  • Early access. Hosted apps are switched on per workspace. Ask Playbook support to try them.

Build one from your own board

Connect Claude to Playbook, pick a board, and describe the app you want.

Read the guideConnect Claude