case-justification
Draft case justification sections for interview-based sociology articles. Guides cluster selection, component coverage, and calibration based on analysis of 32 Social Problems/Social Forces articles.
What this skill does
# Case Justification Writer
You help sociologists write **case justification sections** (also called "Case Background," "Research Setting," or "The [Site Name] Context") for interview-based journal articles. Your guidance is grounded in systematic analysis of 32 articles from *Social Problems* and *Social Forces*.
## When to Use This Skill
Use this skill when users want to:
- Draft a new case justification section from scratch
- Restructure an existing section that's too long, too short, or poorly matched to the study type
- Determine the appropriate level of contextualization for their case
- Ensure the section matches genre conventions for interview-based research
- Position the case section correctly relative to the theory section
This skill assumes users have selected their research site and can describe its key features. The case justification section contextualizes the empirical setting for readers.
## Connection to Other Skills
| Skill | Purpose | Key Output |
|-------|---------|------------|
| **interview-analyst** | Analyze qualitative data | Coding structure, findings |
| **interview-writeup** | Write findings sections | Draft findings |
| **methods-writer** | Write methods sections | Draft methods |
| **case-justification** | Write case/setting context | Draft case justification |
| **interview-bookends** | Write intros/conclusions | Draft bookends |
This skill handles the case background that typically appears between the theory section and methods section.
## Core Principles (from Genre Analysis)
Based on systematic analysis of 32 case justification sections:
### 1. Position Determines Function
- **88% position AFTER theory** - the case illustrates or tests theoretical claims
- **12% position BEFORE theory** (Policy-Driven only) - the case motivates the theoretical framework
- Position is not a stylistic choice; it signals the relationship between case and theory
### 2. Phenomenon-Site-Link Openings Dominate (50%)
Half of all case justification sections open by connecting the phenomenon to the site:
> "With the formalization of a labor-export policy in the mid-1970s, the Indonesian government entered the labor brokerage industry."
Other openings: Geographic-Introduction (19%), Institutional-Description (16%), Research-Setting (9%), Historical-Periodization (6%)
### 3. Single Subsection Is the Norm (75%)
Most case justification sections use exactly one subsection heading. Multiple subsections signal Deep Historical (episodes) or Comparative (sites) clusters.
### 4. Implicit Transitions Dominate (66%)
Two-thirds of sections end without explicit transition language. The structural break to Methods carries readers forward. Explicit transitions are rare except in Comparative sections with integrated methods content.
### 5. Tables Signal Comparative Treatment
71% of Comparative sections include tables; all other clusters rarely or never use tables. If you have a table, you probably have a Comparative section.
## Key Statistics (Benchmarks)
### Corpus Overview
| Metric | Value |
|--------|-------|
| Total articles | 32 |
| Median word count | 765 |
| Range | 264-3,210 |
| Single subsection | 75% |
| Position after theory | 88% |
### Cluster Distribution
| Cluster | N | % | Word Target |
|---------|---|---|-------------|
| Standard Context | 11 | 34% | 700-1,000 |
| Comparative | 7 | 22% | 1,000-1,500 |
| Minimal Context | 5 | 16% | 300-500 |
| Deep Historical | 5 | 16% | 1,500-2,500 |
| Policy-Driven | 4 | 13% | 650-900 |
### Opening Move Distribution
| Opening Type | Prevalence |
|--------------|------------|
| Phenomenon-Site-Link | 50% |
| Geographic-Introduction | 19% |
| Institutional-Description | 16% |
| Research-Setting | 9% |
| Historical-Periodization | 6% |
### Justification Strategy Distribution
| Strategy | Prevalence |
|----------|------------|
| Intrinsic-Interest | 38% |
| Theoretical-Fit | 22% |
| Empirical-Extremity | 16% |
| Variation-Leverage | 16% |
| Access-Driven | 9% |
## The Five Clusters
Case justification sections cluster into five recognizable styles:
| Cluster | Target Words | Prevalence | Key Feature | When to Use |
|---------|--------------|------------|-------------|-------------|
| **Minimal** | 300-500 | 16% | Brief, efficient | Well-known site, mixed-methods |
| **Standard** | 700-1,000 | 34% | Balanced context | DEFAULT for single-site studies |
| **Deep Historical** | 1,500-2,500 | 16% | Chronological narrative | Movement studies, periodization |
| **Comparative** | 1,000-1,500 | 22% | Parallel sites, tables | Multi-site comparisons |
| **Policy-Driven** | 650-900 | 13% | BEFORE theory | Policy IS the phenomenon |
**Default**: Standard Context. Choose other clusters only when specific triggers apply.
See `clusters/` directory for detailed profiles with benchmarks, signature moves, and templates.
## Workflow Phases
### Phase 0: Assessment
**Goal**: Gather study information and select the appropriate cluster.
**Process**:
- Collect case details (site, population, context, justification)
- Apply decision tree to identify cluster
- Confirm cluster selection with user
- Note any special considerations
**Guide**: `phases/phase0-assessment.md`
> **Pause**: User confirms cluster selection before drafting.
---
### Phase 1: Drafting
**Goal**: Write the complete case justification section following cluster template.
**Process**:
- Follow cluster-specific structure and word allocation
- Include required components for the cluster
- Use appropriate rhetorical patterns from corpus
- Position correctly (before or after theory)
**Guides**:
- `phases/phase1-drafting.md` (main workflow)
- `clusters/` (cluster-specific templates)
- `techniques/opening-moves.md` (how to start)
- `techniques/justification-strategies.md` (how to justify)
- `techniques/transitions.md` (how to end)
**Output**: Complete case justification section draft.
> **Pause**: User reviews draft.
---
### Phase 2: Revision
**Goal**: Calibrate against benchmarks and polish.
**Process**:
- Verify word count against cluster target
- Check required components are present
- Assess transition type
- Polish prose
- Final quality check
**Guide**: `phases/phase2-revision.md`
**Output**: Revised case justification section with quality memo.
---
## Cluster Decision Tree
To identify which cluster fits your study:
```
START
|
v
[Does your case context need to PRECEDE your theoretical framework?]
(Is the policy/institutional context itself the phenomenon you will theorize about?)
|
+-- YES --> POLICY-DRIVEN CLUSTER
| Position: BEFORE theory
| Target: 650-900 words
|
+-- NO (or unsure) --> Continue
|
v
[Do you have MULTIPLE RESEARCH SITES that you will compare?]
(Two or more locations, organizations, or cases studied in parallel?)
|
+-- YES --> COMPARATIVE CLUSTER
| Parallel structure, tables
| Target: 1,000-1,500 words
|
+-- NO (single site) --> Continue
|
v
[Is HISTORICAL DEVELOPMENT central to your case?]
(Must you trace multiple episodes, periods, or phases?)
|
+-- YES --> DEEP HISTORICAL CLUSTER
| Chronological organization
| Target: 1,500-2,500 words
|
+-- NO --> Continue
|
v
[Is your case WELL-KNOWN and requires MINIMAL introduction?]
(Famous site, mixed-methods design, phenomenon over site, space constraints?)
|
+-- YES --> MINIMAL CONTEXT CLUSTER
| Brief, efficient
| Target: 300-500 words
|
+-- NO --> STANDARD CONTEXT CLUSTER (DEFAULT)
Balanced single-site context
Target: 700-1,000 words
```
## Cluster Profiles
Reference these guides for cluster-specific writing:
| Guide | Cluster | Triggers |
|Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.