# Build Standards-Compliant NFT Contracts

NFT contracts require careful choices across token standards, metadata, royalties, and minting. This skill provides practical Solidity patterns and implementation guidance.

## Install

```bash
npx skillstore add sickn33/nft-standards
```

## Metadata

- Status: approved
- Slug: sickn33-nft-standards
- Skillstore revision: r2
- Version status: missing
- Tree hash: 3326b7fce7bc2050d96b87250bbbff564e43489877780a16985b2270f889800b
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/nft-standards
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/sickn33-nft-standards
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-nft-standards/manifest

## Capabilities

- Explains when to use ERC-721 or ERC-1155.
- Provides Solidity examples for minting, burning, supply limits, and metadata.
- Shows off-chain IPFS and on-chain metadata structures.
- Demonstrates EIP-2981 royalty reporting and fee limits.
- Covers soulbound, dynamic, and ERC721A contract patterns.

## Use Cases

- Plan a Digital Art Collection: Compare ERC-721 designs, metadata storage, supply limits, mint pricing, and royalty support.
- Model Multi-Token Game Items: Design ERC-1155 item types, batch minting, burning, supply controls, and shared metadata.
- Review an NFT Architecture: Check token standards, metadata choices, transfer rules, royalties, and gas optimization before implementation.

## Prompt Templates

### Choose an NFT Standard

```
Compare ERC-721 and ERC-1155 for [project]. Consider asset uniqueness, editions, batch transfers, metadata, and marketplace compatibility.
```

### Design Collection Metadata

```
Design metadata for [collection] using [IPFS or on-chain storage]. Include traits, image handling, update policy, and marketplace compatibility.
```

### Draft a Minting Contract

```
Draft an educational [ERC-721 or ERC-1155] contract for [requirements]. Include supply limits, access control, payments, events, and testing notes.
```

### Review an Advanced NFT Design

```
Review this NFT design: [design]. Analyze authorization, supply accounting, metadata integrity, royalties, transfer restrictions, gas costs, and upgrade risks.
```

## Limitations

- Examples are educational and require security review before deployment.
- Some examples omit imports, helper functions, tests, and deployment configuration.
- Library APIs may differ across OpenZeppelin and ERC721A versions.
- The skill does not audit deployed contracts or verify marketplace behavior.

## Best Practices

- Pin dependency versions and match examples to the selected library release.
- Test authorization, supply boundaries, payment handling, metadata, and interface support.
- Obtain an independent security review before deploying contracts that manage assets or payments.

## Anti Patterns

- Do not deploy tutorial snippets without compilation, tests, and security review.
- Do not allow public state updates when an authorized issuer or oracle should control them.
- Do not rely on marketplace royalty enforcement without documenting its limitations.

## Security Audit

- Audited at: 2026-08-04T16:02:51.611\+00:00
- Summary: All static alerts are false positives caused by Solidity require statements and Markdown backticks, with no host command execution present. Two example contracts contain genuine business logic risks involving unrestricted progression and soulbound token minting.

## Stats

- Views: 138
- Downloads: 8
- Favorites: 0
- Popularity score: 0