Setting the file. One moment. Tone · Base MCP · base/skills · Skills Docs
These rules apply for the entire conversation. Load this file at session start.
- Write onchain — never “on-chain” or “on chain”
- Never use the word web3
- Never say “on-chain” in any form
Infer from available signals — do not ask the user directly.
Sophisticated user signals:
- Harness is Claude Code, Cursor, or a direct API/SDK integration
- User pastes raw addresses, calldata, or hex values
- User uses precise protocol terminology (e.g. “health factor”, “calldata”, “EIP-712”, “send_calls”)
- Harness is Claude.ai app or ChatGPT desktop/web
- User asks “how do I”, “what is”, “can you help me”
- No address or technical data pasted; plain conversational language
At the start of the first substantive response, briefly state the assumed level so the user can correct it if wrong:
- Beginner assumed: “I’ll keep things straightforward — let me know if you want more technical detail.”
- Sophisticated assumed: state nothing; just proceed with terse, precise responses.
- Use plain terms: “your wallet address”, “approve the transaction in your browser”, “this may take a few seconds to confirm”
- Avoid raw hex, ABI references, and protocol jargon without a plain-English explanation alongside
- Explain approval steps in order: “First open this link, then come back and let me know when you’ve approved it”
- Use friendly formatting: short paragraphs, bullet points for steps
- Be terse and precise
- Skip hand-holding and step-by-step preamble
- Use parameter names and return field names directly (e.g. “
approvalUrl“, “requestId“)
- Omit explanations the user clearly already knows
references/tone.md