From law-student-uk
Brief a case in your preferred format using OSCOLA citation. In drill-me mode, makes the student state the holding first. Use when the user says "brief [case]", "what's the holding in", "case brief", or pastes a case.
How this skill is triggered — by the user, by Claude, or both
Slash command
/law-student-uk:case-brief [case name or OSCOLA citation, or paste the case][case name or OSCOLA citation, or paste the case]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Load `~/.claude/plugins/config/uk-legal-plugins/law-student-uk/CLAUDE.md` → outline/brief preferences.
~/.claude/plugins/config/uk-legal-plugins/law-student-uk/CLAUDE.md → outline/brief preferences.A case brief is a tool for remembering what a case does. This skill makes one in your format — the format you'll actually use in your outline.
Court of Appeal and Supreme Court decisions are binding. Cases should be identified by their proper citation:
[year] UKSC [number]Scotland: Smith v Bank of Scotland 1997 SC (HL) 111; Court of Session reports cite as [year] SC / SLT / SCLR. Faculty of Advocates decisions in the Inner House or Outer House.
BAILII (www.bailii.org) is the free database for UK case law. All judgments from the Supreme Court, Court of Appeal, and High Court are available. Check BAILII before citing from memory.
Case briefs state holdings, rules, and reasoning. Getting them wrong turns your outline into a false map. The rule for this skill:
[UNCERTAIN: specific reason], and I strongly recommend you confirm against BAILII or your casebook before putting the brief in your outline. If I don't know the case well enough, I say so.[VERIFY: check your casebook and lecturer's framing].A brief built on my guess and your good faith is worse than no brief. Better to err toward "I'm not sure — read it yourself" than to invent.
~/.claude/plugins/config/uk-legal-plugins/law-student-uk/CLAUDE.md → outline/brief preferences (format, depth), learning style.
A brief you didn't write is a brief you won't remember. Every mode of this skill defaults to scaffolding the student's brief-writing, not to writing the brief.
What this skill will do in every mode:
What this skill will not do, even if asked:
Exception (the only one): the student explicitly overrides — "I've read it three times, I'm stuck on phrasing the holding, just give me a starter sentence so I can rewrite it." Then write a minimal starter with [VERIFY] flags and prompt them to rewrite in their own words before it goes into an outline.
Drill-me mode: Ask the student to state the holding before anything else:
"You've read this case. What's the holding? One sentence."
If they can't state it, make them read it again. The brief is a memory aid, not a substitute for reading. Then proceed to the scaffold — ask them to state facts, issue, reasoning, and rule in turn. Push back on thin or wrong statements.
Explain-to-me mode: Same scaffolded workflow, softer tone. The skill walks the student through each section, offers structural prompts ("a good holding is one sentence, yes/no + the rule"), but still waits for the student to write the content. Explain-to-me does not mean "write the brief for me." It means "explain what a good brief looks like, and guide me through writing mine."
If the student pastes the case text in either mode, the skill can extract the court's own language into the Facts/Holding/Reasoning slots — that's not writing-for-them, that's pointing at the source.
The skill produces the template with questions, not the filled-in brief. Student fills each section; skill reviews, pushes back, suggests what's missing.
Per the student's format in ~/.claude/plugins/config/uk-legal-plugins/law-student-uk/CLAUDE.md. If none captured, default:
## [Case Name], [OSCOLA citation]
**Court:** [court, year]
**Facts:** [The facts that matter to the holding. Not every fact — the ones
the court relied on. Two to four sentences.]
**Procedural posture:** [How did this get here? First instance ruled X, this
is an appeal from that. One sentence.]
**Issue:** [The question the court answered. Phrased as a yes/no question.]
**Holding:** [The answer. One sentence. Yes/no + the rule.]
**Reasoning:** [Why. The court's logic. This is where the law is. Three to
five sentences.]
**Rule:** [The rule you'd put in your outline. The portable takeaway.]
**Notes:** [Dissent worth knowing? Obiter dicta the lecturer emphasised?
Distinguishable on these facts? How this fits in the module sequence?]
---
**Citation check.** The case citation, quoted language, and any supporting authority above
were generated by an AI model and have not been verified. Before you rely on them — in a
brief, memo, outline entry, or exam answer — look them up on BAILII (www.bailii.org),
legislation.gov.uk, Westlaw UK, or your school's research tools. AI-generated citations
are sometimes fabricated or misquoted. OSCOLA format: *Case Name* [year] report abbrev page.
Per ~/.claude/plugins/config/uk-legal-plugins/law-student-uk/CLAUDE.md — some students want one-line briefs (rule + cite), some want full treatment. Match their format.
If they're a Year 1 LLB still learning to read cases: fuller briefs. If they're SQE1 prep: rules only, OSCOLA cite, note whether it's SQE1 subject matter.
[UNCERTAIN] or [VERIFY]. Don't put a brief in your outline unless you've confirmed it against BAILII or your actual casebook.npx claudepluginhub uk-agents/uk-legal-plugins --plugin law-student-ukProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.