Free Field Guide · Orcalynx

You describe it. Claude builds it.

No design software. No templates. You explain the carousel in plain English, Claude Code writes every slide as real code, and you shape it with feedback until it looks like you made it. This field guide walks you through the whole system: the setup, the build loop, the saved styles, and the rules that make a deck worth posting.

Section 01

The mental model

Claude Code is a workspace that lives in a folder on your computer. You talk to it in plain language, like briefing a designer sitting next to you. That is the whole interface. No canvas, no layers panel, no font picker.

The shift: you steer with words, not menus. You never pick fonts or drag boxes. You say “make the hook bigger” or “swap the cover photo for my portrait” and Claude rewrites the slides. Every carousel is a small web page, one html file with one slide per screen at 1080 by 1350. That is why it can be edited infinitely and exported as crisp images.

Section 02

One time setup

Get Claude Code as the desktop app, the terminal tool, or the VS Code extension. Then open a carousel project folder. The folder is the memory of the system. Four pieces inside it make the output feel like you, not generic AI.

Set these up once. Every future carousel inherits them automatically. Click through the tree below to see what each piece does.

# Voice

- Speak as "we and our clients", never "I"
- Never write "follow for more".
  Always "follow @yourhandle"
- CTA is a comment keyword: "comment HOOKS"
- Lead with specifics. "388K in 18 months",
  not "huge growth"

Section 03

Your first carousel

Two ways in. Both start with a sentence. Either way, Claude picks a framework, picks a hook, tells you the angle it chose, then builds the slides and drafts the caption. You review. You never wait and hope.

Make a dark carousel about why most reels flop, for service based business owners.

/carousel why your reels aren't getting views

Section 04

The build loop. The actual skill

Everything else in this guide is setup. This is the part you do every time: six moves, repeated until the deck looks right. Play it through below, then steal the habit that makes it fast.

Section 05

Skills. Why output stays on brand

A skill is a saved instruction file that encodes an entire look and rulebook: colors, fonts, layout, voice, CTA style. Once it exists, you never describe that style again. You just name it.

The first time, you build one carousel you love by iterating. Then you say “save this style as a skill.” After that, “make a dark carousel about X” comes out on brand every single time. Here is an example library.

Section 06

What makes a carousel good

Claude can build anything you describe. These rules decide whether what you describe is worth posting. Bake them into your voice.md and your skills so every deck follows them by default.

Section 07

The power tools

None of these are needed to start. All of them live in the same conversation, so the whole pipeline, research to render, never leaves one window.

Section 08

Do this now

Ship one carousel in ten minutes. Then make the highest leverage move in this entire guide: when a deck finally looks exactly right, say “save this as a skill” and never describe that style again.