Backbase

How it works

From a Figma frame to a draft page in your Storyblok space, with a yes from you before every write.

The flow

/backbase:new <figma frame link> my-site
The flow: Doctor, Create, Read, Classify, then Gate 1, where you confirm the plan. 1 · bbDoctorbb doctor2 · bbCreatebb create3 · AgentReadsections.json4 · AgentClassifyplan.json5 · YouGate 1you confirmbb checks it until it passes The flow: Doctor, Create, Read, Classify, then Gate 1, where you confirm the plan. 1. Doctorbbbb doctor2. Createbbbb create3. ReadAgentsections.json4. ClassifyAgentplan.json5. Gate 1Youyou confirm
Agent makes the judgment calls.bb holds the facts and runs the checks.You decide.

In a project you already have, /backbase:analyze starts at Read. Up to Gate 1, nothing is written to Storyblok or Figma.

After Gate 1, each write waits for your yes: sync the space at Gate 2, compose a draft page, refine it, then build the missing components. Nothing is published.

Reuse first

Most of a page already exists. Backbase reuses Backpack and Site Builder first, and builds from existing blocks second. It writes new code only where Backpack has a gap, and only after you say yes. See the bucket rules.

Who it’s for

EF developers building Site Builder pages on Backpack 4, with Claude Code. Support for other AI agents is coming.

Where it is

In beta: from a Figma frame to a draft page in your Storyblok space. Next: bb adopt and audits for sites already live. The changelog has each release.