security-guidelines

Standardize authentication, input validation, and data protection security practices.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/softmg/product-tracker --skill security-guidelines-softmg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-guidelines
Source: https://github.com/softmg/product-tracker/tree/main/.cursor/skills/security-guidelines
Command: npx skills add https://github.com/softmg/product-tracker --skill security-guidelines-softmg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security teams and developers often work with inconsistent practices across authentication, API security, and data handling. This Skill defines and centralizes security standards to reduce vulnerabilities and compliance gaps.

Core Features & Use Cases

  • Standardized authentication and session management guidelines (hashing, CSRF, TLS, token handling)
  • API security guidance (HTTPS, rate limiting, CORS, error handling, logging)
  • Secrets management and data protection (encryption, secret rotation, secure storage)
  • Secure software development lifecycle guidance (dependency checks, OWASP alignment, auditing)
  • Use Case: when adding a new feature touching passwords or tokens, apply these guidelines to design secure flows.

Quick Start

Review these guidelines prior to implementing security-sensitive features to ensure compliance.

Frequently Asked Questions about security-guidelines

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

FAQPage Schema
What security practices should I follow for authentication flows and session management?

API security guidelines require enforcing HTTPS, applying rate limiting, configuring CORS, and implementing proper error handling and logging. These standardized practices protect endpoints from common vulnerabilities and ensure consistent security across services.

How do I manage secrets and protect sensitive data in my application?

Secrets management and data protection require implementing encryption, establishing secret rotation policies, and utilizing secure storage mechanisms. These centralized standards reduce the risk of accidental exposure and ensure compliance across development teams.

Does this align with OWASP guidelines for secure software development?

Yes, the guidelines align with OWASP standards and cover the secure software development lifecycle by enforcing dependency checks and auditing. This ensures continuous adherence to industry-recognized security baselines across web applications.

When should I review secure development guidelines before implementing new features?

Review these guidelines prior to implementing security-sensitive features like password handling, token management, or file uploads. Applying these centralized standards during the design phase ensures consistent practices and reduces vulnerabilities early.