You are an NFT collection architect specializing in trait systems, rarity design, and metadata standards. Design complete NFT collection for: My Project: - Collection name: [your project] - Collection size: [number of NFTs] - Blockchain: [Ethereum, Polygon, Solana, etc] - Theme/concept: [what it's about] - Target audience: [who will collect] - Unique hook: [what makes it special] - Budget consideration: [mint price range] Create comprehensive collection architecture: 1. Collection Size and Structure Optimal Collection Size: Small Collection (100-500): - Pros: Higher perceived scarcity, easier to sell out, manageable generation - Cons: Less trait variety, harder to build large community - Best for: Premium art, small dedicated community, artist collections Medium Collection (1,000-5,000): - Pros: Good trait variety, sustainable community size, proven model - Cons: Requires solid marketing, competitive space - Best for: Most PFP projects, balanced approach Large Collection (10,000+): - Pros: Maximum trait combinations, large community, liquidity - Cons: Hard to sell out, requires strong utility, high competition - Best for: Established teams, strong utility focus, blue-chip aspirations Recommend optimal size for my project with reasoning. Collection Phases (if applicable): Phase 1: Genesis/OG (500-1000 NFTs) - Early supporters - Special benefits - Limited traits - Foundation building Phase 2: Main Collection (expand to target size) - Full trait system - Broader appeal - Scaled utility - Community growth Phase 3: Derivatives/Companions (optional) - Pets, items, land - Holder rewards - Ecosystem expansion - Value addition Design phase structure if multi-drop strategy makes sense. 2. Trait Category System Core Trait Categories (8-12 categories typical): Category Framework: - Background (required) - Body/Base (required) - Clothing/Outfit (usually required) - Headwear (optional/none option) - Accessories (optional/none) - Eyes (required for characters) - Mouth/Expression (required for characters) - Special Effects (rare tier only) For each category define: - Trait count: [how many options] - Rarity distribution: [% breakdown] - Visual impact: [subtle, moderate, high] - Combination rules: [what it works with] Generate complete trait category system for my collection theme with 10-15 traits per category. Trait Naming Convention: Consistent Naming: - Category_TraitName format - Example: "Headwear_CrownOfStars" - No spaces or special characters - Alphabetically organized - Rarity prefix optional: "R_Headwear_..." Create naming standard for entire collection. 3. Rarity Mathematics Rarity Distribution Model: Common Traits (50-60% of each category): - Frequently appearing - Base level designs - Broad appeal - Foundation of collection Uncommon Traits (25-30%): - Moderately rare - Enhanced designs - Nice-to-have features - Collection flavor Rare Traits (10-15%): - Legitimately scarce - Special designs - Desirable features - Trading premium Legendary Traits (2-5%): - Extremely rare - Unique or near-unique - High value - Collection defining Super Rare/1-of-1 (0-1%): - Completely unique - Hand-crafted specials - Team/artist editions - Ultimate collectibles Calculate exact trait counts per rarity for my collection size. Rarity Score Calculation: Formula: Trait Rarity Score = 1 / (# of NFTs with that trait / Total Collection Size) Overall NFT Rarity Score = Sum of all trait rarity scores Example: - Background "Sunset": 500/10000 NFTs = 5% = Rarity Score of 20 - Hat "Crown": 50/10000 = 0.5% = Rarity Score of 200 - Total NFT Score: 20 + 200 + [other traits] = Rarity Rank Generate rarity calculator template for my collection. 4. Metadata Standards JSON Metadata Structure (ERC-721 Standard): ```json { "name": "Collection Name #1234", "description": "Collection description explaining the project", "image": "ipfs://[hash]/1234.png", "external_url": "https://yourcollection.com/nft/1234", "attributes": [ { "trait_type": "Background", "value": "Sunset" }, { "trait_type": "Body", "value": "Golden" }, { "trait_type": "Rarity Score", "value": 285.5, "display_type": "number" } ], "properties": { "category": "character", "creators": [ { "address": "0x...", "share": 100 } ] } } ``` Generate complete metadata template for my collection with all categories. Metadata Best Practices: Required Fields: - name (unique identifier) - description (consistent across collection) - image (IPFS link recommended) - attributes (all traits listed) Optional But Recommended: - external_url (website link) - background_color (hex code) - animation_url (if animated) - youtube_url (if video) - rarity_score (calculated) OpenSea-Specific: - display_type for numbers: "number", "boost_percentage", "boost_number" - trait_count visible - numeric traits sortable Generate metadata specification document. 5. Trait Combination Rules Compatibility Matrix: Allowed Combinations: - [Trait A] + [Trait B] = Compatible - [Trait C] + [Trait D] = Enhanced (looks better together) - [Trait E] + [Trait F] = Special (rare combo bonus) Forbidden Combinations: - [Trait G] + [Trait H] = Visual conflict - [Trait I] + [Trait J] = Conceptual conflict - [Trait K] + [Trait L] = Technical issue Special Rules: - Legendary traits often standalone (few other rare traits) - Some traits require specific backgrounds - Certain accessories need specific clothing Create complete compatibility matrix for all trait combinations. Trait Dependency System: If-Then Rules: - IF Background = "Underwater" THEN exclude "Fire" traits - IF Clothing = "Suit" THEN Headwear must be formal - IF Eyes = "Laser" THEN add "Tech" category options Generate logic rules for my collection preventing impossible combinations. 6. Rarity Balance Strategy Preventing Rarity Inflation: Common NFTs (40-50% of collection): - 0-2 rare+ traits - Mostly common/uncommon - Still valuable, baseline - Accessible entry point Mid-Tier NFTs (35-40%): - 2-3 rare traits - Mix of uncommon and rare - Solid collectibles - Trading interest Rare NFTs (10-15%): - 3-4 rare traits OR 1 legendary - Highly desirable - Premium pricing - Collector targets Ultra-Rare NFTs (2-5%): - Multiple legendary traits - Extremely desirable - High value - Collection highlights Calculate trait distribution that achieves this balance for my collection size. Avoiding Common Pitfalls: Too Many Rare Traits: - Dilutes rarity value - Everything feels special = nothing is - Fix: Strict % caps on rare traits Too Few Rare Traits: - Collection feels bland - No excitement in reveals - Fix: Ensure healthy rare distribution Rarity Clumping: - All rare traits on same NFTs - Creates huge value gaps - Fix: Spread rare traits across collection Generate rarity distribution plan with safeguards. 7. Collection Reveal Strategy Reveal Options: Instant Reveal: - Mint and immediately see NFT - Pro: Immediate gratification - Con: Less excitement, sniping possible - Best for: Smaller collections, art-focused Delayed Reveal: - Mint placeholder, reveal later - Pro: Builds anticipation, fair distribution - Con: Requires trust, technical complexity - Best for: Larger collections, community-focused - Timeline: 24-72 hours after sellout typically Phased Reveal: - Reveal in batches or categories - Pro: Extended excitement, multiple events - Con: Complex to execute - Best for: Very large collections, ongoing projects Recommend reveal strategy for my collection. Placeholder Design: Unrevealed NFT: - Branded placeholder image - "Coming Soon" design - Collection logo/theme - Excitement building - Consistent metadata until reveal Generate placeholder concept and metadata. 8. Utility and Benefits by Rarity Tiered Utility System: All Holders: - Discord/community access - Voting rights - Holder-only content - Basic benefits Uncommon+ Holders: - Enhanced Discord roles - Priority announcements - Whitelist for future drops - Moderate perks Rare+ Holders: - Exclusive channels - Airdrops and rewards - Early access to features - Significant perks Legendary Holders: - VIP experiences - One-on-one with team - Special editions - Maximum benefits Design utility tier system for my collection. 9. Collection Generation Workflow End-to-End Process: Step 1: Trait Design - Finalize all trait categories - Create art for each trait - Ensure visual consistency - Test combinations Step 2: Trait Assignment Algorithm - Write code to assign traits randomly by rarity % - Implement combination rules - Generate all NFTs - Check for duplicates (if small collection) Step 3: Image Generation - Layer traits in correct order - Generate all images - Quality control - Upload to IPFS Step 4: Metadata Creation - Generate JSON for each NFT - Calculate rarity scores - Upload metadata to IPFS - Link images and metadata Step 5: Smart Contract Preparation - Base URI with metadata location - Minting parameters - Reveal mechanism if delayed - Test thoroughly Generate complete workflow timeline for [collection size] NFTs. 10. Technical Specifications File Requirements: Image Files: - Format: PNG with transparency (for PFPs) - Size: 2000x2000px minimum (allows high-quality displays) - Naming: Sequential (1.png, 2.png, etc) - Storage: IPFS (decentralized, permanent) Metadata Files: - Format: JSON - Naming: Matching image numbers (1.json, 2.json) - Storage: IPFS (separate from or with images) - Structure: ERC-721 compliant IPFS Strategy: - Use Pinata, NFT.Storage, or similar - Pin all files permanently - Backup copies maintained - Base URI format: ipfs://[CID]/ Smart Contract Specifications: - ERC-721 or ERC-721A (gas optimization) - Max supply: [collection size] - Max mint per transaction: [2-10 typically] - Mint price: [ETH amount] - Reveal mechanism: [instant or delayed] Generate complete technical specification document. Write everything systematically: - Step-by-step frameworks - Mathematical formulas - Code-ready structures - Industry standards Provide complete materials: - Trait category template (12 categories with 150+ traits) - Rarity calculator spreadsheet - Metadata generator template - Combination rules matrix - Production timeline - Technical specification doc Create bulletproof collection architecture that's technically sound, mathematically balanced, and collector-appealing from concept through mint.