Submit a free Buildprint.
Creators can submit reusable Buildprints for products, features, architectures, workflows, and integrations. Submissions are verified before they appear in the registry.
Converting an existing repo? Start with Mapper OS.
Mapper OS is the canonical workflow for turning a working codebase into scoped Buildprint candidates, selecting one, extracting a source-independent package, and recording proof-ledger evidence. Use that page instead of copying a stale submission prompt.
GitHub is the first identity and review layer.
No marketplace auth yet. For now, creator identity comes from the GitHub account/repo that submits the package, and every Buildprint is reviewed before listing.
Map or discover scope
For existing repos, use Mapper OS to produce scoped candidates before extraction. No separate mapper CLI is required.
Extract selected Buildprint
Create one scoped package, or a hierarchical System Buildprint with modules. Avoid whole-repo sludge.
Submit for review
Open a GitHub issue with repo URL, package path, creator profile, license, scope, and checklist.
my-buildprint/
BUILDPRINT.md # architecture / intent
SPEC.md # behavior, if applicable
PLAN.md # execution plan
CONTRACTS.md # interfaces/data contracts
EXECUTION_PROTOCOL.md # agent execution rules
IMPLEMENTATION_PLAN.md # implementation roadmap
VERIFICATION.md # checks and evidence
prompts/
policies/
tests/
examples/ - Package has a clear build outcome
- Required files are present for its tier
- No secrets, tokens, or private data
- Links and package manifest resolve
- Quality gates are concrete, not vibes
- License and creator/source are clear
Stars and requests use GitHub first. That keeps early demand signals tied to real accounts without building a full auth system yet.