技能 nft-standards
📦

nft-standards

安全

Implement NFT Smart Contracts

也可從以下取得: wshobson

Build secure NFT collections using ERC-721 and ERC-1155 standards with proper metadata, royalties, and marketplace integration.

支援: Claude Codex Code(CC)
🥉 75 青銅
1

下載技能 ZIP

2

在 Claude 中上傳

前往 設定 → 功能 → 技能 → 上傳技能

3

開啟並開始使用

測試它

正在使用「nft-standards」。 Create an ERC-721 contract with minting

預期結果:

  • Complete Solidity contract using OpenZeppelin ERC721URIStorage
  • Minting function with quantity limits and payment validation
  • URI generation for IPFS metadata
  • Withdraw function for collecting payments

正在使用「nft-standards」。 Add royalties to my NFT collection

預期結果:

  • IERC2981 implementation for royalty standard
  • Royalty fee configuration (default 5-10%)
  • Marketplace integration notes for OpenSea, LooksRare

安全審計

安全
v1 • 2/24/2026

All 38 static findings are false positives. The skill contains educational Solidity code examples for NFT standards (ERC-721, ERC-1155). The 'require' statements are standard contract validation, 'IERC2981' references are legitimate royalty standards, and 'shell command' flags are misclassified Solidity syntax. This is a legitimate developer tool for NFT smart contract development.

1
已掃描檔案
398
分析行數
0
發現項
1
審計總數
未發現安全問題
審計者: claude

品質評分

38
架構
100
可維護性
85
內容
50
社群
100
安全
100
規範符合性

你能建構什麼

Create NFT Art Collection

Build a gas-optimized NFT collection with reveal mechanism and royalty distribution

Build Gaming Item System

Implement multi-token standard for game assets with varying supply and attributes

Create Credential System

Use soulbound tokens for non-transferable credentials and achievements

試試這些提示

Basic NFT Contract
Create an ERC-721 NFT contract with OpenZeppelin. Include minting with payment, URI storage, and withdrawal function.
Gaming Items Contract
Implement an ERC-1155 contract for game items with max supply limits, batch minting, and burn functionality.
Royalty-Enabled Marketplace NFT
Create an NFT contract with EIP-2981 royalties, configurable fee recipient, and marketplace compatibility.
Dynamic Evolving NFT
Build a dynamic NFT that changes based on external state. Include experience points and level-up mechanics.

最佳實務

  • Use OpenZeppelin contracts for battle-tested security
  • Pin IPFS metadata with a pinning service for reliability
  • Implement EIP-2981 royalties for marketplace compatibility
  • Use ERC721A for gas-optimized batch minting

避免

  • Storing images directly on-chain (use IPFS or external hosting)
  • Hardcoding royalty addresses without upgradeability
  • Skipping access controls on mint and burn functions
  • Not implementing supportsInterface for full compatibility

常見問題

What is the difference between ERC-721 and ERC-1155?
ERC-721 is for unique non-fungible tokens where each token is one-of-a-kind. ERC-1155 is a multi-token standard that supports both fungible (currency) and non-fungible tokens in a single contract, ideal for gaming.
How do I add royalties to my NFT collection?
Implement the EIP-2981 royalty standard. This allows marketplaces like OpenSea and LooksRare to automatically calculate and distribute royalties on secondary sales.
What is IPFS and why do NFTs use it?
IPFS is a distributed file storage system. NFTs store metadata (images, attributes) on IPFS because it provides permanent, decentralized storage without a single point of failure.
Can NFTs be made non-transferable?
Yes, soulbound tokens (SBTs) use the _beforeTokenTransfer override to block transfers after minting. This is useful for credentials and achievements.
What is ERC721A and why is it popular?
ERC721A is a gas-optimized implementation of ERC-721 that reduces minting costs by up to 90% when minting multiple tokens in a single transaction.
Do I need to test NFT contracts before deployment?
Yes, always test thoroughly. Use tools like Hardhat or Foundry to write comprehensive test suites covering minting, transfers, approvals, and edge cases.

開發者詳情

檔案結構

📄 SKILL.md