What problem does it solve?
Security-first development practices for web applications. Treat every external input as hostile, every secret as sacred, and every authorization check as mandatory. Security isn't a phase — it's a constraint on every line of code that touches user data, authentication, or external systems.
Core Features & Use Cases
- Three-Tier Boundary System: Always validate external input at the boundary, parameterize database queries, encode outputs, enforce HTTPS, set secure cookies, and run npm audit before releases.
- OWASP Top 10 Prevention: Implement protections against common weaknesses such as injection, broken authentication, and misconfigurations with concrete patterns and checks.
- Input Validation & Data Handling: Enforce strict input validation, proper output encoding, and safe handling of sensitive data, secrets, and tokens.
- Secrets & Configuration Management: Avoid hard-coded keys; recommend environment-based secrets management, rotation, and minimal privilege design.
Quick Start
Integrate security-first guidelines from this Skill into your codebase and start applying input validation, secret management, and defensive coding practices immediately.