Cookie Consent

What it does

Gates optional cookies and tracking behind clear, reversible consent, with regional behaviour handled correctly.

When to use it

Use for consent banners, analytics or advertising gating, or auditing tracking that fires before permission.

Problems it prevents

Stops analytics or ad scripts firing before a visitor has actually given permission.

Typical workflow

1. Inventory what actually needs consent
2. Build the gate before scripts load
3. Make withdrawal as easy as consent
4. Verify regional behaviour

Example output

A consent banner that provably blocks optional scripts until accepted, with a working withdrawal control.

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

• SystemLegal Compliance

  Identifies the approved legal pages, disclosures and third-party service notices a real site actually needs.

• SystemData Privacy Governance

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

• SystemLaunch Readiness

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