A prompt collection where the newest file wins is an inventory. This is an asset.

You have prompts. They live in a Slack thread, three Google Docs, and one person’s head. Nobody can tell you which version is current, who owns it, or what it does badly — so every hand-off starts from scratch and the craft never compounds.

The Marketing Template Library is the fix, and it runs on your own machine. Sixty-five governed marketing templates, the schema they all obey, and a quality gate that refuses a template which does not meet the bar. You buy it once, you install it in five minutes, and it is yours.

Individual

$100

One-off · yours to keep

One named person — their own work and their own clients.

• The solo library — one canon, no approval overhead
• All 65 templates, in six job-to-be-done folders
• Every script, the quality gate, and the registry
• The Claude Code slash commands

Buy Individual

Complete

$549

One-off · both editions

Both editions, for one organisation.

• Everything in Individual and Team
• Start solo, move the team across when you are ready
• Both archives on one licence — $51 less than buying them separately
• The edition the set-up service installs

Buy Complete

Team

$500

One-off · yours to keep

One organisation, unlimited internal seats.

• The team library — canonical, personal, and graduating tiers
• A promotion gate with a named approver
• Ownership records and the orphaned-entry audit
• No seat count to track and no per-seat fee

Buy Team

Support until AGI arrives — every future release of the edition you buy, no renewal fee and no upgrade fee. You create an account (or sign in), then pay; Lemon Squeezy is the merchant of record and VAT is included.

The gate is the product

Anyone can collect prompts. What makes a collection compound is the thing that stops a weak entry getting in.

A template only enters this library if it passes validate.py:

• Every {variable} in the prompt body is declared in inputs, and every declared input is used in the body.
• A real worked example, with values a person could actually paste — not a placeholder.
• Four to six failure modes, each naming a diagnosable shape. “Vague core_message produces interchangeable headlines” passes. “Output may be wrong” does not.
• A semantic version, a valid lifecycle status, and a named owner.

The gate exits non-zero on any failure, so it can guard a commit. That is the whole product philosophy in one script: the discipline is enforced mechanically, not remembered.

What is inside

Sixty-five templates, filed by the job they do rather than by date, model, or client:

Folder	Templates	What lives here
ops/	18	Working practice, prompt primitives, marketing ops, AI stack
content/	13	Blog briefs and drafts, social, SEO
copy/	13	Ad creative, email, paid campaigns
research/	9	Market research, customer insight, interview synthesis
governance/	8	Positioning, brand voice, policy, ROI measurement
analytics/	4	Reporting, insight-to-decision, executive narrative

Around them sits the operating system: stable IDs, semantic versioning, a registry regenerated from source, named ownership, a promotion gate between personal and canonical entries, and usage telemetry. Templates name model classes — frontier, mid-class, small-fast — never model IDs, so the library outlives any particular model.

The bundled Claude Code slash commands wrap the daily loop: /gate, /new-template, /library-status, /audit. The library is files and scripts, operated from your terminal or from Claude Code.

Install in five minutes

bash install.sh          # creates .venv, installs PyYAML, runs the gate
make configure           # your name, your mode, your Drive folder
make doctor              # confirms the environment

Python 3.9 or newer is the only prerequisite. No API key, no account, no external service — the core installation calls nothing. Windows runs install.ps1 instead.

make configure stamps your name on the templates you author and records where your generated artefacts are filed. The library itself lives in git on a local path; the outputs go to Google Drive. Those two stores stay separate on purpose, and the docs explain why.

How this differs from the subscription

Both exist, and neither replaces the other.

A subscription does not include a licence, and a licence does not include the Playbook. Plenty of people want only one of them.

Your licence, in plain English

Use it commercially without limit, for your own business and for clients you serve. Modify anything — templates, scripts, the schema. Everything you generate is yours, with no attribution required. Store it in private repositories, private Drive, your own CI.

What you may not do is resell, sublicense, or republish the library itself, publish the templates publicly, or use it to build a competing prompt product. An Individual licence covers one named person; a Team licence covers one organisation with unlimited internal seats. An agency serving many clients needs one Team licence, not one per client.

The full terms ship as LICENSE.md inside the archive, and the governing law is South African.

Support until AGI arrives

Every future release of the edition you bought is included: no renewal fee, no upgrade fee, no access period that lapses. Questions about installing, configuring, and operating the library are answered for as long as the library is published.

Updates arrive as a fresh archive on your library page, or as a git pull if you take the private repository invite. UPGRADING.md covers taking a new release without losing the templates you have written yourself.

Want it installed for you?

The set-up service does the whole thing with you: the library installed, your Google Drive artefacts store configured, a private GitHub repository, Claude Code wired up, and a working session with your team. The Complete licence is included in the fee.

See the set-up service