4d55f53962
Cleanup pass following the CoCounsel merge (#4) and Lexis removal (#5): - Normalize whitespace and JSON indentation across plugin metadata files - Sync marketplace.json with plugin.json (ip-legal description, Courtroom5 title field) - Add missing ai-inventory and invention-intake rows to README skill reference - Replace stale short-form skill names in customize/cold-start SKILL.md prose with canonical directory names across 11 plugins (same bug class as the /setup -> /cold-start-interview QA fix) - Fix FYY -> FYI typo and a phantom WebFetch claim in launch-radar docs - Address review findings: line-wrapped /check-claims, /renewals-due -> /renewal-tracker, stale /setup in references/, agent.yaml comment contradiction, redundant 'intake intake' - Add root CLAUDE.md with validation conventions (claude plugin validate, I1-I11 invariants, frontmatter requirements) and a marketplace.json description + $schema No behavioral changes. claude plugin validate passes clean.
1.4 KiB
Company Profile
Shared by all Claude for Legal plugins. The first plugin you set up writes this; the rest read it.
Edit directly or re-run any plugin's /cold-start-interview to update.
Practice setting: [Solo/small firm | Midsize/large firm | In-house | Government/legal aid/clinic] Name: [Company or firm name] Industry: [What the company does / the firm's primary practice areas] What we sell / deliver: [Products, services, who to — or "N/A, law firm"] Size: [Employee count / lawyers / relevant headcount]
Geographic and regulatory footprint
Jurisdictions we operate in: [e.g., US (CA, NY, TX), UK, EU (DE, FR), AU, SG] Primary jurisdiction: [Where the bulk of work happens] Regulators we're subject to: [SEC, FTC, ICO, EDPB, ASIC, OAIC, etc. — only what applies] Open regulatory matters: [or none]
Risk posture
Overall risk appetite: [Conservative / middle / aggressive] What keeps us up at night: [The thing that would be a very bad day] The question leadership always asks: [or not known yet]
Key people
GC / Head of Legal: [Name] Escalation chain: [Name → Name → Name, or "set per plugin"]
Per-plugin practice profiles (playbooks, review frameworks, house style, matter workspaces) live alongside this file in each plugin's folder. This file holds the facts that are true regardless of which plugin you're using.