[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70TWV3J83RAJMA7BC62CPAH":3,"skill-same:01M70TWV3J83RAJMA7BC62CPAH":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M70TWV3J83RAJMA7BC62CPAH","build-evm-game-contracts",null,"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.","TimothyMeadows\u002FHephaera","TimothyMeadows","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4072037?v=4","01M6ERVE3WV9X55S1NT4W5FDGA","Timothy D Meadows II","01M6ERVE8H7CBATH6KYFDKG5CJ",4,"MIT","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fbuild-evm-game-contracts\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"evm","build","build evm game contracts","contracts","game","tooling","mint","verify","signing","admin","with","author","Rules","use","host","contract","collections","player","deployment","for","2026-11-10 10:12:30",false,"---\nname: build-evm-game-contracts\ndescription: 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.\nengines: [AGNOSTIC]\n---\n\n# Build EVM Game Contracts\n\n## When to use\n\nUse for ERC721\u002FERC1155 game collections and contract-owned supply, identity, permissions or asset transformations. Wallet login, inventory admission and order submission have separate owners. A collection request does not select an economy, paid packs, upgrade proxies or a marketplace.\n\n## Workflow\n\n1. Resolve engine\u002Fskill compatibility and the host architecture. Read the host `WEB3.md`, `web3-game.json` and `.web3\u002FCONTRACT.md`; absent or unresolved chain policy remains unconfigured. Solidity source needs `.architecture\u002FSOLIDITY.md` support even when host services use .NET or Node. Preserve engine and media selections.\n2. State the proposed invariants before authoring: standard and exact asset identities; lifetime versus circulating supply; ID reuse; ERC1155 interchangeable quantities; mint\u002Fresult authority; holder versus operator burns; metadata rights\u002Fmutation; royalties; admin succession and recovery. For crafting\u002Fupgrades, define each atomic input\u002Foutput and replay\u002Fclaim identity. Missing authority is a design gap, never a guessed reward oracle.\n3. Read `.web3\u002Fcontracts\u002FREADME.md` when using the original bounded examples in `.web3\u002Fcontracts\u002F`. Adapt them into a reviewed host-owned source directory. Keep imported reviewed libraries and licenses intact. Record exact dependency\u002Fcompiler\u002Fsettings identities; the tested baseline is OpenZeppelin 5.6.1 with Solidity 0.8.28, optimizer 200 and Cancun. Revalidate these pins against the selected chain rather than silently upgrading.\n4. Select transfer policy explicitly. Unrestricted standard tokens and the optional registry profile have different compatibility. For Immutable, verify the actual managed allowlist\u002Fcode identity, current policy and every wallet\u002Fsettlement\u002Fescrow operator. A synthetic registry, ABI compatibility or registry declaration cannot prove approval. A blocked operator requires direction or a reviewed compatible design.\n5. Compile actual source and execute disposable local-EVM transactions for each changed invariant. Cover unauthorized mint\u002Fadmin\u002Fburn, cap exhaustion through burns, repeated identity, quantity\u002Fduplicate batches, approvals\u002Frevocation, callback reentry and rollback, and the selected operator rejection paths. Review warnings and bound callbacks\u002Floops. The baseline test is `node --test tests\u002Ftest-web3-contracts.mjs`; provision tools explicitly under existing authorization before running it. Do not install tooling or contact a chain during policy inspection.\n6. Prepare a candidate with exact source\u002Fdependency\u002Fcompiler input, ABI and bytecode identities, constructor\u002Frole\u002Fregistry configuration and test results. Obtain independent review of source and deployment assumptions. Report public-chain, registry, wallet\u002Fdevice, audit and target evidence separately. Broadcast only when separately authorized for the exact chain and operation.\n\n## Output\n\n- Host-owned source and explicit invariants, authority and unsupported behavior.\n- Reproducible pinned compilation, local successful\u002Freverting transaction evidence and resolved review findings.\n- An identified deployment candidate and target-specific prerequisites; local readiness does not imply a deployed or audited collection.\n\n## Boundaries\n\nERC-2981 reports royalties without universally enforcing them. Metadata grants no copyright or gameplay trust automatically. Token approvals are durable transfer authority, not login or burn permission. Ordinary public contract state cannot hide hands, decks or secrets.\n\nThe example sale\u002Freceiver\u002Fregistry harness under `.web3\u002Fcontracts\u002Ftest\u002F` is unrestricted test code. Never promote it as production settlement or deploy it with real value. A single atomic rollback test certifies no protocol, order replay policy, custom exchange or cross-chain trade. Escrow\u002Fstrict locks, proxies, economics and externally authorized crafting\u002Frewards require their own reviewed designs. No live deployment, player key, hosted service, license acceptance or paid action follows from selecting this skill.\n","# Build EVM Game Contracts\n\n## When to use\n\nUse for ERC721\u002FERC1155 game collections and contract-owned supply, identity, permissions or asset transformations. Wallet login, inventory admission and order submission have separate owners. A collection request does not select an economy, paid packs, upgrade proxies or a marketplace.\n\n## Workflow\n\n1. Resolve engine\u002Fskill compatibility and the host architecture. Read the host `WEB3.md`, `web3-game.json` and `.web3\u002FCONTRACT.md`; absent or unresolved chain policy remains unconfigured. Solidity source needs `.architecture\u002FSOLIDITY.md` support even when host services use .NET or Node. Preserve engine and media selections.\n2. State the proposed invariants before authoring: standard and exact asset identities; lifetime versus circulating supply; ID reuse; ERC1155 interchangeable quantities; mint\u002Fresult authority; holder versus operator burns; metadata rights\u002Fmutation; royalties; admin succession and recovery. For crafting\u002Fupgrades, define each atomic input\u002Foutput and replay\u002Fclaim identity. Missing authority is a design gap, never a guessed reward oracle.\n3. Read `.web3\u002Fcontracts\u002FREADME.md` when using the original bounded examples in `.web3\u002Fcontracts\u002F`. Adapt them into a reviewed host-owned source directory. Keep imported reviewed libraries and licenses intact. Record exact dependency\u002Fcompiler\u002Fsettings identities; the tested baseline is OpenZeppelin 5.6.1 with Solidity 0.8.28, optimizer 200 and Cancun. Revalidate these pins against the selected chain rather than silently upgrading.\n4. Select transfer policy explicitly. Unrestricted standard tokens and the optional registry profile have different compatibility. For Immutable, verify the actual managed allowlist\u002Fcode identity, current policy and every wallet\u002Fsettlement\u002Fescrow operator. A synthetic registry, ABI compatibility or registry declaration cannot prove approval. A blocked operator requires direction or a reviewed compatible design.\n5. Compile actual source and execute disposable local-EVM transactions for each changed invariant. Cover unauthorized mint\u002Fadmin\u002Fburn, cap exhaustion through burns, repeated identity, quantity\u002Fduplicate batches, approvals\u002Frevocation, callback reentry and rollback, and the selected operator rejection paths. Review warnings and bound callbacks\u002Floops. The baseline test is `node --test tests\u002Ftest-web3-contracts.mjs`; provision tools explicitly under existing authorization before running it. Do not install tooling or contact a chain during policy inspection.\n6. Prepare a candidate with exact source\u002Fdependency\u002Fcompiler input, ABI and bytecode identities, constructor\u002Frole\u002Fregistry configuration and test results. Obtain independent review of source and deployment assumptions. Report public-chain, registry, wallet\u002Fdevice, audit and target evidence separately. Broadcast only when separately authorized for the exact chain and operation.\n\n## Output\n\n- Host-owned source and explicit invariants, authority and unsupported behavior.\n- Reproducible pinned compilation, local successful\u002Freverting transaction evidence and resolved review findings.\n- An identified deployment candidate and target-specific prerequisites; local readiness does not imply a deployed or audited collection.\n\n## Boundaries\n\nERC-2981 reports royalties without universally enforcing them. Metadata grants no copyright or gameplay trust automatically. Token approvals are durable transfer authority, not login or burn permission. Ordinary public contract state cannot hide hands, decks or secrets.\n\nThe example sale\u002Freceiver\u002Fregistry harness under `.web3\u002Fcontracts\u002Ftest\u002F` is unrestricted test code. Never promote it as production settlement or deploy it with real value. A single atomic rollback test certifies no protocol, order replay policy, custom exchange or cross-chain trade. Escrow\u002Fstrict locks, proxies, economics and externally authorized crafting\u002Frewards require their own reviewed designs. No live deployment, player key, hosted service, license acceptance or paid action follows from selecting this skill.\n",{"name":5,"engines":44,"description":7},[45],"AGNOSTIC","main","c88f4c5f7ece8057ad15e220a7020f8446e0ba80","skills\u002Fbuild-evm-game-contracts",3,"https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera","https:\u002F\u002Fhephaera.com\u002F","https:\u002F\u002Fgithub.com\u002FTimothyMeadows","http:\u002F\u002Fwww.timothymeadows.com","Software & AI Systems Architect | Distributed Systems & Agentic Platforms","2026-11-13 03:52:23",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add TimothyMeadows\u002FHephaera --skill build-evm-game-contracts",{"tool":62,"command":63},"bunx","bunx skills add TimothyMeadows\u002FHephaera --skill build-evm-game-contracts",{"tool":65,"command":66},"pnpm","pnpm dlx skills add TimothyMeadows\u002FHephaera --skill build-evm-game-contracts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fbuild-evm-game-contracts\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",282,"https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fbuild-evm-game-contracts\u002Fagents\u002Fopenai.yaml",[77,98,119,138,156,175],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":39},"01M70V3EJ7JDFDFJ3XTKRGKRBP","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.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fverify-web3-game-lifecycle\u002FSKILL.md",[],[23,26,84,85,86,29,87,88,89,90,91,92,93,34,94,95,96,97],"lifecycle","verify web3 game lifecycle","web3","evidence","readiness","release readiness","Wallet","recovery","properties","release","canonical","asset","ownership","trading",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"01M70V3CS767H4M1FP4C2A7K51","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\u002FERC1155 inventory, reorg recovery, reservations, or transfer-during-match rules.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fverify-onchain-game-assets\u002FSKILL.md",[],[23,105,26,106,107,108,109,38,110,111,112,113,32,31,114,115,91,116,117,118],"onchain","game assets","assets","verify onchain game assets","chain","inventory","reservations","design","erc721","collection","on-chain","at","blocks","reconcile",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":39},"01M70TZYWE48MTM8CGGDMWSJDN","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.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fplan-web3-game-assets\u002FSKILL.md",[],[23,126,106,107,127,86,128,129,130,131,109,132,84,133,134,135,136,95,137],"plan","plan web3 game assets","supply","opt","immutable","rights","dependencies","token","base","define","ethereum","identity",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":39},"01M70TYYZ7SPZ7PE6A6GQ5RXQ9","integrate-game-wallets","Integrate explicit player-wallet connection, scoped SIWE authentication, authority invalidation and reviewed target-specific handoff without application-held player keys.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fintegrate-game-wallets\u002FSKILL.md",[],[23,145,146,147,148,90,149,150,36,151,152,153,154,155],"integrate game wallets","integrate","wallets","siwe","keys","authentication","scoped","connection","authority","application","handoff",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"01M70TYX656BP1R0KWMYRX437R","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.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fintegrate-game-asset-trading\u002FSKILL.md",[],[23,163,146,95,97,164,165,38,151,166,32,167,168,29,169,170,171,172,173,174],"integrate game asset trading","reconciliation","idempotent operations","retries","listing","idempotent","nft","approvals","operations","marketplace","integration","intents",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":186,"publishedAt":39},"01M6ES7KY8K93QWQ83R063FN6K","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.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fthreejs-build-code-models\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":184,"taxonomyTypeDesc":185},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[187,20,188,189,190,191,192,193,194,195,196,197,198,199,200,32,201,202,203,204],"code","models","threejs build code models","Code Models","threejs","mesh","deterministic","brief","three","model","runtime","pipeline","Art","generated","review","text","javascript","references"]