tetherto
- 64 skills
- 0 followers
- 11 hours ago last updated
- ▌ Wdk Wallet · tetherto bundleManage a multi-chain crypto wallet via the wdk CLI. Supports multiple named wallets. Use when: user asks to check wallet balance, get wallet address, send tokens, swap tokens, bridge tokens across chains, check transaction history, buy/sell crypto, or invoke chain-specific wallet module methods (discover them with `wdk method list`). Supports Bitcoin, Ethereum, Polygon, Arbitrum, Base, BSC, Avalanche, Solana, Tron, Spark, and Smart Accounts (ERC-4337). Triggers on: 'check balance', 'wallet address', 'send tokens', 'transfer tokens', 'swap tokens', 'bridge tokens', 'cross-chain swap', 'best route', 'transaction history', 'buy crypto', 'sell crypto', 'get address'.
- ▌ Use UI Kit · tethertoUse whenever creating or editing UI in this repo — React components, modals, dialogs, forms, buttons, inputs, typography, styling, icons, or any .tsx/.jsx work. The repo uses `@tetherto/pearpass-lib-ui-kit` as the single source for UI primitives; do not roll custom ones. Load this before suggesting any UI change, especially when touching src/action/pages, src/action/containers, src/shared/containers, or src/contentPopups/views.
- ▌ Qts Pr Create · tethertoGenerate qvac-test-suite pull request titles and descriptions for framework runtime changes, packaging or export changes, workflow or publish changes, docs-only cleanup, and template or mobile runtime updates. Use when creating a framework PR or refining its title/body.
- ▌ Qts Pr Review · tethertoReviews qvac-test-suite pull requests and diffs for package-surface risk, CLI/versioning behavior, dist hygiene, workflow parity, docs accuracy, and mobile template/runtime integrity. Use when reviewing a PR, a branch diff, or doing a senior engineer pass on framework changes.
- ▌ Qts Skill List · tethertoCatalog of the repo-local qts-* skills for qvac-test-suite with one-line purpose and when-to-use guidance. Use when the user asks what skills exist in this repository, which skill fits a task, or how to invoke a repo-specific skill.
- ▌ Wdk · tetherto bundleTether Wallet Development Kit (WDK) for building non-custodial multi-chain wallets. Use when working with @tetherto/wdk-core, wallet modules (wdk-wallet-btc, wdk-wallet-evm, wdk-wallet-evm-erc-4337, wdk-wallet-solana, wdk-wallet-spark, wdk-wallet-ton, wdk-wallet-tron, ton-gasless, tron-gasfree), and protocol modules including swap (wdk-protocol-swap-velora-evm, bridge (wdk-protocol-bridge-usdt0-evm), lending (wdk-protocol-lending-aave-evm), and fiat (wdk-protocol-fiat-moonpay). Covers wallet creation, transactions, token transfers, DEX swaps, cross-chain bridges, DeFi lending/borrowing, and fiat on/off ramps.
- ▌ Code Of Conduct · tethertoCode of conduct that contributors — including AI coding assistants — MUST follow when writing, modifying, or reviewing code for any Tether Wallet Development Kit (WDK) module (wallets, protocols, core). Covers project workflow (atomic single-feature pull requests, design-before-implementation specs), code quality (avoid code smells, never violate S.O.L.I.D. principles, document every public/protected component, use narrow types, avoid defensive programming, mark every thrown error with @throws), and testing (arrange-act-assert, test only the public API, assert real values not patterns, define jest mocks at the top level, mock all external-service dependencies).
- ▌ Wdk Review Dts · tethertoReview and maintain WDK generated .d.ts type definitions (manual updates, exports, internal exclusion, interface/abstract emission, no build:types).
- ▌ Wdk Review Tests · tethertoReview WDK test suites for compliance with established testing conventions (assertions, mock boundaries, isolation, coverage, naming, structure).
- ▌ Wdk Review Jsdocs · tethertoReview WDK source files for JSDoc format and type-annotation conventions (JSDoc blocks, tags, type precision, imports/exports, naming).
- ▌ Bump Mdk · tethertoBump package version(s) across the MDK monorepo and resync every affected lockfile the way CI expects. Use when raising a release version, when the "package-lock.json is out of sync with package.json" gate is red, or after a merge that left package.json / package-lock.json versions mismatched.
- ▌ Changelog · tethertoGenerate the changelog for the next MDK release by carefully diffing the previous release tag against the current tree, rotating the existing CHANGELOG.md into the year archive, and drafting the matching high-level release-notes file. Use when cutting a release, preparing release docs, or when asked to "update the changelog" / "write the changelog for vX.Y.Z".
- ▌
- ▌ Mdk Skill Suite · tethertoThe MDK product skill suite (mdk, mdk-worker-plugin, mdk-gateway-plugin, mdk-ui-component, mdk-deployment) is not installed in this checkout. Use this whenever a task mentions MDK, a worker, a Worker Plugin, a Gateway plugin, a UI component for worker/plugin data, or deploying an MDK stack.
- ▌ Mdk · tetherto bundleBuild on the MDK (Mining Device Kit) platform. Use whenever a task mentions MDK, the Kernel/ORK, a worker, a Worker Plugin, mdk-contract.json, @tetherto/mdk-* packages, a miner / power meter / sensor / container integration, a cross-worker aggregation endpoint, a UI component for worker/plugin data, or deploying an MDK stack.
- ▌ Mdk Deployment · tethertoDeploy and run a working MDK stack from mdk.yaml. Use when the task mentions "deploy", "run the stack", "start the Kernel/ORK + workers + gateway", "register a plugin", "mdk.yaml", or MDK environment configuration.
- ▌ Mdk UI Component · tetherto bundleBuild a UI page/panel that renders data from an MDK worker or Gateway plugin. Use when the task mentions "UI / component / widget / dashboard", "show telemetry", "chart / tile / heatmap", "render data from a worker/plugin", or prompts like "create a UI to show <metric> for <device>".
- ▌ Mdk Worker Plugin · tetherto bundleIntegrate a new device into MDK as a device worker. Use for any task like "new device / miner / power meter / sensor / container worker", "build a worker", "integrate hardware", "wrap a device protocol (Modbus / CGMiner / HTTP / MQTT)", or anything creating or editing an mdk-contract.json, a Worker Plugin, or telemetry/command handlers under backend/workers/.
- ▌ Mdk Gateway Plugin · tetherto bundleBuild a Gateway / App Node plugin that exposes an HTTP API over one or more MDK workers. Use when the task mentions "aggregate", "combine workers", "site summary / rollup", "plugin", "mdk-plugin.json", "gateway endpoint", "cross-worker endpoint", or when a UI needs live worker data and no matching `/api/...` route exists yet.
- ▌
- ▌ Qv Pr Mine · tetherto bundleShow the current user's open PRs across every pod registered under .github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team. Use when the user asks about their own PRs, merge readiness, who to ping, or invokes /qv-pr-mine.
- ▌ Qv Pr Test · tetherto bundlePlan and run local PR validation for tetherto/qvac PRs. Reuses the shared PR worktree, discovers touched packages and package.json scripts, recommends a test tier, and analyzes results. Use when testing a PR or invoking /qv-pr-test.
- ▌ Qv Dev Diary · tetherto bundleRead, inspect, and add local dev diary entries after diary setup. Use when the user asks to view today's diary, edit diary notes, add work to the diary, or check what has been logged.
- ▌ Qv Pr Review · tetherto bundleDeep-dive review of any GitHub PR in tetherto/qvac. Validates gitflow, CI, title/body format, code quality, security, and applicable repo rules. Posts a PENDING review with inline comments. Use when reviewing a PR, given a PR link, or invoking /qv-pr-review.
- ▌ Qv Asana Sync · tetherto bundleLook up and update Asana tasks using local developer-workflow config and direct Asana REST calls. Use when the user asks to sync an Asana task, move task status, add a PR link to Asana, or validate Asana configuration.
- ▌ Qv Qip Create · tetherto bundleDrafts concise, stakeholder-facing QIPs with an explicit architectural decision, alternatives, and trade-offs. Use when creating a QIP, shaping a fuzzy proposal after qv-qip-triage, or invoking /qv-qip-create.
- ▌ Qv Qip Review · tethertoReviews QIP drafts for approval readiness, architectural fit, decision clarity, material trade-offs, and appropriate stakeholder detail. Use when reviewing a QIP or invoking /qv-qip-review.
- ▌ Qv Qip Triage · tetherto bundleUse during planning, implementation, PR review, or /qv-qip-triage when a change may affect public SDK API, native dependency, plugin contract, model registry contract, runtime, transport, storage, release flow, deployment, security, NFR, or technical principles.
- ▌ Qv Skill List · tethertoCatalog of all repo qv-* custom skills with one-line purpose and when-to-use. Use when the user asks what skills exist, which skill to use, how to invoke a skill, or invokes /qv-skill-list.
- ▌ Qv Holepunch Dev · tethertoGuides discovery and development with Holepunch ecosystem libraries. Use when working with P2P stack (Hypercore, Hyperswarm, Autobase, Hyperdb, Corestore), Bare runtime (bare-* modules like bare-fs), or Pear app framework (pear-* modules). Teaches on-the-fly API discovery via docs.pears.com and gh CLI.
- ▌ Qv Sdk Backmerge · tethertoOpen the follow-up "backmerge" PR that lands a release's version bump + changelog onto main. Use after (or alongside) creating a release PR for an SDK pod package.
- ▌ Qv Sdk Changelog · tetherto bundleGenerate changelogs for SDK pod packages using tag-based GitFlow. Use when preparing a release, generating changelog, or creating CHANGELOG_LLM.md.
- ▌ Qv Sdk Pr Create · tethertoGenerate PR descriptions for SDK pod packages following template and format rules. Use when creating an SDK pod PR or invoking /qv-sdk-pr-create.
- ▌ Qv Sdk Pr Status · tetherto bundleTeam-wide PR dashboard for the SDK pod. Shows open PRs touching SDK pod paths, SDK docs, or authored by SDK roster members, sorted oldest-first, grouped by author tier (SDK Core / Platform / External) into needs-your-re-review / stale / needs-review / fully-approved, with a Docs lane, per-platform e2e on Core impl PRs, merge-conflict and CI-red warnings. Use when checking team SDK pod PR status or invoking /qv-sdk-pr-status.
- ▌ Qv Sdk E2e Create · tethertoPlans and scaffolds e2e tests in packages/sdk/e2e for a new or changed public SDK API. Use when adding or modifying SDK functionality that is exposed to consumers. Enforces happy / sad / error coverage, deterministic model-output assertions, desktop/mobile/Electron consumer coverage, smoke-suite selection, and local validation with run:local.
- ▌ Qv Addon Changelog · tethertoGenerate changelog entries for a target add-on package. Use when preparing a new release.
- ▌ Qv Addon Pr Create · tethertoGenerate PR descriptions for addon packages (non-SDK inference addons, decoder, OCR). Use when creating a PR description or user asks to "prepare PR description" for an addon package.
- ▌ Qv Dev Diary Setup · tetherto bundleSet up the opt-in local dev diary for any developer. Use when the user asks to enable diary logging, initialize diary capture, run diary --init, or configure local daily work updates.
- ▌ Qv Notice Generate · tetherto bundleGenerate NOTICE files with third-party attributions for all packages in the monorepo.
- ▌ Qv Agent Stack Sync · tetherto bundlePlan and prepare the QVAC agent-stack release cascade across @qvac/sdk, @qvac/cli, @qvac/ai-sdk-provider, @qvac/opencode-plugin, and @qvac/openclaw-plugin. Use for /qv-agent-stack-sync --plan, --prepare-cascade, or --promote; syncing CLI to a newer SDK; or checking OpenCode/OpenClaw/provider compatibility.
- ▌ Qv Devops Pr Create · tetherto bundleGenerate PR titles and descriptions for DevOps surfaces (CI/CD, composite actions, automation scripts, IaC) following the devops.md PR template and commit/PR format rule. Use when creating a DevOps PR or invoking /qv-devops-pr-create.
- ▌ Qv Devops Pr Review · tetherto bundlePR review for DevOps changes — runs the generic /qv-pr-review flow then layers a structured GitHub Actions security audit (action pinning, permissions, OIDC, secrets handling). Use when reviewing a PR that touches DevOps paths or invoking /qv-devops-pr-review.
- ▌ Qv Devops Pr Status · tetherto bundleTeam-wide PR dashboard for the DevOps pod, scoped to PRs authored by pod-roster members. Shows open PRs touching DevOps-owned paths and authored by DevOps leads/members, grouped into needs-your-re-review / stale (>3d) / needs-review, with merge-conflict warnings and a separate Excluded section for non-roster authors. Use when checking DevOps pod PR status, asking about stale PRs, or invoking /qv-devops-pr-status.
- ▌ Qv Merge Guard Wire · tetherto bundleWire a new CI job/workflow into the qvac-merge-guard / validate-pr aggregated required status check, instead of it becoming a disconnected standalone check
- ▌ Qv Daily Work Update · tetherto bundleGenerate a concise end-of-day work update from local diary, GitHub activity, PR queue state, and optional Asana config. Use when the user asks for daily update, EOD update, standup, or what they did today.
- ▌ Qv Sdk Lockstep Sync · tetherto bundleStamp the @qvac/inference version onto @qvac/sdk and regenerate tetherto-qvac-sdk so a release-* cut ships one shared version.
- ▌ Qv Sdk Update Models · tetherto bundleRegenerates SDK model constants from the live QVAC registry and opens a [mod] PR. Use when registry models landed and packages/sdk models.ts needs syncing, or when invoking /qv-sdk-update-models. Optional cascade refreshes ai-sdk-provider and sdk-python generated catalogs.
- ▌ Cpp String API Review · tetherto bundleReview C++ changes for string parameter and call-site efficiency conventions (`std::string_view`, `std::string&&`, `const std::string&`, `const char*`, and TransparentStringMap lookup). Use when reviewing C++ code, refactoring addon interfaces, or invoking /cpp-string-api-review.
- ▌ Qv Addon Release Notes · tethertoGenerate release notes for addon packages (non-SDK inference addons, decoder, OCR). Use when preparing release notes or user asks to "generate release notes" for an addon package.
- ▌ Qv Devops Daily Update · tetherto bundleCompose a daily standup in the team's Slack format (🔨 Done today / 📅 Planned for tomorrow / 🚧 Blockers / risks), aggregating recent PRs, reviews, and CI from tetherto/qvac. Use when asked for a daily update, standup, EOD, or invoking /qv-devops-daily-update.
- ▌ Qv Devops Runner Queue · tetherto bundleInspect GitHub Actions self-hosted runner queues when a developer provides a run URL, job URL, runner label, or reports a blocked CI job, or invokes /qv-devops-runner-queue.
- ▌ Qv Devops Why My Pr Not · tetherto bundleDiagnose why CI checks are not running on a PR and/or why a PR cannot be merged by comparing live PR state with current labels, CODEOWNERS, fork trust, and approval configuration. Read-only by default. Use when a developer asks why checks are missing, why a PR cannot merge, or invokes /qv-devops-why-my-pr-not with a PR URL.
- ▌ Review · tethertoRun a comprehensive code review with 4 specialized reviewers (security, correctness, performance, consistency) in parallel.
- ▌ Release · tethertoRelease a package to NPM. Validates version bump, changelog, creates release branch, monitors CI, verifies publish.
- ▌
- ▌ Orchestrate · tethertoRun the full implement → test → CI → review → PR pipeline for a task. Coordinates implementer, test-writer, ci-validator, and code-reviewer agents.
- ▌ Qv Registry Autobase Patterns · tetherto bundleReference material for Autobase, HyperDB, and multi-writer patterns in the QVAC registry server. Use when working with Autobase, HyperDB schemas, blind pairing/peering, Hyperdispatch, or debugging Corestore/replication issues.
- ▌ Bump Version · tethertoBump a native addon package's version in package.json and write its CHANGELOG.md entry. Defaults to a minor bump. Use before /release.
- ▌ Commit Trace · tethertoTrace a commit to its published npm versions, including transitive SDK resolution with time-aware accuracy
- ▌ Release Patch · tethertoBack-port fix(es) onto an existing release line and cut a patch release. Create the new release branch from the base with NO direct commits, land the fix(es) and the version+changelog bump via PRs into it, then publish via the `release` skill. Use for patching a shipped version (e.g. what an older SDK release pins) without pulling in later main-line changes.
- ▌ Vlm Benchmark · tethertoBenchmark an optimization (PR or branch) on a Device Farm device via the vlm-benchmark framework — baseline vs optimized, quality-regression-aware.
- ▌ Rollout Phase A · tethertoPhase A of a qvac-fabric rollout — set up overlay port and validate all 7 consumers against the fabric branch before publishing to the registry. Pass --on-top-of-pr to apply the overlay onto an open PR's head branch instead of a dedicated validation branch.
- ▌ Rollout Phase B · tethertoPhase B of a qvac-fabric rollout — tag the merged fabric commit, publish to registry, land the consumer side (vcpkg bumps + package versions + changelogs for all 7 consumers) as one PR, post one Slack message. Pass --bump-only to resume a part-done rollout and do just the version + changelog work. Pass --on-top-of-pr to put the whole consumer side onto an open PR — revert the overlay commit Phase A placed there AND land the bumps on that same PR, instead of opening a separate bundled PR.
- ▌ Release Fabric Consumers · tethertoRelease the qvac-fabric consumers to npm after the bundled version-bump PR merges — one release branch + on-merge dispatch per consumer, stopping at the npm approval gate. Supports --exclude to hold packages back. Phase C after rollout-phase-b.