distributions/direct/example/blockchain-integration-builder/SKILL.md
Design and implement blockchain integrations across chains and frameworks with emphasis on patterns over specific technologies. Use when building Web3 applications, smart contract systems, token mechanics, decentralized identity, or blockchain-verified data. Triggers on blockchain architecture, smart contract design, Web3 integration, token systems, or decentralized application development. Framework-agnostic—applies to Ethereum, Solana, or emerging chains.
npx skillsauth add a-organvm/a-i--skills blockchain-integration-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design blockchain systems using universal patterns applicable across chains.
Blockchain-agnostic thinking: focus on what you're trying to achieve, then select chain/framework.
| Primitive | What It Is | Chain Examples | |-----------|------------|----------------| | Account | Identity with balance | EOA (Eth), Wallet (Solana), Account (Near) | | Transaction | State change request | Signed message + gas | | Block | Batch of transactions | Time-ordered, immutable | | Contract | On-chain program | Solidity, Rust, Move | | Event/Log | Indexed side-effect | Emitted by contracts, queryable | | State | Persistent data | Mappings, storage slots |
| Need | Consider | Why | |------|----------|-----| | Programmability | Ethereum, Arbitrum, Base | Mature tooling, EVM ecosystem | | Speed/Cost | Solana, Sui, Aptos | High throughput, low fees | | Privacy | Aztec, Zcash | Zero-knowledge proofs | | Interoperability | Cosmos, Polkadot | Cross-chain communication | | Simplicity | Bitcoin, Litecoin | Limited scripting, proven security |
Wallet-Based Identity
User → Wallet → Sign Message → Verify Signature → Authenticated
Soul-Bound Tokens (SBTs)
Issuer → Mint SBT → User Wallet (non-transferable)
Decentralized Identifiers (DIDs)
did:method:identifier → Resolve → DID Document → Public Keys, Services
Fungible Tokens (ERC-20 pattern)
// Universal interface
balanceOf(address) → uint256
transfer(to, amount) → bool
approve(spender, amount) → bool
transferFrom(from, to, amount) → bool
Non-Fungible Tokens (ERC-721 pattern)
// Universal interface
ownerOf(tokenId) → address
transferFrom(from, to, tokenId)
tokenURI(tokenId) → string (metadata)
Semi-Fungible (ERC-1155 pattern)
// Batch operations, mixed fungible/non-fungible
balanceOf(account, id) → uint256
balanceOfBatch(accounts[], ids[]) → uint256[]
safeTransferFrom(from, to, id, amount, data)
Token Voting
Proposal → Snapshot Balances → Vote Period → Tally → Execute (if passed)
Quadratic Voting
Cost of N votes = N² tokens
Reduces plutocratic dominance
Optimistic Governance
Proposal → Challenge Period → Execute if unchallenged
Bonding Curves
Price = f(Supply)
Buy: Price increases with supply
Sell: Price decreases with supply
Creates automatic market making
Staking/Slashing
Stake tokens → Perform duties → Earn rewards
Misbehave → Lose stake (slashing)
Streaming Payments
Deposit → Linear unlock over time → Recipient claims
| Aspect | On-Chain | Off-Chain | |--------|----------|-----------| | Cost | High (gas fees) | Low/free | | Speed | Slow (block time) | Fast | | Trust | Trustless | Requires trust | | Privacy | Public | Can be private | | Storage | Expensive | Cheap |
Hybrid approach:
Off-chain: Computation, storage, user experience
On-chain: Verification, settlement, ownership
Bridge: Oracles, merkle proofs, signatures
Blockchain data is hard to query directly. Use indexers:
Blockchain → Events → Indexer → Database → API → Frontend
Tools: The Graph, Goldsky, custom indexers
Bring external data on-chain:
External Data → Oracle Network → Consensus → On-chain Value
Use cases: Price feeds, random numbers, API data
| Vulnerability | Description | Prevention | |---------------|-------------|------------| | Reentrancy | Recursive calls drain funds | Checks-effects-interactions | | Integer overflow | Math wraps around | SafeMath or Solidity 0.8+ | | Front-running | Miners/validators see pending txs | Commit-reveal, flashbots | | Oracle manipulation | Fake price data | Multiple oracles, TWAP | | Access control | Missing permission checks | Role-based access |
Based on: throughput needs, cost constraints, ecosystem fit, team expertise
references/contract-patterns.md - Common smart contract patternsreferences/chain-comparison.md - Chain-specific considerationstesting
Designs systems for encoding, scoring, and generating choreographic movement using Laban notation, computational geometry, and procedural animation principles.
tools
Manage monorepos and multi-package repositories with workspace tools, dependency management, selective builds, and change detection. Covers npm/pnpm workspaces, Turborepo, and Python monorepo patterns. Triggers on monorepo setup, workspace management, or multi-package repository requests.
development
Curated bundle for managing monorepos with containerized deployment pipelines. Includes monorepo management, Docker containerization, CI/CD deployment, and coding standards. Use when setting up or improving multi-package repository infrastructure.
development
Apply modular synthesis principles to system design, workflow architecture, and conceptual frameworks. Use when designing modular systems, creating architecture diagrams using synthesis metaphors, applying signal flow thinking to data pipelines, or translating between audio engineering and software concepts. Triggers on modular architecture design, signal flow diagrams, synthesis-inspired system thinking, or "oscillator/patch" metaphors.