nft-standards

Implement ERC-721 and ERC-1155 NFT contracts with metadata, royalties, and minting logic.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill nft-standards-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nft-standards
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/nft-standards
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill nft-standards-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing NFT smart contracts from scratch is error-prone and requires deep knowledge of token standards, metadata formats, and marketplace compatibility. This Skill provides production-ready Solidity patterns for ERC-721 and ERC-1155 tokens so developers can ship NFT collections, marketplaces, and digital asset systems without reinventing core logic. ## Core Features & Use Cases - ERC-721 & ERC-1155 Implementations: Complete OpenZeppelin-based contracts with supply caps, mint pricing, batch minting, and burn logic. - Metadata Handling: Patterns for both off-chain IPFS metadata (JSON with attributes) and fully on-chain Base64-encoded metadata with SVG generation. - Advanced Token Features: EIP-2981 royalties, soulbound (non-transferable) tokens, dynamic NFTs with evolving state, and gas-optimized ERC721A minting. - Use Case: A game studio needs in-game items as ERC-1155 tokens with per-item supply caps and batch minting; this Skill provides the complete contract structure ready to customize. ## Quick Start Ask the AI to create an ERC-721 NFT collection with a 10000 max supply, 0.08 ETH mint price, and IPFS metadata using the nft-standards skill.

Frequently Asked Questions about nft-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an ERC-721 NFT contract in Solidity?

Extend OpenZeppelin's ERC721URIStorage and ERC721Enumerable, then add a mint function with supply and payment checks. Set a max supply, mint price, and per-transaction limit, and generate token URIs pointing to IPFS metadata.

ERC-721 vs ERC-1155: which token standard should I use?

ERC-721 suits unique one-of-one assets like art or collectibles, while ERC-1155 handles multiple token types in one contract, ideal for game items with quantities. ERC-1155 also supports batch minting and transfers, reducing gas costs.

How do I add royalties to an NFT contract?

Implement the EIP-2981 interface by adding a royaltyInfo function that returns a recipient address and royalty amount calculated from the sale price. Marketplaces that support EIP-2981 will automatically honor these royalties on secondary sales.

Should NFT metadata be stored on-chain or on IPFS?

IPFS metadata is cheaper and supports rich images, but depends on external file availability. On-chain metadata encodes JSON and SVG directly in the contract using Base64, guaranteeing permanence at higher gas cost.

How do I make a non-transferable soulbound token?

Override the _beforeTokenTransfer hook to revert unless the sender or recipient is the zero address, allowing only minting and burning. This blocks all transfers between wallets while still letting owners destroy their token.

How can I reduce gas costs for large NFT mints?

Use ERC721A instead of standard ERC721, which stores ownership data once per batch rather than per token. This significantly lowers gas when users mint multiple tokens in a single transaction.