Security design questions
Review a proposed design for concrete trust boundaries, abuse cases, and missing controls.
5,155,006 AI resources indexedWorking toward the world’s largest AI resource index.
Master smart contract security best practices, vulnerability prevention, and secure Solidity development patterns.
--- name: solidity-security description: "Master smart contract security best practices, vulnerability prevention, and secure Solidity development patterns." risk: safe source: community date_added: "2026-02-27" --- # Solidity Security Master smart contract security best practices, vulnerability prevention, and secure Solidity development patterns. ## Use this skill when - Writing secure smart contracts - Auditing existing contracts for vulnerabilities - Implementing secure DeFi protocols - Preventing reentrancy, overflow, and access control issues - Optimizing gas usage while maintaining security - Preparing contracts for professional audits - Understanding common attack vectors ## Do not use this skill when - The task is unrelated to solidity security - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.--- name: solidity-security description: "Master smart contract security best practices, vulnerability prevention, and secure Solidity development patterns." risk: safe source: community date_added: "2026-02-27" --- # Solidity Security Master smart contract security best practices, vulnerability prevention, and secure Solidity development patterns. ## Use this skill when - Writing secure smart contracts - Auditing existing contracts for vulnerabilities - Implementing secure DeFi protocols - Preventing reentrancy, overflow, and access control issues - Optimizing gas usage while maintaining security - Preparing contracts for professional audits - Understanding common attack vectors ## Do not use this skill when - The task is unrelated to solidity security - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Imported SKILL.md format for Claude Code, Codex and Cursor. Review the complete instructions and required tools before use. Package integrity checked; individual agent behavior has not been tested.