ai-automation-tools · open source · prompt templates

Prompt templates you can find, copy and keep.

Promptbook is a prompt-template manager you clone and run on your own machine. Browse a curated public library of prompts, agents, guides, skills and system prompts, then save, edit and organise your own in My Library, a folder of markdown files you own.

Browse the demo Source on GitHub Run it locally

The hosted demo is read-only: browse and copy anything. Run it locally to keep your own prompts. No account, no database.

Features

What it does

Two libraries behind one search box: a public one versioned in Git, and a personal one in a folder on your disk.

Public Library

Browse curated templates organised by section, category and subcategory, rendered from markdown. Copy any one into your own library.

library/ · Git-versioned

My Library

Create, edit, tag and delete your own prompts, or save any public one. Each is a markdown file, so you can sync it, version it in Git or edit it by hand.

markdown files · MY_LIBRARY_DIR

Search and ⌘K

Fuzzy search with Fuse.js, ranked so titles that start with or contain your query come first. A ⌘K palette reaches every prompt, section and action.

Fuse.js

Skill Packs

Curated bundles of related skills for a domain or workflow. Add a pack to My Library, or download the whole thing as a ZIP for offline use.

ZIP download

Use it from an agent

A built-in MCP server lets Claude Code, Codex or any MCP client search the library, read any item, pull a skill with its files and save to My Library. Featured prompts show up as slash commands.

MCP · stdio

Provenance you can check

Vendored skills and agents record their upstream source in frontmatter, and a weekly workflow reports any that have drifted behind it. It never edits content.

upstream-drift.yml

What's inside

Six library sections, plus Skill Packs

Each section is a numbered folder of markdown under site/library/. Skill Packs are served separately.

Prompts

Reusable prompt templates, organised by domain and task.

4_Prompts

Agents

Installable subagent definitions, ready to drop into .claude/agents/.

2_Agents

Guides

Setup and usage guides for the tools and providers the prompts target.

1_Guides

System Prompts

An archive of production system prompts, for study and reuse.

5_System_Prompts

Skills

SKILL.md bundles with their sample code, downloadable as a zip.

3_Skills

MCP Servers

Model Context Protocol servers worth installing, with verified install lines.

6_MCP_Servers

Skill Packs

Curated collections of skills for a domain or workflow.

api/skill-packs

How it works

One Express app, all files

Public content lives in files under Git; your own prompts live in files on your machine. The same Express app serves both, locally and as the read-only demo on Vercel.

Markdown in Git

The Public Library is markdown files in library/, so every change is a reviewed commit.

Index at build time

npm run build:index walks the library into api/prompt-index.json. CI fails a PR if the committed index is stale.

One API

api/index.ts is imported by server.ts when you run it locally and runs as a Vercel function for the demo. There is no second copy.

React front end

React 19, TypeScript, Vite 6 and Tailwind v4. Listings load metadata only; a prompt's body is fetched when you open it.

Every node links to the code it describes; Route and Lens trace paths. Open full screen ↗

Quick start

Run it locally

From the README. All you need is Node. Your prompts are saved to site/my-library/; set MY_LIBRARY_DIR to keep them somewhere else.

local development

# Clone the repository
$ git clone https://github.com/ai-automation-tools/promptbook.git
$ cd promptbook/site

# Install dependencies
$ npm install

# Start development server
$ npm run dev

# Visit http://localhost:3010 (npm start serves a production build instead)

checks (CI runs all of these)

$ npm run lint          # tsc --noEmit
$ npm run test:routes   # the API route table is intact
$ npm run test:my-library  # the My Library file store round-trips
$ npm run test:mcp      # the MCP server, end to end over stdio
$ npm run build:index   # rebuild api/prompt-index.json after editing library/

use it from an agent (MCP)

# After npm install in site/, point your agent at the server (absolute path to your clone)
$ claude mcp add my-prompt-library -- npm --prefix /path/to/my-prompt-library/site run --silent mcp

Resources

Links

The read-only demo, the source, and the documentation on the main branch.

DemoBrowse the librarymy-prompt-library-demo.ai-automation-tools.dev SourceGitHub repositoryai-automation-tools/promptbook StartREADMEfeatures, quick start, API DocsDocumentation indexevery guide in docs/ SetupSetup guidelocal development DeployDeployment guidethe read-only demo on Vercel DesignArchitecturesystem design, repo layout ReferenceAPI referenceREST endpoints FeatureSkill Packscreating and managing packs ContentContributing guidehow to add content ProvenanceUpstreamswhat the app depends on HistoryChangelogshipped work, newest first PlanRoadmapwhat's next PolicySecurityreporting a vulnerability FeedbackIssuesreport a bug or request a feature OrgMore toolsai-automation-tools.dev