t2000

Escrow USDC for agent-to-agent deliverable work (A2A jobs). Use when hiring another agent for async work (research reports, builds, SLA tasks) or when selling deliverable work yourself (list a service: fixed price + SLA, no server needed) — anything where funds must commit before delivery starts and delivery takes minutes to days. Funds lock in a shared Sui Move object (no platform custody); release/refund are pure functions of state, clock, and caller. For instant request/response API calls use t2000-pay instead — x402 settle-then-serve needs no escrow.

How to read data from the Sui network. Use when choosing or implementing a data access strategy — queries for on-chain state, indexing pipelines, historical lookups, event subscriptions, cross-chain reads, or off-chain blob storage. Covers the three live Sui APIs (gRPC, GraphQL RPC, deprecated JSON-RPC), the Archival Store, the General-Purpose Indexer, the `sui-indexer-alt` custom indexing framework, and Walrus for off-chain blobs.

Use when writing Move functions on Sui, especially public APIs. Applies to function visibility (public vs entry), parameter ordering, and return patterns. Use whenever designing function signatures or deciding whether functions should transfer objects or return them.

Use when writing Move code on Sui to ensure 2024 edition syntax is used. Applies to method calls, string literals, vector operations, option handling, loops, and struct unpacking. Use whenever writing Move code to avoid legacy function-call syntax patterns.

Use when writing unit tests for Move smart contracts on Sui. Applies to test function naming, assertions, test attributes, context usage, and cleanup patterns. Use whenever user asks to write tests, add tests, or test a Move module.

Use when writing or reviewing Move smart contracts on Sui. Applies to naming structs, error constants, regular constants, events, getter functions, capability types, hot potato types, and dynamic field keys. Use whenever creating new types, functions, or constants in Move code.

Sui Programmable Transaction Blocks (PTBs). Use when writing, reviewing, or debugging code that composes multiple Sui transaction commands into a single atomic transaction — including TypeScript SDK `Transaction` usage, CLI PTB construction, gas coin handling, sponsored transactions, shared-object inputs, chaining command results, or troubleshooting PTB execution errors.

Sui Move smart contract development. Use when writing, reviewing, or debugging Move code on Sui. Covers Move abilities (key, store, copy, drop), TxContext, init functions, One-Time Witness, package publishing and upgrades, resource safety, events, and coins. Also use when the user asks about struct abilities, UID, how to destroy objects, or how to create a fungible token. For object model and ownership, see the `object-model` skill. For programmable transaction blocks, see the `ptbs` skill. For frontend dApp development, see the `frontend-apps` skill. For project setup and Move.toml, see the `sui-move-project` skill.

Deep reference for the Sui object model: ownership types, object abilities, dynamic fields, collections, versioning, transfer patterns, and derived objects. Use this skill whenever the user asks about Sui objects, object ownership (address-owned, shared, immutable, wrapped), how to transfer or share or freeze objects, dynamic fields vs dynamic object fields, Table vs Bag vs VecMap, object versioning, wrapping and unwrapping, the Receiving type, custom transfer rules, hot potato pattern, capability pattern, object deletion, Object Display, or how to model data (inventories, registries, nested items) in Sui Move. Also use when the user needs to choose between ownership types or storage patterns for their use case.

Publishing, upgrading, and deploying Sui Move packages. Use this skill when the user needs to publish a package, upgrade a published package, deploy to multiple networks, serialize transactions for multisig signing, run a local Sui network (localnet), prepare for Mainnet launch, monitor production deployments, or debug dry run failures. Also use when the user asks about sui client publish, sui client upgrade, UpgradeCap, upgrade policies, Published.toml, --serialize-output, localnet, mainnet launch checklist, gas estimation, multisig publishing, production monitoring, rollback, incident response, devInspectTransactionBlock, or --dry-run.

Sui SDK landscape — which SDK to pick (TypeScript, Rust, or community-maintained Python/Go/Dart/Kotlin/Swift), how they map to each other, and how to install and wire each one up. Use when a user is starting a new Sui project in any language, migrating between languages, comparing APIs across SDKs, or asking "what SDK should I use for X?". For deep patterns inside a single SDK, route to that SDK's reference file.

The Confidential AI (GPU-TEE) verifiable-inference architecture — attested fail-closed upstream, TEE-signed receipts, anchor-every on Sui, durable receipts in Redis (NOT Walrus), client-trustless verification, and the honest trust boundary that must never be overclaimed. Use when touching the confidential inference path, receipts, anchoring, the phala/* model catalog, verifyReceipt / t2 verify / the t2000_verify MCP tool / verify.t2000.ai, or when writing any copy that describes what confidential mode proves.

The t2000 family design system — design-tokens/tokens.css is the copy-in SSOT for VALUES, shadcn primitives are owned per-app, the house look is a seamless near-black dark theme with a per-app --t2k-accent, and @t2000/ui must never be reintroduced. Use when styling or restyling any app in apps/*, adding a new t2000 surface, editing tokens.css or an app's globals/theme CSS, picking colors or radii, deciding whether to reach for shadcn, or when tempted to create a shared UI/token package.

The deep version of the t2000 engineering discipline — trace-the-full-path debugging, verifiable success criteria, simplicity/surgical-change rules, complete-removal (no orphans), and the Musk product algorithm. CLAUDE.md carries the one-line assertions; read this for the worked examples, the ask-vs-proceed test, the ESLint flat-config override trap, and the test-file location convention. Use when scoping a feature or spec, planning a multi-step change, debugging something that has already taken more than one attempt, removing a feature/package/dependency, deciding whether to factor an abstraction, or adding an ESLint flat-config rule.

The cross-app env-validation contract — every app with ≥1 required env var validates at boot via a Zod schema and exposes values through a typed `env` proxy; raw `process.env.X` reads are banned outside the env module. Use when adding or renaming an environment variable, wiring up a new app in apps/*, writing or reviewing a lib/env.ts, debugging a "works locally, broken in Vercel" misconfiguration, or when you catch yourself about to write process.env or a `process.env.X || 'default'` fallback.

Money and token-metadata safety — floor display amounts (never round up), per-token decimal precision, preset/chip amount math, and the canonical token registry that owns every coin type and decimal count. Use when formatting or displaying a balance, computing a max/percentage/preset amount, converting between display and raw on-chain units, passing an amount into an SDK builder (send / swap / pay), adding or resolving a token, or debugging an unexpected "Insufficient balance" error.

Sui platform patterns for throughput and gas — Address Balances (SIP-58) accumulators that let ONE address run concurrent txs, and gasless stablecoin transfers that remove the "you need SUI to send USDC" wall. Includes the eligibility gotchas that cause misleading failures (0.01 minimum, the dust-remainder floor, contract-calls-are-not-gasless, gRPC-only auto-detect). Use when architecting a high-throughput payer or settlement address, building or debugging a USDC send, seeing an "insufficient SUI balance" or "Invalid withdraw reservation" error, considering a wallet fleet for scaling, or wondering whether a transaction leg qualifies as gasless.

Set up a t2000 Agent Wallet end-to-end on the user's machine. Use when the user says "set up t2000", "install the wallet", "create my Agent Wallet", "connect t2000 to Claude / Cursor", or pastes a one-prompt install URL. Covers wallet creation, optional spending limits, and MCP wiring. Read this first when bootstrapping a new user; the other skills assume this has run.

Connect a t2000 Agent Wallet to Claude Desktop, Cursor, Cline, Continue, or any MCP-compatible client. Use when asked to set up MCP, paste an MCP server config, install @t2000/mcp, or troubleshoot why the MCP server "doesn't do anything" when run from a terminal. v4 surface: 14 tools (6 read + 4 write + 3 Private Inference + 1 limit-view) and one skill-* prompt per SKILL.md in t2000-skills/skills/.

Read Sui chain state over gRPC — balances, objects, transactions, coin metadata, names. Use for any direct Sui read; JSON-RPC deactivates July 31, 2026 (mainnet), so new integrations MUST use gRPC. Read-only.

Resolve SuiNS names (alice.sui) to Sui addresses and back, from an agent. Use when asked to look up a .sui name, find the address behind a name, or find the name for an address. Read-only — registering names happens at suins.io.

Check the t2000 Agent Wallet balance on Sui. Use when asked about wallet balance, how much USDC / USDsui / SUI is available, or total funds. Also use before any send, swap, or pay operation to confirm sufficient funds exist.

Pay for an x402-protected API service using the t2000 wallet. Use when asked to call an AI model, search the web, generate images, send email, buy gift cards, send physical mail, check weather, execute code, or any task that requires a paid API. Handles the full x402 402 challenge automatically. Use t2000_services to discover all available services first.

Send USDC, USDsui, or SUI from the t2000 Agent Wallet to another Sui address. Use when asked to pay someone, transfer funds, send money, tip a creator, or make a payment to a specific Sui address or SuiNS name. Do NOT use for API payments — use the t2000-pay skill for x402-protected services.

Swap tokens on Sui via Cetus Aggregator (20+ DEXs, best-route across SUI, USDC, USDsui, USDT, USDe, ETH, GOLD, NAVX, WAL, vSUI, and more). Use when asked to swap, trade, convert, exchange, or "turn X into Y". Do not use for sending — use the t2000-send skill for transfers.

Write and review Sui Move that touches value using OpenZeppelin's audited primitives instead of hand-rolled math or access control. Use when writing Move with fees, shares, swaps, or AMM math; when reviewing or auditing a Sui Move package; or when a contract needs ownership handoff, spending allowances, timelocks, or rate limiting. Teaches the never-roll-your-own rules and where each OZ package applies.

Check — don't trust — a confidential (GPU-TEE) AI response by its receipt id. Use when asked to verify, prove, or audit that an AI response ran in a genuine hardware enclave (Intel TDX), wasn't tampered with, and is anchored on Sui. Works on any t2000 Private Inference confidential (`phala/*`) response. No key needed.

Read live market data from DeepBook, Sui's on-chain central limit order book — pools, tickers, order books, candles, trades — over a free public REST indexer. Use for Sui price checks, market depth, volume, or OHLCV questions. Read-only.

Read and store blobs on Walrus, Sui's decentralized blob store, over plain HTTP. Use when asked to fetch a Walrus blob, publish content to Walrus, or work with walrus:// / blob IDs. Reads are free; mainnet writes need your own publisher.

Discover x402 services payable via `t2 pay`. Use when the user asks "what can I pay for?", "what AI models are available?", "show me the service catalog", "is there a weather API?", or any other discovery question. Pairs with the t2000-pay skill (discovery first, then pay).

Generate a payment request for the t2000 Agent Wallet — print the wallet address, an ANSI QR code, and (via MCP) a Payment Kit URI (sui:pay?…). Use when asked to receive a payment, share a wallet address, create a payment link, or set up a fund-me link.