customize
Guided customization of your law-student study profile — change one thing without re-running the whole cold-start interview. Adjust current classes, learning style, outline preferences, bar prep subjects, seed materials, or study session cadence. Use when the user says "change my [thing]", "add a class", "update my profile", "new semester", 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 law-student study profile — change one thing without re-running the whole cold-start interview. Adjust current classes, learning style, outline preferences, bar prep subjects, seed materials, or study session cadence. Use when the user says "change my [thing]", "add a class", "update my profile", "new semester", or "customize".
- argument-hint
- [section name, or describe what you want to change]
03 SKILL.md 正文
/customize
When this runs
The user typed /law-student:customize. They want to change something in
their study profile — a class, a learning style preference, a bar prep
subject — 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/law-student/CLAUDE.md. If the plugin config does not exist or still contains[PLACEHOLDER]values, say:You haven't run setup yet. Run
/law-student: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:
- Student profile — name, school, year (1L/2L/3L/LLM), jurisdiction for bar, enrolled clinics or journals
- Current classes — class name, professor, syllabus path, exam format (closed/open book, essay/MBE/mixed), cold-call style
- Learning style — Socratic vs. summary, how much pushback you want, whether the plugin rewrites your work or only critiques structurally
- Outline preferences — outline format (IRAC/CREAC/case-briefing style), level of rule detail, whether to include policy discussion, saved outline templates
- Bar prep — which exam (UBE/state), subjects in rotation, weak- subject flagging, MBE vs. essay cadence
- Seed materials — casebook paths, prior outlines, graded essays, old exams, MBE sets, syllabi, papers
- Study workflow — session length, flashcard Leitner bucket schedule, exam forecast cadence, cold-call prep timing
- Integrations — document storage / flashcard app (if any) 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 class: "
/outline-builderwill scaffold a new outline for this class./flashcardswill add a new subject bucket./cold-call-prepwill ask for a seat and a topic when you invoke it for this class." - Learning style Socratic → summary-first: "
/socratic-drillwon't ask you to answer first — it'll present the rule and example, then quiz you on application." - Adding a bar subject: "
/bar-prep-questionswill include this subject in rotation and weight it higher if you mark it weak."
- Adding a new class: "
-
Close.
Done. Your next output will reflect the change. Anything else? You can run
/law-student:customizeanytime.
Guardrails
- Never delete a section. If the user wants to "drop" a class, offer to
mark it
[Archived — retain seed materials]and explain what flashcard and outline behavior changes. - Flag internal inconsistency. If the change would make the profile inconsistent (e.g., "summary-first" learning style + "maximum pushback" Socratic setting), flag the tension.
- Flag guardrail degradation. The "no rewriting your writing" rule on
/legal-writingand/irac-practiceis load-bearing — the value of the skill is structural feedback, not ghost-writing. If the user asks to turn that off, confirm they understand that the plugin will not write their work for them. - 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.