security-and-hardening
Guides secure coding practices like threat modeling, input validation, authentication hardening, dependency auditing, and privacy compliance when building or reviewing features that handle untrusted d
What it does
Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.
Quality judgment
Exceptionally thorough coverage spanning threat modeling, OWASP, SSRF, supply chain, privacy, and LLM-specific risks, with a well-organized three-tier rule system and actionable checklists. Concrete code examples are deferred to referenced files rather than shown inline, and the description contains a minor grammatical error, but the guidance itself is precise and actionable.