Collect, reuse and share prompts and prompt templates
Updated by fix-consistency on 2026-09-06: - update .custodian-brief.md for canned-prompts Assistant: claude-code Assistant-Model: opus Assistant-Process: 388925@bnt-lap001 Assistant-Session: 3507023f-e0fd-4a1e-9d90-a0d4217d1502 |
||
|---|---|---|
| examples/pqrst-estimate | ||
| reference | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| CannedPromptFormat-v0.1.md | ||
| INTENT.md | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
canned-prompts seed
Collect, reuse and share prompts and prompt templates.
This bundle contains a first project seed for canned-prompts:
INTENT.md— project mission, boundaries, principles, and success criteria.CannedPromptFormat-v0.1.md— experimental package-format specification.reference/— deliberately small Python CLI implementing the basic lifecycle.examples/pqrst-estimate/— a real package that can be used to exercise the implementation.
Try the reference implementation
cd reference
python -m venv .venv
. .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -r requirements.txt
# add the included example to your local catalog
python canned_prompts.py add ../examples/pqrst-estimate
# find and inspect it
python canned_prompts.py search pqrst
python canned_prompts.py show practice/pqrst-estimate
# render it
python canned_prompts.py render practice/pqrst-estimate \
--set session_summary="Implemented feature X, read unfamiliar code, added tests."
# publish it to the local filesystem registry
python canned_prompts.py publish ../examples/pqrst-estimate
# remove the local catalog if you want to simulate another machine, then install
python canned_prompts.py install practice/pqrst-estimate --version 0.1.0
By default the reference tool uses:
~/.canned-prompts/catalog
~/.canned-prompts/registry
Override them with:
CANNED_PROMPTS_HOME=/some/path
or command-level --catalog / --registry options.
Deliberate limitations
This seed has no hosted registry, model execution, authentication, network access, dependency resolver, or social features. publish and install operate on a filesystem registry so that the package semantics can be tested before infrastructure is built around them.