nft launch command center

The problem

Managing an NFT launch involves coordinating disparate workstreams like generative art, smart contract security, and mint economics. Missing a single dependency or failing to verify metadata against contract supply leads to broken mints and lost capital.

What it does

• Orchestrates 10 specialist sub-skills across the entire NFT lifecycle from concept validation to post-launch reconciliation.
• Enforces strict dependency gates, preventing mainnet deployment if security audits or testnet verifications are missing.
• Maintains a persistent Project State document to track status, blockers, and verified decisions across multiple sessions.
• Performs automated cross-checks between contract supply, metadata count, and website documentation to catch mismatches.
• Distinguishes between EVM compatibility and specific wallet support (like Robinhood Wallet) to prevent false integration claims.

Frameworks & tools

EVM-compatible chains (Ethereum, Robinhood Chain, Polygon, etc.), Hardhat/Foundry, IPFS/Arweave, and standard NFT metadata schemas.

Why this beats prompting it yourself

A standard LLM will often "hallucinate" a successful deployment or skip boring QA steps to please the user. This skill functions as a launch control system that defaults to BLOCKED unless specific, verified evidence is provided for every stage of the pipeline.

Use cases

• Coordinating a multi-stage generative NFT drop from art generation to mint.
• Managing change-impact analysis when mint price or supply targets shift mid-development.
• Executing a mandatory pre-flight security checklist before mainnet contract deployment.
• Generating a post-launch reconciliation report to audit treasury and token distribution.

Known limitations

Requires the user to manually carry the project state file between sessions if the host environment lacks persistent storage. Cannot execute blockchain transactions directly.