Crypto Token Creator

For meme coins or simple utility tokens, keep it lean — don't over-engineer. For governance tokens or DeFi protocols, include the full stack.

Step 2: Read the Chain-Specific Reference

Based on the target chain, read ONE of these reference files. They contain the contract templates, toolchain setup, and deployment patterns for each ecosystem:

• Ethereum/EVM chains → Read references/ethereum.md

  • Covers: Solidity, Hardhat/Foundry, OpenZeppelin, ERC-20/721/1155
  • EVM-compatible: Polygon, BSC, Arbitrum, Base, Avalanche, Optimism

• Solana → Read references/solana.md

  • Covers: Anchor framework, SPL tokens, Metaplex NFTs, Token-2022

• TON → Read references/ton.md

  • Covers: Tact/FunC, Jetton standard, TON NFT, Blueprint SDK

• Multi-chain → Read the primary chain's reference, then cross-reference others as needed

Step 3: Generate the Project

Create a complete project structure. The exact layout depends on the chain (see references), but every project should include:

Required outputs:

1. Smart contract(s) — the token contract with all requested features
2. Deployment script — parameterized, targeting testnet by default
3. Test file — at minimum, tests for: deployment, transfers, access control, edge cases
4. Configuration — chain config, compiler settings, environment template
5. README.md — setup instructions, deployment steps, contract addresses placeholder

Optional outputs (include when relevant):

6. Tokenomics document — supply breakdown, vesting schedule, distribution plan
7. Verification script — for Etherscan/Solscan/Tonviewer source verification
8. Frontend mint page — simple HTML/React page for minting (NFTs) or claiming (airdrops)
9. Whitepaper draft — project overview, utility description, roadmap placeholder
10. Liquidity guide — DEX listing steps (Uniswap/Raydium/STON.fi)

Step 4: Security Checklist

Every contract must pass these checks before delivery. Walk through each one and note any that apply:

Critical (must fix before deploy):

• Reentrancy — external calls before state changes? Use ReentrancyGuard or checks-effects-interactions
• Integer overflow — Solidity <0.8.0 without SafeMath? (0.8+ has built-in checks)
• Access control — admin functions properly gated? Ownable/AccessControl used?
• Approval race condition — ERC-20 approve() front-running? Use increaseAllowance
• Unchecked return values — low-level calls without checking success?

Important (should fix):

• Centralization risk — single owner with too much power? Consider multisig or timelock
• Front-running — commit-reveal needed for fair launches?
• Gas optimization — unnecessary storage reads? Use memory/calldata appropriately
• Event emission — all state changes emit events for indexing?

For DeFi contracts specifically:

• Flash loan attacks — price manipulation via flash loans?
• Oracle manipulation — TWAP vs spot price?
• Sandwich attacks — slippage protection implemented?
• Infinite approval — can tokens be drained via approve?

Tell the user which items you checked and what the status is. If anything is flagged, explain the risk and the fix applied.

Step 5: Deployment Guide

Provide step-by-step deployment instructions:

1. Environment setup (Node.js/Rust/TON CLI)
2. Install dependencies
3. Configure environment variables (RPC URL, private key — remind user NEVER to commit keys)
4. Compile contracts
5. Deploy to testnet first (always!)
6. Run verification
7. Test on testnet thoroughly
8. Deploy to mainnet (with gas estimation)

Always remind the user:

• Test on testnet first — never deploy untested contracts to mainnet
• Audit before mainnet — for any contract holding significant value, get a professional audit
• Private key safety — use .env files, never hardcode, add .env to .gitignore
• Contract is immutable — once deployed, it cannot be changed (unless using proxy pattern)

Tokenomics Templates

When the user wants tokenomics documentation, use these frameworks:

Simple token (meme/utility):

• Total supply, decimal places
• Initial distribution (team, community, liquidity, treasury)
• Lock/vesting for team tokens
• Tax mechanism (if any) — buy/sell percentages, distribution of fees

Governance token:

• All of the above, plus:
• Voting power calculation
• Quorum requirements
• Proposal threshold
• Delegation mechanics

DeFi token:

• All of the above, plus:
• Emission schedule (if inflationary)
• Staking rewards APY model
• Liquidity incentives
• Protocol fee structure
• Treasury management

Important Notes

• Legal disclaimer: Always include a note that token creation may be subject to securities regulations depending on jurisdiction. The user should consult legal counsel before launching a token that could be classified as a security.

• No rugpull patterns: Never include hidden mint functions, blacklist abuse mechanisms, honeypot logic, or any pattern designed to defraud token holders. If the user asks for these, explain why they are harmful and offer legitimate alternatives.

• Gas costs: Mention estimated deployment gas costs for the target chain.

• Testnet faucets: Include links to relevant testnet faucets (Sepolia, Solana devnet, TON testnet).3b:["$","$L3f",null,{"content":"$40","frontMatter":{"name":"crypto-token-creator","description":"Generate production-ready cryptocurrency tokens, NFT collections, and DeFi primitives across Ethereum (ERC-20/721/1155), Solana (SPL/Metaplex), and TON (Jetton/NFT). Use this skill whenever the user mentions creating a token, launching a coin, minting NFTs, building a token contract, deploying a smart contract for crypto, tokenomics design, creating a meme coin, launching a DeFi protocol, staking contract, liquidity pool, or any blockchain token-related development task. Also triggers on mentions of ERC-20, SPL token, Jetton, NFT collection, token generator, smart contract deployment, airdrop contract, vesting schedule, or token launch. Even if the user just says "I want to create my own cryptocurrency" or "help me launch a token", use this skill.\n"}}]