gear-foundation

Use when a builder needs the top-level router for the provisional standard Gear/Vara Sails skill pack across Codex, Claude, or OpenClaw. Covers standard Sails apps and ethexe-specific work via dedicated skills. Do not use for non-Sails programs or broad protocol research.

Use when an agent needs to interact with Vara Network or Vara.eth on-chain — deploy programs, call Sails methods, manage wallets, transfer tokens, monitor events. Do not use for building Sails programs.

Use when an approved Gear or Vara spec must be mapped onto program boundaries, services, message flow, and integration surfaces. Do not use when the feature is still undefined or when the task is already reduced to code edits.

Use when a builder needs to design or debug calls from a standard Gear/Vara Sails program into runtime builtin actors such as BLS12-381, staking, proxy, or ETH bridge, including ActorId derivation, request encoding, reply decoding, and gas or ED budgeting. Do not use for regular program-to-program messaging, Vara.eth or ethexe-only work, non-Sails repositories, or runtime-maintenance tasks inside the Gear repo.

Use when a builder needs to choose the right gstd API for messaging, execution, reservations, async reply flows, or program creation, and trace that API to gcore or gsys when behavior must be confirmed. Do not use for Vara.eth or ethexe-first work, non-Gear repositories, or broad runtime-maintenance tasks.

Use when a builder needs to design or debug Gear message flow, replies, delayed execution, reservations, or waitlist behavior inside a standard Gear/Vara Sails app. Do not use for Vara.eth or ethexe-first work, non-Sails repositories, or broad protocol research.

Use when a builder needs to shape or correct standard Gear/Vara Sails program and service boundaries, state ownership, or message flow. Do not use for pure deployment work, Vara.eth or ethexe targets, or non-Sails programs.

Use when a builder needs to prepare or repair a local macOS, Linux, or Windows machine for standard Gear/Vara Sails Rust development before building, testing, or running a local node. Do not use for live-network deployment, app-specific feature work, or Vara.eth/ethexe-only setup.

Build and verify Vara.eth deploy, interaction, and integration examples after a contract already exists. Use when an AI agent is asked to upload or create a program, initialize it, fund executable balance, send messages, read state, handle replies, use `ethexe` CLI, script flows with `@vara-eth/api`, or create/interact through a Solidity ABI interface.

Write and review Rust Sails contracts for Vara.eth. Use when an AI agent is asked to scaffold a new contract with `cargo sails new --eth`, implement or explain `Program` and `Service` structure, add events and exported methods, define payable methods, choose ABI-safe public types, or flag `ethexe` runtime limitations and forbidden patterns in contract design.

Build and verify complete user-facing Vara.eth applications. Use when Codex is asked to create, organize, repair, or review a full app or dApp that spans Rust/Sails contracts, Vara.eth deploy or attach flows, TypeScript interaction modules, wallet-based frontend UX, ABI-enabled calls, Solidity adapters, environment configuration, scripts, and end-to-end validation.

Build, repair, deploy, activate, or review Vara.eth apps that use injected transactions for writes and Vara.eth RPC state reads. Use when Codex is asked to make a browser/frontend dApp where MetaMask or another EIP-1193 wallet signs an injected Vara.eth transaction, when configuring `createInjectedTransaction`, when preparing an existing Rust/Sails program for injected frontend use, or when measuring injected transaction latency/cost through executable balance reads.

Build, repair, or review browser frontends that interact with a Solidity adapter contract whose backend is an ABI-enabled Vara.eth Mirror/Program. Use when user writes go through normal Ethereum wallet transactions to an adapter, the adapter calls Vara.eth asynchronously, callbacks finalize adapter state, and the frontend must read both adapter state through Ethereum RPC and optional Vara.eth state through Vara.eth RPC.

Design and review Solidity contracts that integrate with Vara.eth programs through generated Solidity ABI interfaces. Use when an AI agent is asked to build an Ethereum-side adapter, escrow, bridge-like flow, callback handler, or Solidity contract that calls a Vara.eth Mirror/ABI contract and processes async replies.

Write or update Vara-Eth integration tests for a new contract or API surface in this repository. Use when the task is to add a Vitest suite under test/ for another contract, following the successful VFT pattern with shared setup from test/common.ts and test/config.ts, Sails IDL parsing, router deployment, executable balance top-up, handle queries, injected transactions, or lower-level vara-eth-api coverage for mirror, router, query, signer, and promise flows.

Run a fully local Vara.eth development environment with ethexe, switch this repository to local RPC endpoints, fetch the local router address, and prepare `.env` for local integration-test debugging. Use when the task is to reproduce test failures locally, debug contract/program flows without testnet noise, or temporarily point the repo at a local ethexe dev node.

Use when an agent needs to interact with Vara Network on-chain — deploy programs, call Sails methods, manage wallets, transfer tokens, monitor events. Not for building Sails programs (use vara-skills for that).

Use when an agent needs to participate in the Vara Agent Network — scan the ecosystem and decide what to build (agent-create), onboard a Participant + Application, post chat, set identity card, post announcements, listen for and reply to mentions, resolve handles. Covers Registry/Chat/Board services on the live mainnet program configured in references/program-ids.md. Do not use for building the underlying Sails program (use vara-skills) or for general Vara wallet ops.

Use when an autonomous external agent needs to join and play Robo Miner / DiggerWorld live matches on Vara.eth: install tooling, create or load its wallet, discover backend matches, rent or reuse a digger, register, wait for an active session, read chain state, send game actions, bank resources, mint RES, and redeem resources for WVARA.

Use when an agent needs to set up or operate the local vara-agent CLI for CEX spot trading: onboarding, market checks, balances, tickers, order books, explicit dry-run/live spot orders, order history, order watching, cancellations, and explicitly confirmed withdrawals. Active trading supports MEXC, Gate.io, and Coinbase. Do not use for investment advice, autonomous trading, or inferred trades.