customize
Guided customization of your legal clinic profile — change one thing without re-running the whole cold-start interview. Adjust clinic profile, jurisdiction, supervision style, practice-area templates, semester configuration, or output safeguards. Use when the user says "change my [thing]", "new semester", "add a practice area", "update my config", or "customize".
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.0w
- Forks
- 2.0k
01 前言 Front Matter
- name
- customize
- description
- Guided customization of your legal clinic profile — change one thing without re-running the whole cold-start interview. Adjust clinic profile, jurisdiction, supervision style, practice-area templates, semester configuration, or output safeguards. Use when the user says "change my [thing]", "new semester", "add a practice area", "update my config", or "customize".
- argument-hint
- [section name, or describe what you want to change]
03 SKILL.md 正文
/customize
When this runs
The user typed /legal-clinic:customize. They (usually the professor, sometimes
a student) want to change something in the clinic profile — a jurisdiction, a
supervision style, a practice-area template, a semester rollover — without
re-running the whole cold-start interview and without hand-editing YAML.
What to do
-
Read the config. Read
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md. If the plugin config does not exist or still contains[PLACEHOLDER]values, say:You haven't run setup yet. Run
/legal-clinic:cold-start-interviewfirst — customize is for adjusting a profile you already have. -
Show the customizable map. List what's in the profile, grouped, with a one-line summary of the current value:
- Clinic profile — clinic name, host school, faculty lead, active practice areas, case type limits
- Jurisdiction — primary state, courts, agencies, local rules path
- Supervision style — informal vs. formal review queue; if formal, who reviews what before it goes out
- Practice-area templates — which templates are active (immigration, housing, small business, family, expungement, etc.) and any local overrides
- Semester — current semester, active students, rollover rules, handoff memo format
- Output safeguards — plain-language standards for client-facing outputs, deadline warning rules, privilege labeling
- Seed documents — clinic handbook, jurisdiction rules, template letters, sample memos, form libraries
- Outputs — supervisor guide format, client letter templates, memo scaffolds
- Workflow — case directories, deadline tracker location, review queue channel
- Integrations — document storage / Slack / court e-filing status, fallbacks
-
Ask what they want to change.
What would you like to adjust? Pick a section, or describe the change in your own words.
-
Make the change. Show the current value, ask for the new value, explain what changes downstream, confirm, write it to the config.
Examples:
- Adding a new practice area: "
/client-intakewill route matters of this type through the new template./draft,/memo, and/client-letterwill use the practice-area prompts./research-startwill add the corresponding Westlaw search terms." - Supervision style informal → formal review queue: "
/supervisor-review-queuebecomes active — student output will land there for supervisor sign-off before it goes to the client." - New semester rollover: "I'll archive the prior semester's active
cases, carry forward matters you flag as continuing, and prompt the
incoming students through
/ramp."
- Adding a new practice area: "
-
Close.
Done. Your next output will reflect the change. Anything else? You can run
/legal-clinic:customizeanytime.
Guardrails
- Never delete a section. If the user wants to "drop" a practice area,
offer to mark it
[Archived]and explain that archiving keeps case history accessible but hides the template from/client-intakerouting. - Flag internal inconsistency. If the change would make the profile inconsistent (e.g., formal review queue on + informal supervision note; or practice area on + no jurisdiction rules configured), flag the tension.
- Flag guardrail degradation. These are load-bearing and should not be
removed: the "NOT final work product" framing on
/draft, plain-language standards on client-facing outputs, "does NOT decide case acceptance" on/client-intake, "NOT substantive advice" on/client-letter, and the scaffold-not-analysis framing on/memo. These exist because students ship work product — if the safeguards go, the risk of student work reaching a client without supervisor review goes up. Confirm the trade-off with the user, and if they're a student rather than the professor, suggest they discuss it with the supervisor first. - One change at a time. Don't re-ask the whole interview.
04 同仓库更多 Skills
reg-feed-watcher
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
policy-redraft
Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
policy-diff
Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.
matter-workspace
Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
gaps
Open gaps tracker — what's flagged and not yet closed. Use when the user asks "what gaps are open", "gap tracker", "remediation status", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.