Find agent skills by outcome

- Regulations: DSA (Digital Services Act)

local speech/content laws

- Key Clauses: Cookie table

consent banner specification

- Scope: Acceptable behavior

prohibited conduct

- Dependencies: Privacy Policy for legal bases

analytics/ad platform documentation

- Scope: Cookie inventory

- Regulations: ePrivacy Directive

GDPR cookie requirements

- Regulations: GDPR

CCPA/CPRA

- Key Clauses: Cross-border transfers

sub-processors

- Key Clauses: Arbitration

limitation of liability

- Scope: User eligibility

rights

- Dependencies: References to Privacy Policy

Cookie Policy

Coding & Debugging

Write all proposed legal documents and any code snippets to `TODO_legal-document-generator.md` only. Do not create any other files. If specific files should be created or edited

include patch-style diffs or clearly labeled file blocks inside the TODO.

Use checkboxes and stable IDs (e.g.

`LEGAL-PLAN-1.1`):

In `TODO_legal-document-generator.md`

include:

- Refund Policy contradicts ToS: If ToS says non-refundable but Refund Policy allows refunds

the inconsistency creates legal exposure

- Ignoring minors: If the service could be used by under-18 users

failing to address COPPA/age-gating is a serious gap

- Provide machine-readable policy endpoints (e.g.

`.well-known/privacy-policy`)

- Include in-app policy viewer (WebView pointing to `/privacy`

`/terms`

- Host policy pages on the web at their dedicated URLs (`/terms`

`/privacy`

- Implement cookie consent banner with granular opt-in/opt-out controls

linking to `/cookies` and `/privacy`

- For Next.js/Nuxt: use file-based routing (e.g.

`app/privacy/page.tsx` or `pages/privacy.vue`)

- Create dedicated route/page for each policy document (`/terms`

`/privacy`

- Track regulatory updates (GDPR amendments

new state privacy laws)

- Use semantic versioning (e.g.

v1.0