security

Provide security coding guidelines for frontend and backend vulnerability prevention.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/juchanhwang/missionary --skill security-juchanhwang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/juchanhwang/missionary/tree/main/.claude/skills/security
Command: npx skills add https://github.com/juchanhwang/missionary --skill security-juchanhwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides comprehensive security coding guidelines to preempt common vulnerabilities in both frontend (XSS, sensitive data exposure) and backend (injections, authentication/authorization, CORS) and to guide secure code reviews, secure implementations, and safe input handling.

Core Features & Use Cases

  • Frontend security practices: XSS prevention, safe handling of user input, avoid exposing secrets, and proper input validation before rendering.
  • Backend security practices: robust authentication/authorization, injection prevention (SQL/NoSQL), proper CORS configuration, secure error handling, and safe environment variable usage.
  • Use cases: When designing or reviewing features, refer to these rules to ensure security by default and to reduce risk in production systems.

Quick Start

Review these guidelines during code development and code reviews to ensure security by default.

Frequently Asked Questions about security

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

FAQPage Schema
How do I prevent XSS and injection vulnerabilities in frontend and backend code?

To prevent XSS and injection vulnerabilities, apply secure coding guidelines for safe input validation, robust authentication, and proper CORS configuration across frontend and backend contexts. These rules encode security requirements directly into your development workflows.

What are the best practices for secure authentication and authorization implementation?

Secure authentication and authorization practices involve enforcing robust backend access controls, preventing SQL or NoSQL injection, and safely handling environment variables. Following structured coding guidelines ensures security by default and reduces production risks during feature design and review.

How do I handle user input validation safely before rendering on the frontend?

Safe user input validation requires checking and sanitizing all inputs before rendering on the frontend to prevent XSS and sensitive data exposure. Secure coding rules provide actionable steps to ensure safe input handling and reduce vulnerability risks.

How do I configure CORS properly to avoid sensitive data exposure in production systems?

Proper CORS configuration prevents unauthorized cross-origin requests and sensitive data exposure in production systems. Backend security guidelines define actionable coding rules for safe environment variable usage and secure error handling to mitigate these risks.

Do I need specific frameworks to apply these secure coding guidelines?

No specific frameworks are required to apply these secure coding guidelines. They provide general actionable rules and review practices for preventing common frontend and backend vulnerabilities, ensuring security by default across any development workflow.

When should I refer to secure coding rules during the development workflow?

You should refer to secure coding rules when designing, implementing, or reviewing features to ensure security by default. Applying these guidelines during code development and code reviews helps preempt common vulnerabilities and reduce risk in production systems.