Someone else’s working set.
A pack is one file carrying pads and, optionally, the look that goes with them. Installing one adds a deck beside what you already have — nothing of yours is replaced, and use counts never travel in either direction.
Cook
10 pads
The set that changes what a coding assistant gives back. Each pad forbids the thing a model does instead of the good answer, and says where the saved effort should go.
- Cook harder
- Finish it
- Debug it properly
- Prove it
- Read it first
- +5 more
Code
4 pads
Diff review, commit messages, tests and explanations — the four that read your clipboard.
- Review diff
- Commit msg
- Write tests
- Explain this
Everyday
3 pads
Shorter, plainer, less throat-clearing. For writing that is not code.
- Be concise
- Plain English
- Shorter
Shipping
8 pads · with a look
The same instincts aimed at a pull request, and the one pack that carries a look with it.
- Review this diff
- Root cause, not a patch
- Commit message
- PR description
- Tests that would catch it
- +3 more
No account, no review, no us.
A pack installs from any URL, so publishing one is hosting a file. There is no registry to be admitted to and no key to be issued — the link is the distribution.
- 01
Export it
On the board, Import / export → name it → Export pack. If the bridge is running, your theme travels with it. - 02
Put the file anywhere public
A GitHub gist, a raw file in a repo, object storage — anything that serves it over https and allows other sites to read it. Most do. - 03
Share the install link
promtly.dev/board?pack=<your-url>Anyone who opens it sees what they are about to get, and chooses pads-only or pads plus the look. Nothing installs silently.
Listing a pack here is editorial, not permission. If this page disappeared, every install link anyone has shared would keep working — which is the property worth protecting.