What problem does it solve? TypeScript developers integrating Algorand payments via the x402 protocol face a modular @x402-avm/* package ecosystem with role-specific signer interfaces, subpath-based scheme registration, and network constants that are easy to misuse. This Skill explains the package structure, signer implementations, and registration patterns so developers can wire up client, server, and facilitator components correctly. ## Core Features & Use Cases - Package Ecosystem Guidance: Maps each @x402-avm package (core, avm, express, hono, next, fetch, axios, paywall, extensions) to its role and key exports. - Signer Implementation Patterns: Shows how to implement ClientAvmSigner with @txnlab/use-wallet or algosdk private keys, and FacilitatorAvmSigner with simulation, submission, and confirmation methods. - Scheme Registration & Troubleshooting: Covers registerExactAvmScheme subpaths per role, CAIP-2 network constants, utility functions, and a table of common errors with fixes. - Use Case: A developer building an Express API that charges USDC on Algorand testnet can follow the workflow to install packages, register the AVM scheme on an x402ResourceServer, and gate routes with paymentMiddleware. ## Quick Start Ask the assistant to explain how to register the AVM scheme and implement a ClientAvmSigner for a TypeScript client using @x402-avm packages.