Build prompts in public.
Publish your prompts, fork what works, improve them together, and keep the evidence attached to the exact version it was measured against.
Versioned
Every meaningful change has history, authorship, and a diff.
Collaborative
Fork, propose changes, review, comment, and merge.
Evidence-based
Every version has an immutable commit sha, so evidence can be pinned to exactly what was tested — not to a moving target.
Portable
Export plain repositories and self-host without a proprietary control plane.
Open
AGPL core, open schemas, and explicit prompt licensing.
BI-native
Creation, reuse and collaboration are measured from an append-only event ledger, not inferred after the fact.
How versioning and forks work
The same loop software collaboration has had for twenty years, applied to the artefact that is actually running in production: the prompt.
- 01
Publish
A prompt repository is a plain directory with a prompt.yaml manifest — a name, a licence, the prompt itself, and whatever evidence you have. Nothing proprietary.
- 02
Fork
Forking keeps durable upstream lineage, so a prompt three generations downstream can still be traced to where it came from.
- 03
Propose
Changes arrive as proposals against a specific version, with a rendered diff of the prompt text rather than an opaque paste.
- 04
Merge
A merge records an immutable version with a real commit sha. That sha is what evaluations, citations, and rollbacks point at.
Recently improved
Browse allPublic repositories with a new version. Ordered by when they last changed — not by popularity, which this platform deliberately keeps as a separate signal.
Verification check
CC-BY-4.0maxwell/verification-check
Turn a claim about a system into a check that could actually fail.
Updated 3 weeks ago
hello-world
CC-BY-4.0maxwell/hello-world
The smallest possible prompt: greet someone by name. A worked example of the manifest, and a way to verify a repository end to end.
Updated 1 month ago
Who this is for
- Creators
- Build a reputation around useful, well-maintained prompts.
- Teams
- Replace scattered prompt documents with governed, reviewable repositories.
- Evaluators
- Connect claims to repeatable evidence.
- Self-hosters
- Run the full collaboration loop on your own infrastructure.
Open, and portable on purpose
The server and this web application are AGPL-3.0-or-later. There is no hosted-service dependency for login, mail, storage, search, analytics, or the collaboration loop itself — every external service has a documented adapter and a local default, so a self-hosted deployment is the same software rather than a reduced edition.
Repositories export as plain directories. Nothing you publish here is trapped here.
What we commit to
- Prompt licences are visible before you reuse anything.
- Popularity and quality are separate signals, and are never merged into one score.
- Private inputs and outputs are not published by default.
- Identity is standards-based OIDC — independent deployments may use any compliant provider.
The policies behind these are on the policies page, including the ones still open.
Where this is today
Active incubation. Publishing, forking, proposing, reviewing, merging, versioned diffs, licence metadata, abuse reporting, account export and deletion all work. Evaluation result ingestion, follows and collections, and federation are on the roadmap and are not built. We would rather you read that here than discover it on your second click.