What problem does it solve? Handling payment card data exposes applications to strict PCI DSS obligations, and mistakes like storing CVV codes or transmitting unencrypted card numbers lead to failed audits and security breaches. This Skill provides concrete implementation patterns for meeting the 12 PCI DSS requirements in payment systems. ## Core Features & Use Cases - Data Minimization & Sanitization: Enforce rules on prohibited data (CVV, PIN, track data), mask PANs in logs, and validate that no forbidden fields are stored. - Tokenization & Encryption: Implement Stripe token-based payments, custom token vaults, AES-256-GCM encryption at rest, and TLS enforcement in transit. - Access Control & Audit Logging: Apply role-based access decorators for cardholder data and generate PCI-compliant audit trails for access and authentication events. - Use Case: When building a checkout flow, use this Skill to ensure card details never touch your server, payment methods are stored only as processor tokens, and every access to cardholder data is logged for your next PCI assessment. ## Quick Start Use the pci-compliance skill to review my payment processing code and implement tokenization, encryption, and audit logging that satisfy PCI DSS requirements.