# Legal Context

> Force the project's legal ground to be declared instead of assumed, and write it to LEGAL-CONTEXT.md. Use before drafting or reviewing any legal document, or when the user asks "do we need an NDA / ToS / privacy policy", "legal setup", "what jurisdiction". This is the legal department's core — the LEGAL-CONTEXT.md it produces is what legal-doc and legal-critic hold every document to. Templates and structure only; not legal advice.

- Skill: `le-19-stvn/legal-context` (Agent Skill)
- Install (CLI): `npx skillmds@latest add le-19-stvn/legal-context`
- Raw SKILL.md: https://api.skillmd.com/api/skills/le-19-stvn/legal-context/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: le-19-stvn (https://skillmd.com/u/le-19-stvn)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/le-19-stvn/legal-context

---


# Legal Context

Legal documents are wrong when they assume the wrong ground. Before drafting anything, produce a `LEGAL-CONTEXT.md` that states the project's actual legal situation — so every document is built on declared facts, not defaults.

Read `TASTE.md` and `CLAUDE.md` first for register and constraints. (Check for and open these with your Read/Glob tools, not shell commands — OS portability.)

## What LEGAL-CONTEXT.md must declare

Each line is a fact about the project, marked *confirmed* or *to verify with a lawyer*.

- **Jurisdiction(s)** — governing law and the countries where users/customers are (this drives GDPR/CCPA and consumer-law exposure).
- **Entity** — legal form and name (or "not yet incorporated"), which changes liability and signing.
- **What's being handled** — personal data collected, payments, user-generated content, minors, third-party processors. Each flags a document or clause.
- **Documents in scope** — which of NDA, ToS/CGU, privacy policy, legal notices/mentions légales, cookie notice this project actually needs, and which it doesn't.
- **Out of scope / needs a lawyer** — anything binding, high-stakes, or specialized (equity, employment, regulated sectors, litigation). Name it here so it's routed to a professional, not drafted here.

## Rules

- **Declare, don't assume.** No governing law or entity taken as default — write down the real one, or mark it *to verify*.
- **Scope down.** Only list documents the declared context actually requires. Unneeded legal boilerplate is its own kind of risk.
- **Route the hard stuff out.** If it's binding or specialized, its place here is a pointer to a lawyer, not a draft.

## Not legal advice

This records the project's context to structure informational templates. It is not legal advice and does not determine legal obligations — a qualified lawyer does.

## Output

Write `LEGAL-CONTEXT.md` at project root. Short and declarative — read at the start of every legal session and by `legal-critic` on every document. Link it from `CLAUDE.md`.

## Before calling it done

Jurisdiction and entity are stated (or explicitly *to verify*), the in-scope documents map to real data/activity, and the out-of-scope/needs-a-lawyer section exists. If a document is listed with no reason in the context, drop it.