← Browse Buildprints

Submit

Submit Buildprint.

If you already have a Buildprint package in GitHub, add it as a scanned Community listing. If you only have a normal project, copy Buildprint Mapper first.

1
Normal project?

Make it a Buildprint first.

Copy this prompt into your coding agent inside the project repo. It creates the Buildprint package files, including the canonical start and manifest metadata that other agents can use.

Buildprint Mapper prompt Open prompt 
Use the Agent Buildprint at https://agent-buildprint.com/buildprints/buildprint-mapper-os/agent.md.

Fetch https://agent-buildprint.com/buildprints/buildprint-mapper-os/package.json.
Read order: `BUILDPRINT.md`.
Do not scrape human cards. Use this manifest, agent.md, and raw files. BUILDPRINT.md is the canonical start file and owns the required read order, phase gates, and acceptance gates. Structured control files are machine-readable mirrors only.
Follow alignment/question rules before implementation.
Do not scrape human UI cards.

First bootstrap exact snapshots: agb start https://agent-buildprint.com/buildprints/buildprint-mapper-os/package.json .
If agb is not installed, clone https://github.com/DomEscobar/agent-buildprint and run node agent-buildprint/bin/agb.js start https://agent-buildprint.com/buildprints/buildprint-mapper-os/package.json .
Then read .buildprint/next-agent.md and continue. Do not write Buildprint snapshots manually.

If the Buildprint requires it, finish with a chat handover summarizing outcome, evidence, known gaps, and recommended next direction.
See Buildprint Mapper
2
Have the URL?

Add a GitHub listing.

Paste a GitHub repo or folder that contains a Buildprint package, ideally BUILDPRINT.md plus package.json with canonical read order. It appears immediately as a Community listing that links back to GitHub; official site-hosted packages are created only after review/import.

Only a GitHub URL is required. Sign in with GitHub first so you can remove the listing later from your profile.