plan-web3-game-assets
Define an opt-in Ethereum, Base or Immutable game-asset lifecycle, including token identity, supply, rights, custody, game eligibility and chain-specific dependencies.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 4
- Forks
- 3
01 前言 Front Matter
- name
- plan-web3-game-assets
- engines
- [ "AGNOSTIC" ]
- description
- Define an opt-in Ethereum, Base or Immutable game-asset lifecycle, including token identity, supply, rights, custody, game eligibility and chain-specific dependencies.
02 资源文件 2
- 参考文档agents/openai.yaml262 B
- 参考文档references/asset-brief.md2.0 KB
03 SKILL.md 正文
When to use
Use when a game needs blockchain-owned assets, NFT collections, transferable inventory or a Web3 asset economy. A visual asset request alone does not select blockchain integration.
Workflow
Read the host WEB3.md, web3-game.json and the shared .web3/CONTRACT.md when configured. Use commands/web3-game.sh registry and local inspect, validate or doctor; these do not contact a chain. Preserve ENGINE, ARCHITECTURE, STYLE and independent media selection.
Define the actual lifecycle using the asset brief. Separate card/item definitions, unique instances or interchangeable quantities, wallet control, on-chain ownership, gameplay entitlement and content licenses. Keep authoritative game rules separate from arbitrary NFT metadata.
Honor explicit Ethereum mainnet, Base or current Immutable selection. Refresh the dated chain/compiler/operator facts from primary sources before production. Do not replace L1 with a cheaper chain or treat retired Immutable X as the EVM target. Disclose managed chain ingress/operator dependencies and optional hosted products separately.
Choose the transfer-during-match rule before implementing admission. A snapshot license can permit an admitted match to finish after sale; a server reservation cannot stop external transfers. Strict exclusivity needs a reviewed contract-enforced lock/escrow with custody and recovery decisions. Never select custody silently.
Prepare the complete proposed policy, asset/content ancestry, numerical limits and open production decisions for user review. Explicit init --spec reviewed-spec.json creates fresh host files; it neither proves approval nor selects services. Route contract, wallet, ownership, trading and lifecycle verification to their focused skills and resolve the selected engine's concrete integration owners.
Output
Return a reviewed lifecycle specification, exact chain/collection/content identities, authority and dependency map, failure/recovery rules, evidence requirements and any unresolved decisions. Keep configuration and installation separate from signing, transactions, live deployment, asset promotion and release.
04 同仓库更多 Skills
verify-web3-game-lifecycle
Verify a game's selected Web3 asset, wallet, ownership and trading lifecycle with contract properties, canonical recovery, actual target evidence and separate release readiness.
verify-onchain-game-assets
Verify exact on-chain game collection ownership and quantities at canonical blocks, reconcile inventory events, and design honest match admission. Use for ERC721/ERC1155 inventory, reorg recovery, reservations, or transfer-during-match rules.
integrate-game-wallets
Integrate explicit player-wallet connection, scoped SIWE authentication, authority invalidation and reviewed target-specific handoff without application-held player keys.
integrate-game-asset-trading
Integrate explicitly selected game asset settlement with exact unsigned intents, scoped approvals, idempotent operations and canonical receipt reconciliation. Use for NFT listing, buying, cancellation, retries or marketplace integration.
build-evm-game-contracts
Author and verify host-owned EVM game collections and explicit mint, burn, craft or admin rules with pinned Solidity tooling. Use for contract source and deployment candidates; deployment and player signing require separate authorization.
threejs-build-code-models
Author procedural Three.js TypeScript or JavaScript models from a text brief and optional authorized references using deterministic ordered review passes. Use when the selected art pipeline is CODE and the runtime model should be source code rather than a downloaded or generated mesh.