The guide, as skills your agent can run
11 skills and a router that picks the right one.
Each carries the guide's rules, the costly ones first, each linked to its source.
For teams whose agent is doing the interface work.
Installing them
Each skill is a directory with a SKILL.md and a references folder, which is the layout the Agent Skills convention expects. Install the whole set, so the links between skills resolve, and point your agent at the router first. An agent that only has the web can start from /SKILL.md.
Step 1
Install the set
Copy every skill into your agent's skills folder, so the links between them resolve.
git clone https://github.com/vincemedia/connectwallet bitcoinsv.design
cp -r bitcoinsv.design/skills/* ~/.claude/skills/Step 2
Or start from the web
An agent that only has the web can load the router and follow its links.
curl https://www.bitcoinsv.design/SKILL.mdIf you would rather look things up mid-task than load a procedure, the same content answers as MCP tools at /mcp/, and the whole guide is markdown at /llms.txt.
Start here
bitcoinsv-design
The router matches a task to the right skill, by what the user is doing or by the BRC standard involved, and carries the patterns every BSV flow shares: payment states, loading labels, error messages, amounts, who is on the other end, fees, and what to say before anything irreversible.
The skills
Review a BSV product against the guide
Review a screen, a flow or a diff against the guide, costly findings first, every one citing its rule.
- 757 rules
- 113 can cost money
- 3 patterns
bsv-design-reviewConnect an app to a BSV wallet
Connect, permissions, allowances, sign-in and Passes: the app's half of the conversation with a wallet.
- 86 rules
- 5 can cost money
- 5 patterns
bsv-wallet-connectionCreate, sign and report BSV actions
createAction, signAction, abortAction and listActions, with descriptions people can read and states that tell the truth.
- 24 rules
- 2 can cost money
- 3 patterns
bsv-actionsSend and receive BSV payments
Paying a person, getting paid, and the review screen that is the last chance to catch a mistake.
- 100 rules
- 18 can cost money
- 5 patterns
bsv-paymentsCharge per use with BSV micropayments
Prices of a few sats, payment inside the request, and a running total the user can always see and stop.
- 46 rules
- 4 can cost money
- 3 patterns
bsv-micropaymentsLet software spend BSV on someone's behalf
A wallet of its own, limits it cannot argue with, and a report a person actually reads.
- 59 rules
- 12 can cost money
- 4 patterns
bsv-agent-spendingShow, receive and issue BSV tokens
A token is an output you hold. Show what it is, where it came from, and whether it is the real one.
- 9 rules
- 1 can cost money
- 4 patterns
bsv-tokensWrite data on the BSV chain with consent
Hash by default, say "permanent and public" before writing, and never offer a delete button.
- 10 rules
- 1 can cost money
- 3 patterns
bsv-on-chain-dataLock BSV behind keys, time or a secret
Multi-key, time locks with nLockTime and nSequence, and the configuration that has to be backed up with the keys.
- 50 rules
- 18 can cost money
- 3 patterns
bsv-script-conditionsWrite BSV amounts, units and interface copy
Units, formatting and the words on screen, where an amount off by a factor of a hundred million is a design bug.
- 50 rules
- 2 can cost money
- 3 patterns
bsv-amounts-and-copyDesign BSV wallet backup and recovery
The two halves of a BSV backup, the flow that gets both done, and a restore that says what came back.
- 85 rules
- 28 can cost money
- 4 patterns
bsv-backup-and-recovery
How they are made
A person writes the steps; the guide supplies the rules. Every rule is quoted straight from its page each time the site is built, so when the guide changes, the skills change with it. If they ever disagree, the build stops.