Sign in

Resource Library

Organize a sprawling body of material into one searchable library where finding the right asset takes seconds.

Pro moderate Knowledge Offers

What it adds

The builder indexes your full archive of assets and structures it into a browsable catalog with categories, tags, filters, and search — sold on retrieval speed rather than raw quantity. It converts because the pain being solved is navigational: buyers already have too much material and pay for the version they can actually find things in. The goal is a purchase of ongoing access to an organized index.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied archive files and produce a full inventory with type, topic, format, and use case for each asset.

  2. 2

    Derive the taxonomy from that inventory: a small number of top-level categories, a controlled tag vocabulary, and the filter dimensions that match how someone would search under time pressure.

  3. 3

    Sell retrieval, not volume. Lead with a working search-and-filter demonstration on the page so a buyer experiences the navigation before purchase.

  4. 4

    Show item counts per category and the date range of the collection so both breadth and currency are visible.

  5. 5

    Define the access model: whether the library is browse-only or downloadable, whether new items are added and how often, and what happens to access if a subscription lapses.

  6. 6

    Address the objection this format always faces — 'I already have too many resources' — by contrasting an indexed collection against scattered folders, using the taxonomy itself as the argument.

  7. 7

    Specify responsive behavior: on mobile search is the primary control with filters in a bottom sheet and results as single-column cards; on tablet show a filter rail beside a two-column result grid; on desktop use a persistent left filter sidebar, a three-column grid, and keyboard-accessible search focus.

  8. 8

    Finish with one action — get access — and keep search available to non-buyers with result titles visible and contents gated, so retrieval quality is provable before payment.

Edge cases it handles

5

The things an agent skips when you only say "build a resource library".
  • Assets carry inconsistent or missing metadata: normalize during indexing and flag items where topic or format had to be inferred.
  • Some assets are outdated but historically useful: tag them by date rather than removing them, and expose date as a filter dimension.
  • The archive is too small to justify filtering: reduce to categories only and drop the filter interface rather than shipping empty facets.
  • Duplicate assets exist across folders: deduplicate before publishing counts so the advertised total is accurate.
  • Additions are not on a schedule: describe the library as a fixed collection and remove any ongoing-additions language.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • A working search and filter experience is demonstrable on the page before purchase.
  • Every asset carries category, tags, format, and date drawn from the inventory.
  • Per-category item counts and the collection date range are displayed and accurate after deduplication.
  • Access, download, and lapse terms are stated or flagged as unresolved.
  • Mobile, tablet, and desktop navigation behaviors match the specification, including the desktop filter sidebar.
  • Items with inferred metadata are identifiable in the index.
  • The builder reports which archive files it indexed, and lists unresolved assumptions such as inferred metadata or unconfirmed update cadence.

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.