agentleFS
Falcon305Falcon305/vibe-starter/.claude/skills/vibe-legal/SKILL.md

vibe-legal

Skill1 starsChanged 5 months agoMITView on GitHub

Generate or update a vibe-starter app's legal pages (privacy, terms, cookies) from its config and installed modules. Use when data practices change, a module is added or removed, the business details change, or the user runs /vibe-legal.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Keep the privacy policy, terms, and cookie policy accurate.

    line 8
  2. Very specific:

    Read .vibe/installed.json.

    line 37
  3. Very specific:

    Start the app and read /privacy, /terms, and /cookies.

    line 49
  4. Distinctive:

    Never overstate or understate what data is collected.

    line 64
  5. Distinctive:

    Never edit generated files directly.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

vibe-legal

Keep the privacy policy, terms, and cookie policy accurate. The pages render from lib/legal/config.ts plus generated contributions from installed modules, so this skill's job is to make the facts in that config true and confirm the output reflects reality.

When to use

  • The user set up or changed their business details.
  • A module was installed or removed (new subprocessor, new cookie, new data collected).
  • The user asks to review or regenerate legal pages.

Workflow

1. Gather the facts

Determine, by asking or by reading the app:

  • Legal entity name, operating name, privacy contact email, postal address.
  • Jurisdiction: eu, us, or global (which visitors, which laws apply).
  • Whether the app sells or shares personal data for value.
  • What personal data the app actually collects (from forms, accounts, uploads, analytics).
  • Governing law and effective date.

2. Update the config

Edit lib/legal/config.ts with those facts. Do not edit the generated files by hand — the installer owns lib/legal/modules.generated.ts (subprocessors, cookies, data from modules).

3. Reconcile with installed modules

Read .vibe/installed.json. Confirm every installed module's subprocessors and cookies appear on the cookie page and in the privacy policy. If they are missing or stale, re-run the installer's regeneration:

pnpm vibe add <an-installed-module>

Adding an already-installed module is a no-op that still regenerates the legal contributions.

4. Review the rendered pages

Start the app and read /privacy, /terms, and /cookies. Confirm:

  • Jurisdiction is right: GDPR section present for EU/global, CCPA for US/global.
  • The subprocessor list matches what the app actually uses.
  • The cookie table matches the cookies actually set.
  • The "Do Not Sell or Share" control appears only if sellsData is true or jurisdiction includes the US.

5. Report

Summarize what changed and remind the user: this is a strong, honest baseline, not legal advice. Recommend a lawyer review before relying on it for a real business.

Rules

  • Never overstate or understate what data is collected. Accuracy protects the user legally.
  • Never edit generated files directly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.