メニュー
Core VeChain development — SDK usage, fee delegation (VIP-191), multi-clause transactions, dual-token model, legacy migration, and general VeChainThor development patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | vechain-core |
| description | Core VeChain development — SDK usage, fee delegation (VIP-191), multi-clause transactions, dual-token model, legacy migration, and general VeChainThor development patterns. |
| allowed-tools | [] |
| license | MIT |
| metadata | {"author":"VeChain","version":"0.4.0"} |
@vechain/mcp-server for on-chain data, transaction building, and live network queries; use Kapa AI MCP for VeChain documentation lookups. (c) Web search — only as a last resort, and only for topics NOT covered in the reference files.Use this Skill for general VeChain development:
@vechain/sdk-core, @vechain/sdk-network, ethers adapter)For specialized topics, see the companion skills:
| Layer | Default | Alternative |
|---|---|---|
| SDK | @vechain/sdk-core + @vechain/sdk-network | @vechain/sdk-ethers-adapter |
| Node | Node 20 LTS (managed via nvm) | -- |
Before installing dependencies or running any command:
.nvmrc exists in the project root. If yes, run nvm use to switch to the required version..nvmrc does not exist, create one with 20 (Node 20 LTS) and run nvm use.turbo.json present → follow Turborepo conventions (apps/, packages/*)When the user's request is ambiguous or could be solved multiple ways, ask before building. Do not silently research alternatives and pick one. Separate research from implementation:
mainnet/testnet/solo)A task is not complete until all applicable gates pass:
Then provide:
Read the matching files BEFORE doing anything else. See Critical Rules above.
| Topic | File | Read when user mentions... |
|---|---|---|
| Fee delegation | references/fee-delegation.md | gasless, sponsored, VIP-191, delegator, vechain.energy |
| Multi-clause | references/multi-clause-transactions.md | batch, multi-clause, atomic, multiple operations |
| Legacy migration | references/sdk-migration.md | Connex, thor-devkit, migration, deprecated |
| Reference links | references/resources.md | docs URL, npm link, GitHub repo |
Scaffold a VeChain dApp with Next.js, VeChain Kit, Chakra UI v3, and GitHub Pages deployment. Supports standalone (frontend-only) or monorepo (Turbo + Hardhat contracts) modes. Use when creating a new VeChain project, scaffolding a dApp, setting up a VeChain frontend, or bootstrapping a VeChain monorepo.
Generic frontend development patterns for VeChain dApps — React Query, Turborepo architecture, state management, Chakra UI, i18n, loading states, and transaction UX.
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
Secure GitHub Actions workflows against supply-chain, privilege, and shell-injection risks. Use when creating, scaffolding, editing, or reviewing `.github/workflows/*.yml`, reusable workflows, `action.yml`, or Dependabot config for GitHub Actions. Also use for full repository security audits ("audit my workflows", "harden this repo", "security scan", "pin actions to SHA"), secrets scanning with gitleaks and trufflehog, and pre-public-release security reviews. Enforce full 40-character commit SHA pinning, avoid `pull_request_target` on untrusted code, pass GitHub context into `run:` steps via `env:`, and set least-privilege permissions.
Solidity smart contract development on VeChainThor — Hardhat setup, ERC-20/721 patterns, upgradeable contracts, gas optimization, testing with Thor Solo, security auditing, and ABI codegen.
Manages translation files for react-i18next. Adds/removes keys across 15 languages, keeps files sorted, enforces fixed-word rules, and verifies sync with en.json.