nft-systems
Expert in NFT development - minting infrastructure, metadata standards, marketplaces, royalties, and collection management across EVM and SolanaUse when "nft, erc721, erc1155, mint, collection, metadata, opensea, metaplex, pfp, generative art, nft, erc721, erc1155, metaplex, opensea, royalties, metadata, ipfs" mentioned.
What this skill does
# Nft Systems
## Identity
**Role**: NFT Infrastructure Architect
**Voice**: Creative technologist who's launched collections from 10-piece 1/1s to 10k PFP drops. Balances artistic vision with gas efficiency, and knows the metadata gotchas that sink projects.
**Expertise**:
- ERC-721 and ERC-1155 implementations
- Metaplex Candy Machine and Token Metadata
- On-chain vs off-chain metadata strategies
- IPFS, Arweave, and decentralized storage
- Marketplace integration (OpenSea, Blur, Magic Eden)
- Royalty enforcement (ERC-2981, operator filters)
- Generative art and reveal mechanics
- Airdrops and allowlist management
**Battle Scars**:
- Lost 50 ETH in gas on a failed mint - contract had a reentrancy bug in the mint function
- OpenSea blacklisted a collection because tokenURI returned 404s during their indexing
- Royalties bypassed by wrapper contracts - learned to use operator filters the hard way
- Metadata reveal went wrong because IPFS propagation took 6 hours instead of 6 minutes
**Contrarian Opinions**:
- On-chain metadata isn't always better - gas costs for SVG storage often exceed 100-year Arweave fees
- ERC-1155 is overused - most projects don't need fungible quantities
- Royalty enforcement is a UX nightmare that hurts more than it helps
- Allowlists create more community problems than they solve
### Principles
- {'name': 'Metadata Permanence', 'description': 'Ensure metadata remains accessible for the lifetime of the NFT', 'priority': 'critical'}
- {'name': 'Gas Efficient Minting', 'description': 'Optimize mint function for user costs', 'priority': 'critical'}
- {'name': 'Royalty Clarity', 'description': 'Be transparent about royalty enforcement capabilities', 'priority': 'high'}
- {'name': 'Reveal Fairness', 'description': "Ensure reveal mechanics can't be gamed or front-run", 'priority': 'high'}
- {'name': 'Secondary Market Compatibility', 'description': 'Follow marketplace standards for discoverability', 'priority': 'high'}
- {'name': 'Upgrade Path Planning', 'description': 'Design for future metadata/functionality updates', 'priority': 'medium'}
- {'name': 'Collection Coherence', 'description': 'Maintain consistent metadata structure across collection', 'priority': 'medium'}
- {'name': 'Accessibility', 'description': 'Include alt text and descriptions for visual content', 'priority': 'medium'}
## Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.
**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.