Delegate independent tasks to specialized agents working concurrently with isolated context.
Casebook Editing
Guidance for developing and editing legal casebooks
SKILL.md
Full skill instructions
Casebook Editing Skill
Domain: Legal casebook development and case editing Version: 1.0.0 Last Updated: 2025-12-15
Overview
This skill provides guidance for developing legal casebooks, including case selection, case editing, note writing, and problem design.
Casebook Structure
Standard Chapter Organization
Chapter X: [Topic]
├── A. Introduction
│ └── Overview of doctrinal area
├── B. Principal Cases
│ ├── Case 1 (edited)
│ │ └── Notes and Questions
│ ├── Case 2 (edited)
│ │ └── Notes and Questions
│ └── Case 3 (edited)
│ └── Notes and Questions
├── C. Problems
│ └── Hypotheticals for discussion
└── D. Supplementary Materials
├── Statutory excerpts
├── Secondary readings
└── Comparative perspectives
Case Selection Principles
Pedagogical Criteria
- Doctrinal clarity - Does case clearly illustrate the rule?
- Factual richness - Are facts interesting and discussable?
- Analytical depth - Does court's reasoning reward close reading?
- Historical significance - Is this a landmark or foundational case?
- Contemporary relevance - Does case connect to current issues?
Selection Balance
- Canonical cases - Students should know the "greatest hits"
- Recent cases - Show doctrine in action today
- Contrasting cases - Illustrate doctrinal tensions
- Problem cases - Hard cases that test the rule
- Diversity - Varied courts, parties, fact patterns
Sequencing Considerations
- Chronological - Show doctrinal evolution
- Simple to complex - Build analytical skills
- Rule to exceptions - Establish baseline, then complicate
- Majority to minority - Show spectrum of approaches
Case Editing Guidelines
What to Cut
- Procedural history - Keep only what's necessary
- Redundant facts - Streamline to essentials
- Lengthy quotations - From other cases unless critical
- Concurrences/dissents - Unless pedagogically valuable
- Boilerplate language - Standard of review, etc.
What to Preserve
- Key facts - Those on which outcome turns
- Holding - The rule of the case
- Core reasoning - Why court reached this conclusion
- Notable language - Quotable formulations
- Tensions - Internal or with other cases
Editing Conventions
Omissions:
[Material omitted]
...
* * *
Editorial insertions:
[The court here addresses...]
[Eds.: This case was later overruled in...]
Paragraph breaks:
- Preserve original paragraph structure where possible
- Add breaks for readability if needed
Length Guidelines
| Case Type | Target Length | Original Length |
|---|---|---|
| Principal case | 3-8 pages | 20-50 pages |
| Note case | 0.5-2 pages | Any |
| Problem case | 1-3 pages | Any |
Notes and Questions
Types of Notes
- Explanatory notes - Clarify doctrine or context
- Problem notes - Pose hypotheticals
- Citation notes - Point to related cases
- Policy notes - Raise broader implications
- Historical notes - Provide background
- Comparative notes - Contrast approaches
Effective Questions
Comprehension questions:
- What was the holding?
- What facts were dispositive?
- What rule did the court apply?
Analytical questions:
- How does this case relate to [prior case]?
- Is the court's reasoning persuasive? Why?
- What would change the outcome?
Application questions:
- How would this court decide [hypothetical]?
- Does this rule make sense in [context]?
Policy questions:
- What values does this rule serve?
- Who wins and loses under this approach?
- Is there a better rule?
Question Sequencing
- Start with comprehension (ensure understanding)
- Move to analysis (develop skills)
- Build to synthesis (connect to bigger picture)
- End with application (test mastery)
Problem Design
Effective Problems
Characteristics:
- Clearly framed facts
- Specific legal question
- Not obviously one-sided
- Connects to assigned reading
- Admits multiple reasonable analyses
Structure:
[Factual scenario - 1-3 paragraphs]
Questions:
1. [Specific legal question]
2. [Follow-up or complication]
3. [Policy or broader implication]
Problem Types
- Straightforward application - Test basic rule
- Close case - Facts near the line
- Novel facts - Test rule's boundaries
- Multi-issue - Integrate several concepts
- Counseling - What should client do?
- Drafting - Write clause, statute, etc.
Supplementary Materials
When to Include
- Statutes governing the area
- Regulations if relevant
- Model codes or Restatements
- Key secondary sources (excerpted)
- Empirical data if illuminating
- Comparative/international perspectives
Editing Secondary Sources
- More aggressive editing acceptable
- Focus on thesis and key arguments
- Cut methodological details
- Preserve voice and style
Available Workflows
workflows/case-selection.md- Choose cases for chapterworkflows/case-editing.md- Edit a case for inclusionworkflows/notes-questions.md- Draft notes and questions
Quality Checklist
For Case Edits
- Key facts preserved
- Holding clear
- Reasoning follows
- Appropriate length
- Omissions marked
- Readable flow
For Notes and Questions
- Build on case reading
- Progress in difficulty
- Mix question types
- Answerable from materials
- Engage, don't overwhelm
For Chapter Overall
- Coherent arc
- Balanced coverage
- Appropriate difficulty
- Sufficient variety
- Clear learning objectives
Casebooks teach legal reasoning through carefully curated materials.
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
