Building Adapters with AI

XRPL Wallet Kit includes an adapter developer skill: an agent-readable guide for mapping wallet provider APIs to the Kit contract on XRPL and Xahau. Pair it with the provider documentation and current source; generated adapters still need review and wallet acceptance checks.

Start from the project skill

The skill covers capabilities, chain filters, native sign-in, protocol-aware signing, session restore and cleanup. It guides implementation; it does not establish that a wallet supports an operation or replace verification.

What the skill contains

The skill entry point is:

skills/xrpl-wallet-kit-adapter-developer/SKILL.md

It is written to be agent-readable — structured prose that any coding AI can follow without requiring specific tool support. It covers:

• The full WalletAdapter interface — every required and optional method with semantics
• Capability rules — when signMessage, native signIn, signTransaction, signAndSubmit, payments, nftOffers may be declared
• Chain support — supportedChains, non-XRPL protocol preparation, signed-intent verification and fee ceilings
• Error mapping — which WalletKitErrorCode applies to each failure case
• Session restore rules — when restoreSession() is safe to implement vs when to return null
• Cleanup requirements — WalletConnect proposals, focus/visibility listeners, deeplink timers, storage markers
• Transaction normalization — how to handle hash, txHash, tx_hash, transactionHash, nested response shapes
• Hard rules — no business logic, no UI code, no secrets inside adapters
• Validation commands to run before every commit

Plus companion reference files:

File	Contents
references/adapter-checklist.md	Pre-PR review checklist (20+ items)
references/walletconnect-wallet.md	How to add a WalletConnect wallet definition
references/hardware-adapters.md	Ledger / WebHID / WebUSB notes
references/chain-support.md	XRPL/Xahau chain declarations and protocol-aware signing
references/adapter-docs.md	Common public guide structure, capability tables and transaction snippets
references/scaffold.md	Steps for creating a new official monorepo package
references/test-template.md	Node test runner scaffold for adapter tests
templates/adapter-package/	Copy-paste starter package

---

Activating the skill

Claude Code

/xrpl-wallet-kit-adapter-developer

Run this slash command at the start of your session. The skill is pre-installed in the monorepo at skills/xrpl-wallet-kit-adapter-developer/. Claude Code reads SKILL.md and follows the workflow automatically.

Codex (OpenAI)

Ask the agent to read the project skill and the relevant references:

Read skills/xrpl-wallet-kit-adapter-developer/SKILL.md in this repository.
Implement an adapter for MyWallet using its official provider documentation.
Follow references/chain-support.md for XRPL/Xahau support and
references/adapter-docs.md for the public guide.

Other AI agents

Any agent that can read a markdown file can use the skill. Point it at SKILL.md directly or paste the contents as system context.

---

Workflow: building an adapter with AI

Follow this sequence for best results:

Step 1 — Gather the wallet's documentation

Collect the wallet's injected API docs, SDK README, or provider reference. A URL, a pasted README, or a screenshot all work. The more complete the docs, the better the output.

Step 2 — Activate the skill

/xrpl-wallet-kit-adapter-developer

Step 3 — Describe the wallet to the agent

Give the AI a prompt like:

Build a WalletAdapter for MyWallet using this documentation:

The wallet injects window.myWallet with:

• connect() → { address, publicKey }
• disconnect()
• signTransaction(tx) → { blob }
• signMessage(msg) → { signature, publicKey }

It is a browser extension. Use the adapter skill rules.

Step 4 — Review the output

The AI should produce:

• A factory function createMyWalletAdapter(options)
• Accurate capability flags (e.g. signMessage: true only because it is implemented)
• WalletKitError with the correct error code for every failure path
• isAvailable() that reads window.myWallet without throwing
• restoreSession() that reads passive provider state only — no connect() call inside it

Step 5 — Run validation

npm.cmd run typecheck
npm.cmd test
npm.cmd run build:browser

Step 6 — Manual smoke test

The skill's checklist prompts you to verify:

• Wallet not installed → correct error
• Connect prompt → user approves + user cancels
• Sign request → user approves + user rejects
• Session restore after page reload
• Disconnect clears session cleanly

---

Example prompts

These prompts work well with Claude Code after activating the skill:

New browser extension:

"Build a native Joey Wallet extension adapter using its official SDK and documented provider APIs. Keep it separate from Joey WalletConnect. Use the adapter skill."

WalletConnect wallet definition:

"Add BitgetWallet to the WalletConnect adapter's wallet list. The wallet supports EIP-155 and XRPL chains. AppStore ID: 1639703499, Play Store package: com.bitget.wallet. Icon URL: [url]. Use the walletconnect-wallet reference from the skill."

Mobile deeplink wallet:

"Build a mobile deeplink adapter for WalletX. It uses a custom URI scheme walletx://. QR code flow on desktop, deeplink on mobile. Add guarded recoverSession() for a pending deeplink return and passive restoreSession() for stored sessions. Use the adapter skill rules for mobile flows."

Reviewing a contribution:

"Review this adapter PR against the XRPL Wallet Kit adapter contract. Check capabilities, error codes, cleanup, and session restoration correctness. Use the adapter checklist from the skill."

---

What the skill prevents

When the skill is active, the AI automatically refuses to:

Anti-pattern	What the skill enforces instead
Hardcode projectId or API keys	Always require caller injection via options
Add signAuthPayload to the adapter	Belongs in the app layer, never the SDK
Inject modals, alerts, or React	Adapters are pure TypeScript with no UI
Set signMessage: true before implementing it	Capabilities must match actual method implementations
Return null silently on user cancel	Must throw WalletKitErrorCode.SIGN_REJECTED
Leave stale WalletConnect proposals/pairings	Clean up using the provider's supported lifecycle APIs
Call connect() inside restoreSession()	restoreSession() is passive-only
Submit a transaction inside signTransaction()	Must sign only, never submit

---

Contract and Chain Safety

Use the same contract for extension, popup, mobile and hardware adapters. Validate it with assertWalletAdapter() and keep public capabilities aligned with the implementation. For Xahau, a working XRPL connection does not establish chain support: declare the filter, register the protocol and preserve fields such as NetworkID and HookParameters through signing.

---

Extending the skill

If building outside this monorepo, provide the skill directory with its reference files and inspect the installed core's current types. The scaffold is a starting point, not a validated provider implementation.

For contributions to the official adapter set, read the scaffold guide:

skills/xrpl-wallet-kit-adapter-developer/references/scaffold.md

It walks through creating a new package under packages/adapters/<id>/, wiring it into packages/client/, and registering it in the browser bundle.