skills.rest
Tomy74-vsc
Tomy74-vscCOMMUNITY
Explore all skills by this author →
GitHub

brand-security-integrity

Enforce CSRF, RLS, message authorization, rate limiting, and Stripe webhook idempotence.

Updated Aug 16, 2025
Search Tags:#security#api#rate limiting#integrity#brand#stripe#csrf
One-click install
npx skills add https://github.com/Tomy74-vsc/cliprace --skill brand-security-integrity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brand-security-integrity
Source: https://github.com/Tomy74-vsc/cliprace/tree/main/.cursor/skills/brand-security-integrity
Command: npx skills add https://github.com/Tomy74-vsc/cliprace --skill brand-security-integrity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures robust security and data integrity for ClipRace brand features, preventing unauthorized access, data corruption, and payment fraud.

Core Features & Use Cases

  • Security Guardrails: Enforces CSRF token strength, RLS policies, and message authorization.
  • Rate Limiting: Implements effective rate limiting keyed by user, IP, and user agent.
  • Payment Integrity: Ensures Stripe webhook idempotence and secure payment flows.
  • Use Case: When refactoring the brand's contest creation API, use this skill to verify that all new endpoints correctly implement CSRF protection, enforce RLS for contest ownership, and handle Stripe payments securely.

Quick Start

Use the brand-security-integrity skill to review the security posture of the new brand messaging API endpoints.

Frequently Asked Questions about brand-security-integrity

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

FAQPage Schema
How do I enforce rate limiting keyed by user, IP, and user agent for backend APIs?▼

This Skill enforces rate limiting by tracking combined user, IP, and user agent identifiers to prevent API abuse across brand flows, ensuring backend endpoints maintain data integrity and block unauthorized access.

How do I ensure Stripe webhook idempotence and secure payment flows?▼

Stripe webhook idempotence is enforced by validating payment integrity guardrails that prevent duplicate webhook processing and secure payment flows against fraud during brand API transactions.

What security policies do I need for contest ownership and brand messaging authorization?▼

You need Row Level Security (RLS) policies for contest ownership and strict message authorization rules across brand, contest, and creator endpoints to prevent data corruption and unauthorized access.

How do I verify CSRF token strength when refactoring brand API endpoints?▼

CSRF token strength is verified by applying security guardrails during API refactoring to ensure all new endpoints touching brand flows correctly implement cross-site request forgery protection.

When should I apply security and data-integrity guardrails to backend changes?▼

You should apply security and data-integrity guardrails whenever backend or API changes touch brand flows, messaging, authentication, or payments to prevent unauthorized access and data corruption.

Related Skills

Explore More Software Engineering Skills→
m-salauddinm-salauddin

supabase-best-practices

Enforce Supabase security and performance best practices across RLS, Clerk, storage, and migrations.

Community
Advanced
harperaaharperaa
15

security-testing-verification

Automate security testing for CSRF protection, rate limiting, and input validation.

Community
Intermediate
telum-aitelum-ai
2

stripe-integration

Integrate Stripe for payment processing, subscriptions, and webhook events.

Official
Advanced
sitharaj88sitharaj88
1

gcp-cloud-armor

Generate Google Cloud Armor security policies with WAF rules and rate limiting.

Community
Advanced