Sign in

Swipe File Offer

Collect real-world examples worth copying and annotate exactly why each one works, so buyers borrow judgment not just files.

Pro involved Knowledge Offers

What it adds

The builder curates your collected examples into a categorized reference where every entry carries an annotation explaining the specific mechanic that makes it effective and when to reuse it. It converts on curation and commentary — raw examples are freely available, but the judgment layer is not. The goal is a single purchase of a reference buyers return to whenever they face a blank page.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied examples and notes. Catalog each example with its format, the situation it addresses, and any existing commentary attached to it.

  2. 2

    Establish the annotation standard every entry must meet: the technique in play, why it works structurally, and when it would be the wrong choice. Apply it uniformly.

  3. 3

    Organize by situation rather than by source or date, because buyers arrive with a problem — a headline to write, a sequence to structure — not a browsing intention.

  4. 4

    Show two or three fully annotated entries publicly as the sample. The annotation depth on those samples is what sells the rest.

  5. 5

    State the collection size, the situation categories covered, and the date range so buyers can judge both breadth and currency before purchasing.

  6. 6

    Handle sourcing and rights carefully: describe each example's origin only as the sources support, do not imply any relationship with or endorsement by whoever created it, and exclude anything the sources do not confirm you may reproduce.

  7. 7

    Specify responsive behavior: on mobile each entry is a card with the example collapsed above its annotation and a situation filter in a bottom sheet; on tablet show example and annotation side by side within each card; on desktop use a two-pane reader with the situation index on the left and the annotated entry on the right.

  8. 8

    Close with one action — get the swipe file — with the entry count and category count stated immediately above it.

Edge cases it handles

5

The things an agent skips when you only say "build a swipe file offer".
  • An example lacks commentary in the sources: either write an annotation grounded in observable structure or exclude the entry, and record which was done.
  • Reproduction rights for an example are unclear: describe the technique without reproducing the asset.
  • Examples cluster heavily in one situation category: show the real distribution rather than implying even coverage.
  • Some examples are dated in ways that affect applicability: mark them as period examples and explain what still transfers.
  • Multiple examples demonstrate the identical technique: keep the clearest and note the redundancy rather than inflating the count.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Every entry carries an annotation covering technique, why it works, and when not to use it.
  • Entries are organized by situation, with the category list visible before purchase.
  • At least two fully annotated sample entries are viewable without purchase.
  • Advertised entry count matches the catalog after any exclusions or merges.
  • Mobile, tablet, and desktop presentations match the specified behavior, including the desktop two-pane reader.
  • No example implies endorsement by, or relationship with, whoever originally created it.
  • The builder reports which example and commentary files it used, and lists unresolved assumptions including rights-unclear exclusions.

Related offer files

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.