Preview access

This page isn't public yet. Enter your access code to continue.

← Back to home

Create decks with AI

Hand your notes, a PDF, or a codebase to an AI assistant and study the result on your phone tonight. SuperCards speaks the SuperCards Exchange Format — a documented JSON format any model can write — and imports the output as a native deck, layout and all.

Two official Claude integrations install in a couple of minutes. Every other assistant works today with the universal prompt below.

Recommended · Claude Desktop on macOS

Claude Desktop extension

The flagship integration: a one-click extension for Claude Desktop that connects Claude directly to the SuperCards app on your Mac. Ask for a deck and Claude checks its own output against SuperCards' real import validator, fixes what it got wrong, stages the finished bundle — images included — and hands it to the app. You review the deck in the import inbox and click once to add it to your Library. No files, no folders, no copy-paste.

Download the extension

SuperCards.mcpb · v1.0.0 · 172 KB · built July 2026

SHA-256: 6e59b0d3cf65ff879d1238c2ae438f48ec627499f63ac0a7f0e0856bc27ace5e

What you need

Install

  1. Download SuperCards.mcpb with the button above.
  2. In Claude Desktop, open Settings → Extensions. Depending on your Claude Desktop version this area may be labeled Connectors — the screenshots below are dated so you can tell whether your build matches.
  3. Drag SuperCards.mcpb onto the Extensions screen, or choose Install extension… and select the file. If neither appears — or the standard path refuses the package — use the fallback: Settings → Extensions → Advanced settings and install the file from there.
  4. Confirm the install when Claude Desktop shows the SuperCards extension details (an unsigned-package notice is expected — see the note below).
  5. Check it took: the extension lists four tools (get_spec, get_examples, validate_deck, submit_deck), and the SuperCards Home screen flips to Connected the first time Claude pings the app.

[Screenshot placeholder — Claude Desktop → Settings → Extensions with SuperCards installed · Claude Desktop 1.20, July 2026]

About the unsigned notice: the extension isn't code-signed yet — signing lands with our Apple developer-account changeover. The warning during install is expected for now. If you want certainty about what you're installing, verify your download against the SHA-256 above.

Your first deck

Start a new conversation, attach your source material, and ask for a deck — see the prompting tips for how to get a great one. Claude drafts, validates, fixes its own mistakes, and submits. SuperCards shows a quiet badge — it never steals focus — and the deck waits in the import inbox for your one-click review. SuperCards doesn't even need to be running: submitting a deck launches the app.

SuperCards import inbox modal showing an incoming deck with title, card count, and validation results
Every AI-made deck stops at the import inbox for your review · SuperCards 0.6, July 2026

If Claude says it couldn't read or attach a file, that's usually macOS privacy permissions, not a dead end. Import the deck anyway — the inbox lists exactly what's missing and gives you a drop zone to add those files yourself.

For claude.ai on the web

claude.ai Skill

Using Claude in the browser? The SuperCards Skill teaches claude.ai the format, the card-design guidance, and a pre-flight schema check it runs before handing you a file. Upload the Skill once in claude.ai's settings; from then on, ask for a deck and Claude delivers a single .supercards file that SuperCards imports whole — images bundled in.

Download the Skill

supercards-deck-authoring.zip · 22 KB · built July 2026 · don't unzip it

SHA-256: 621b8ab576e423689970a5cdf8fa42f33f355373df0d45c3443e8a0d5d91aa6f

What you need

  • A claude.ai account with the two settings toggles below available (if you don't see them, your plan may not include Skills yet)
  • SuperCards 0.6.1 or later on your Mac to import the result

Install

  1. Download supercards-deck-authoring.zip with the button above, and leave it zipped.
  2. In claude.ai, open Settings → Capabilities and turn on code execution and file creation (labels as of July 2026 — the dated screenshots below show where).
  3. In the same Capabilities area, find Skills, choose Upload skill, and select the zip.
  4. Confirm SuperCards deck authoring appears in your Skills list, toggled on.

[Screenshot placeholder — claude.ai → Settings → Capabilities: code-execution toggle + Skills upload · claude.ai, July 2026]

Your first deck

  1. Start a new chat, attach your source material — notes, a PDF, photos — and ask for a deck (the prompting tips apply here too).
  2. Claude drafts the deck and runs its pre-flight check, then hands you one .supercards file to download. Photo-heavy decks take longer and download bigger — the images are inside.
  3. Double-click the file — SuperCards opens with the deck waiting in the import inbox — or drag it onto the SuperCards window. Review, then click Import.

Prompting tips: ask like you'd brief a person

"Make me a deck from this document" works. Every model does markedly better when you spell out what you actually want:

  • Say what counts as one card. "One exercise per card," "one verb per card," "one API endpoint per card" — segmentation is the biggest quality lever there is.
  • Say how many. "All ~70 movements in the book" and "just the 20 I'd actually drill" are both great decks; leaving it unsaid is a coin flip.
  • Name the order. If sequence matters — chapters, steps, difficulty — say so. Card order survives import.
  • Steer emphasis and style. Definitions on fronts with mnemonics on backs, code on fronts with plain-English backs — whatever helps you remember, ask for it.
  • Attach the real files. Attaching your PDF or notes to the conversation beats describing them or pointing at a file path, every time. Say which images matter and where they belong.
  • Spot-check the cards, not the format. The built-in checks own the JSON; you own the judgment calls. Skim for cards that fused two ideas or split one — then ask Claude to fix exactly those.

Any other LLM: the universal prompt

ChatGPT, Gemini, a local model — anything that writes JSON can write a SuperCards deck. Copy the prompt, paste it into your assistant along with your source material, save the reply as a .supercards.json file, and import it with the desktop app.

I want you to create a deck of study notecards in the SuperCards Exchange Format (SEF).

First, read the format reference at https://www.supercards.io/sef/llms.txt — it defines the JSON structure, the markdown profile, and how to design good cards. If you can't browse the web, follow the fallback rules below instead.

Then turn the source material I give you into one deck:
- Output a single JSON code block and nothing else, so I can save it as {deck_name}.supercards.json
- One concept per card: the front asks or names, the back answers or explains
- 10-30 cards unless I say otherwise; fill in deck.source with where the content came from
- Only reference images you are sure exist (exact uploaded filenames or verified direct URLs)

Fallback rules (only if you couldn't read the reference):
- Root object: {"supercards_format": "1.1.0", "deck": {...}, "cards": [...]}
- deck: title (required), summary, source. Each card: front (required, at least 1 block) and optional back, both arrays of blocks
- Blocks: {"type": "text", "text": "...", "role": "heading|subheading|body|caption|label"} or {"type": "image", "src": "filename or https URL", "alt": "...", "size": "small|medium|large|full-width"} or {"type": "code", "code": "...", "language": "python"}
- Text is markdown by default: **bold**, *italic*, ==highlight==, inline code, lists, and fenced code blocks render. Markdown headings, links, and tables do not — use a separate block with role "heading" instead of # syntax
- No LaTeX or math blocks — write notation as plain text
- A single newline is a line break; a blank line starts a new paragraph

Here is my source material:
[PASTE YOUR NOTES, ARTICLE, OR TEXT HERE]

Prompt targets SEF format 1.1.0 · guidance revision 2026-07-05 · full reference at /sef/llms.txt

For toolmakers