Connect Claude to SuperCards

Two official Claude integrations ship with SuperCards: a Claude Desktop extension that gives Claude a direct line to the app on your Mac, and a claude.ai Skill for Claude in the browser. Both install once, from the Connect page. This guide covers what each one does and how the workflow feels; the install packages and step-by-step setup live on the Connect page.

Claude Desktop extension (recommended)

The extension connects Claude Desktop to the SuperCards app on your Mac. Once it's installed, deck creation is just a conversation:

1. Ask Claude for a deck — "turn this PDF into a study deck", "make me 20 cards on this codebase"
2. Claude drafts the deck using the format reference and card-design guidance built into the extension, then checks its own output against SuperCards' real import validator — the exact code that guards your Library — and fixes anything it got wrong before you ever see it
3. Claude stages the finished bundle, images and source files included, and hands it to SuperCards
4. SuperCards quietly flags the incoming deck — review it in the import inbox and click Import

No files to download, no folders to assemble, no copy-paste — SuperCards doesn't even need to be running, since a submitted deck launches the app. Once the extension is set up, the app's Home screen switches to Connected mode with example recipes to try. Install it from the Connect page.

claude.ai Skill (Claude in the browser)

The Skill teaches claude.ai the SuperCards format: the schema, the card-design guidance, and a pre-flight check Claude runs on its own drafts before handing you anything.

1. Download the Skill from the Connect page and upload it once in claude.ai's settings
2. Ask Claude for a deck — it drafts, checks, and gives you a single downloadable file
3. Double-click the file (or drag it onto SuperCards) and confirm the import in the inbox

If you upload images in the chat, claude.ai bundles them with the deck into one self-contained file — photo decks work end to end from the browser.

Getting better decks

Both paths reward the same habit: brief Claude like you'd brief a person. Say what counts as one card, how many cards you want, what order matters, and what to emphasize — and attach the real source files instead of describing them. The prompting tips on the Connect page collect what works.

Which one should I use?

If you use Claude Desktop — or are willing to install it — use the extension: it's the smoothest path, and the validation loop means imports essentially never fail. Use the Skill when you prefer working at claude.ai in the browser. The two don't conflict, and the Skill even tells Claude to hand off to the extension when both are available.