Heet-P
- 3 skills
- 0 followers
- 17 hours ago last updated
- ▌ Legal Check · heet-p bundleFull-stack legal, privacy, and compliance audit engine for web applications and SaaS platforms. Use this skill when the user wants to audit a codebase for legal exposure, privacy risks, GDPR/CCPA compliance gaps, missing consent flows, unsafe data practices, cookie policy issues, payment/auth compliance, AI disclosure requirements, or platform liability risks. Trigger whenever the user says "audit my app for compliance", "check my codebase for privacy issues", "do a legal check", "GDPR audit", "privacy policy review", "terms of service check", "is my app compliant", or uploads/shares a codebase and asks about legal or privacy concerns. Also trigger proactively when reviewing any app that handles user accounts, payments, AI outputs, or file uploads — even if the user doesn't use the word "legal".
- ▌ Security Audit · heet-p bundleDeep adversarial security audit engine for full-stack web applications. Use this skill when the user wants to audit a codebase for security vulnerabilities, broken access control, injection risks, authentication weaknesses, payment security, file upload exploits, IDOR, CSRF, SSRF, RLS bypass, business logic abuse, rate limiting gaps, or deployment security issues. Trigger whenever the user says "audit my security", "find vulnerabilities", "pen test my app", "is this secure", "check for IDOR", "harden my auth", "review my payment flow for exploits", "can someone bypass this", "what can an attacker do", or shares code and asks about security, exploits, or hardening. Also trigger proactively when reviewing any app that handles auth, payments, file uploads, admin routes, or user-generated content — even if the user doesn't use the word "security".
- ▌ Scalability Architecture · heet-p bundleFull-stack scalability, architecture, and high-scale engineering audit engine for web applications. Use this skill when the user wants to audit a codebase for scalability bottlenecks, architecture quality, production readiness, infrastructure maturity, performance issues, database design, caching strategy, deployment design, or reliability gaps. Trigger whenever the user says "audit my architecture", "how do I scale this", "will this handle X users", "is my app production-ready", "what's the bottleneck", "how should I redesign this", "review my system design", "make this scalable", "can this handle traffic", or shares a codebase and asks about performance, infrastructure, or growth. Also trigger proactively when reviewing any app with a database, auth, payments, real-time features, or file uploads where scalability tradeoffs are implicitly at stake — even if the user doesn't say "architecture".