Make a theme, hand it to Claude

The cards are drawn by the kit's own code, at the size of a 16:9 video. Things arrive as they would while the voice reads.

These are the kit's own rules, run on your theme file. A theme that fails one is refused when a video is rendered, so it is not handed over here either.

• Caption text on its boxlook
• Captions on a tall frame7 to 1
• Text on a cardlook
• Text on the light groundlook
• Brand colour on a cardlook
• The callout labellook
• Text on a panel4.5 to 1

contrast could not be measured where a surface is see-through or shaded (caption text on its box; text on the ground of a card; text on the light ground; the highlight on the ground of a card; the callout label). Look at these in the preview.

Take it to Claude

1. 1Copy the promptIt holds your theme, your settings and what to make.
2. 2Paste it into Claude CodeIn your project folder. No API key is needed.
3. 3Claude makes the videoIt saves the theme, writes the scenes, drafts, renders and checks.

Make a 60 second demo video of https://my-product.com with Kwartz Showcase.
It should show: how a new user gets started.

Do this in order. If a step fails, stop and tell me what the error says.

1. Install the kit in this folder. If this folder has no package.json, create one first: { "name": "my-video", "private": true, "type": "module" }. Then run "bun add -d kwartz-showcase". If Bun is not installed, run "npm install --save-dev kwartz-showcase" and write "npx" wherever these steps say "bunx".
2. Run "bunx showcase doctor". It lists what is missing, and ends with an error when something is: that is expected. If chromium or voice is missing, run "bunx showcase setup" yourself: it is a one-time download of about 350 MB. If ffmpeg or python is missing, tell me what to install and wait for me.
3. Run "bunx showcase init --config --theme glass". This adds the config, a starter video.ts and the skills: kwartz-showcase, showcase-theme-glass, showcase-theme-new. Then add "out/" and ".showcase/" to .gitignore (create the file if there is none).
4. Save this as themes/acme.json, exactly as written:

{
  "description": "A theme for acme, from the glass look",
  "extends": "glass",
  "colors": {
    "accent": "#FDE68A"
  }
}

5. Replace the settings in showcase.config.json with these (keep its "$schema" line):

{
  "name": "demo",
  "url": "https://my-product.com",
  "length": 60,
  "platforms": [
    "youtube",
    "instagram-reel"
  ],
  "theme": "acme",
  "safety": {
    "banned": []
  }
}

The address is a live site, so it is filmed read-only: scenes may only look and click. "safety.banned" is empty because I have no names that must stay off screen: do not ask me for any.

6. Run "bunx showcase theme check acme". It must pass. Do not change the theme unless it fails.
7. Follow the kwartz-showcase skill from here. Run "bunx showcase explore" and "bunx showcase plan", write the script first, then the scenes. The map's screenshots show only the top of each page: for something further down, scroll it into view in the scene before you click or highlight it. Choose the audience and the promise yourself, and tell me which you chose. I gave no call to action: end on the name of the product, with no next step.
8. Run "bunx showcase make --draft" until it prints no FAIL line, the length included, and frames from every scene look right. Then run "bunx showcase make". If the full render fails the length check, add or cut the words it says and run it again.
9. Look at frames from the finished video (take stills with ffmpeg): every scene, and every shape if there is more than one. A file named after a platform is a copy of a shape, not another shape. Report each check line with the value it measured.
10. You cannot hear the video. End by asking me to listen to it once before I share it.