security-hardening

Review and harden Vue, Nuxt, and TypeScript applications against OWASP Top 10 vulnerabilities.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/OktayCopurlu/ai-shared --skill security-hardening-oktaycopurlu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-hardening
Source: https://github.com/OktayCopurlu/ai-shared/tree/main/.github/workflows/skills/security-hardening
Command: npx skills add https://github.com/OktayCopurlu/ai-shared --skill security-hardening-oktaycopurlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend code touching user input, auth flows, dynamic rendering, and third-party dependencies is a common source of security vulnerabilities. This Skill provides a structured review process so security checks are applied consistently whenever changes cross a system boundary. ## Core Features & Use Cases - OWASP Top 10 Prevention: Applies input validation, auth pattern checks, and secrets management rules to Vue/Nuxt/TypeScript code. - Dependency Audit Workflow: Runs a five-question evaluation before adding dependencies (existing stack fit, bundle size, maintenance status, vulnerabilities, license) followed by npm audit or yarn audit. - Anti-Rationalization Guardrails: Counters common excuses like "it's behind auth" or "env vars are safe" with concrete security realities. - Use Case: When adding a form that accepts user input or integrating a new external service, activate this Skill to validate input handling, check for v-html injection risks, and audit any new dependencies. ## Quick Start Review my latest changes to the login form and user profile page for security vulnerabilities using the security-hardening checklist.

Frequently Asked Questions about security-hardening

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit npm dependencies for security vulnerabilities?▼

Run npm audit or yarn audit after adding any dependency to detect known vulnerabilities. Before adding, check bundle size on bundlephobia.com, verify active maintenance via last commit date and open issues, and confirm the license is MIT, Apache 2.0, or ISC.

How to prevent XSS when rendering dynamic content in Vue?▼

Avoid using v-html with user-controlled content, since it renders raw HTML and enables script injection. Validate and sanitize all user input at every boundary, including forms, URL params, and file uploads.

Are environment variables safe for storing secrets in frontend apps?▼

No. Environment variables in client-side builds are embedded into the JavaScript bundle and are publicly visible. Secrets must remain server-side only and never ship to the browser.

When should I apply security review to frontend code changes?▼

Apply security review whenever handling user input, adding or changing auth flows, rendering dynamic content, adding dependencies, or integrating external services. Any agent-generated code touching a system boundary also warrants a security pass.

Does input validation matter for authenticated users?▼

Yes. Authenticated users can still be attackers, so input validation is required at every boundary regardless of auth state. Being behind a login does not eliminate injection or abuse risks.