Agent skill · software engineering · jeremylongshore
alchemy-reference-architecture
Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations. Use when reviewing or creating an Alchemy-backed system. Trigger with "Alchemy architecture", "design an Alchemy dApp backend", or "review Alchemy boundaries".
Why this skill is useful
Adds a comprehensive reference architecture with executable code examples and design patterns specific to Alchemy and Web3 applications.
What it needs
Requires alchemy-sdk, hardhat installed locally. Requires alchemy account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Alchemy Production Reference Architecture Overview Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations. This workflow produces a reviewable artifact and negative-path evidence before any live side effect. Prerequisites Current first-party Alchemy documentation for the selected product, chain, feature, client, authentication method, limit, and lifecycle. Named product, application, security, data/privacy, budget, release, and operations owners appropriate to the requested scope. Synthetic or approved non-production fixtures, a credential canary, explicit success criteria, and a tested rollback boundary. Current Contract Current architecture separates EVM RPC through viem, Data APIs through typed HTTP adapters, Wallet APIs v5 through a transaction-policy boundary, Notify intake through authenticated idempotent queues, and Admin usage through restricted operations tooling. No shared archived SDK client or credential should collapse these contracts. Authentication Model browser, edge, API, worker, webhook, Admin, and signer identities separately. Application keys may serve permitted reads; Admin access keys, Notify tokens, webhook signing keys, and wallet signing authority remain isolated by runtime, owner, and policy. Instructions 1. Inventory user journeys, data ownership, chains, Node/Data/Portfolio/Wallet/Notify/Admin capabilities, writes, callbacks, SLOs, and regulatory constraints. 2. Draw trust and data-flow boundaries including browser access, server adapters, queue, cache, database, secret store, observability, signer, provider, and external metadata. 3. Define typed capability adapters with chain assertions, pagination, partial success, finality, idempotency, bounded retry, and unsupported-feature outcomes. 4. Keep read paths and transaction intent/signing paths separate; require simulation, policy, user consent, and audit receipts for writes. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/alchemy-reference-architecture