StarGate Skill
CRITICAL RULES
- Read reference files FIRST. When the user's request involves any topic in the reference table below, read those files before doing anything else — before writing code, before making decisions. Briefly mention which files you are reading so the user can confirm the skill is active (e.g., "Reading StarGate staking reference...").
- Information priority for VeChain topics: (a) Reference files in this skill — always the primary source. (b) VeChain MCP tools — use
@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.
- Prefer working directly in the main conversation for VeChain tasks. Plan mode and subagents do not inherit skill context and may fall back to web search instead of using reference files.
- After compaction or context loss, re-read this SKILL.md to restore awareness of the reference table and operating procedure before continuing work.
Scope
Use this Skill for StarGate staking development:
- NFT-based staking platform integration
- Tiered staking and rewards
- Validator system and delegation
- Node Manager features
- Boosting mechanics
- Phase 2 breaking changes
Operating procedure
1. Clarify before implementing
When the user's request is ambiguous, ask before building. Key questions:
- Which staking tier or node level?
- Mainnet or testnet?
- Phase 1 or Phase 2 contract interfaces?
2. Implement with VeChain-specific correctness
- Network: always explicit (
mainnet/testnet/solo)
- Tokens: VET for staking, VTHO for rewards
- Use correct contract addresses for the target network
3. Verify and deliver
A task is not complete until all applicable gates pass:
- Code compiles — no build errors
- Tests pass — existing tests still pass; new logic has test coverage
- Risk notes documented — any staking or delegation implications are called out
Reference files
Read the matching files BEFORE doing anything else. See Critical Rules above.
| Topic |
File |
Read when user mentions... |
| StarGate staking |
references/stargate-staking.md |
staking, StarGate, validator, delegation, VTHO rewards, node tier, boosting, Node Manager |
| Smart contracts |
references/contracts.md |
Contract functions, roles, Stargate, StargateNFT, ProtocolStaker, delegation status, effective stake, maturity, boost, token manager, mint, burn, migrate |
1---2name: stargate3description: StarGate staking on VeChainThor — NFT-based staking, tiered rewards, validator delegation, node management, boosting, and Phase 2 changes.4license: MIT5---67# StarGate Skill89## CRITICAL RULES10111. **Read reference files FIRST.** When the user's request involves any topic in the reference table below, read those files before doing anything else — before writing code, before making decisions. Briefly mention which files you are reading so the user can confirm the skill is active (e.g., "Reading StarGate staking reference...").122. **Information priority for VeChain topics:** (a) Reference files in this skill — always the primary source. (b) VeChain MCP tools — use `@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.133. **Prefer working directly in the main conversation** for VeChain tasks. Plan mode and subagents do not inherit skill context and may fall back to web search instead of using reference files.144. **After compaction or context loss**, re-read this SKILL.md to restore awareness of the reference table and operating procedure before continuing work.1516## Scope1718Use this Skill for StarGate staking development:1920- NFT-based staking platform integration21- Tiered staking and rewards22- Validator system and delegation23- Node Manager features24- Boosting mechanics25- Phase 2 breaking changes2627## Operating procedure2829### 1. Clarify before implementing3031When the user's request is ambiguous, **ask before building**. Key questions:3233- Which staking tier or node level?34- Mainnet or testnet?35- Phase 1 or Phase 2 contract interfaces?3637### 2. Implement with VeChain-specific correctness3839- Network: always explicit (`mainnet`/`testnet`/`solo`)40- Tokens: VET for staking, VTHO for rewards41- Use correct contract addresses for the target network4243### 3. Verify and deliver4445A task is **not complete** until all applicable gates pass:46471. **Code compiles** — no build errors482. **Tests pass** — existing tests still pass; new logic has test coverage493. **Risk notes documented** — any staking or delegation implications are called out5051## Reference files5253Read the matching files BEFORE doing anything else. See Critical Rules above.5455| Topic | File | Read when user mentions... |56|-------|------|---------------------------|57| StarGate staking | [references/stargate-staking.md](references/stargate-staking.md) | staking, StarGate, validator, delegation, VTHO rewards, node tier, boosting, Node Manager |58| Smart contracts | [references/contracts.md](references/contracts.md) | Contract functions, roles, Stargate, StargateNFT, ProtocolStaker, delegation status, effective stake, maturity, boost, token manager, mint, burn, migrate |
vechain