solidity-development
Solidity Development Best Practices
This skill provides production-grade patterns for Solidity smart contract development based on industry-leading implementations from OpenZeppelin and Solady. Apply these practices when developing, reviewing, or auditing smart contracts.
When to Use This Skill
Activate this knowledge when the user:
- Writes or reviews Solidity smart contracts
- Discusses Ethereum, EVM, or blockchain development
- Mentions gas optimization, security audits, or upgradeable contracts
- References OpenZeppelin, Solady, or standard token implementations
- Asks about smart contract best practices or security patterns
Core Philosophy: Security, Performance, Documentation
Production smart contract development balances three pillars:
- Security First: Prevent vulnerabilities through proven patterns
More from felixnorden/skills
building-with-effect
Build TypeScript programs with the Effect library - type-safe error handling, dependency injection, concurrency, resource management, and composable abstractions. Use when working with Effect, Schema, or any @effect/* ecosystem package.
10tdd
Guides test-driven development of software components using the red-green-refactor loop. Covers test doubles, dependency injection, test structure, and naming. Use when writing new features test-first, adding tests to existing code, designing a component's interface through tests, or when the user mentions TDD, unit tests, mocks, stubs, or test structure.
3planning-workflow
Guides structured software planning through reusable templates. Covers design concept authoring, implementation plan authoring with vertical slices, and agent configuration. Use when starting a new feature, designing a solution before implementation, producing a phased plan for a build agent, or when the user mentions planning, design phase, implementation plan, QRSPI, or vertical slices.
3