alpha nerd
27fbe1f313
Port claude-for-legal plugin collection to Opencode skills format. Changes: - 140 skills ported to opencode-for-legal/skills/ (namespaced naming) - 14 agents converted to Opencode subagent format - 5 managed-agent cookbooks flattened to single agents - 19 MCP servers converted to opencode.json format - 11 practice-profile templates ported (CLAUDE.md → PROFILE.md) - Remote skill catalog (index.json) for Opencode URL discovery - Setup wizard skill for first-time configuration License compliance: - Original source preserved in upstream/ per Apache 2.0 §4(b) - NOTICE.md documents derivative work and upstream attribution - LICENSE copied into port directory - README rewritten with port disclaimer and trademark notice Platform updates: - Removed all Claude Code/Cowork product-specific references - Config paths updated to ~/.config/opencode/opencode-for-legal/ - Command syntax: /plugin:skill → opencode auto-loading - Agent frontmatter converted (tools: → mode: subagent)
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.