Security

What it does

Applies the evidence-based production security gate across secrets, auth, data access, uploads, dependencies and APIs.

When to use it

Use for any feature handling data or privileged actions, and as the mandatory gate before every launch.

Problems it prevents

Stops common but preventable exposure (leaked secrets, missing auth checks, unvalidated input) from reaching production.

Typical workflow

1. Review secret and environment handling
2. Check role and access boundaries
3. Audit input and API handling
4. Report evidence, not assumptions

Example output

A security review report with concrete evidence per check (pass, fail, or not applicable) never a blanket 'looks fine'.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• SystemLaunch Readiness

  Classifies and verifies what customers, search engines and operators actually need before a production launch.

• SystemData Privacy Governance

  Builds practical data-privacy governance: data inventories, retention, access requests, vendor data flows.

• FocusedFile Upload & Dropzone

  Implements secure, resilient file-upload flows: validation, malware scanning, resumable transfer, failure recovery.