shot-composition
Plan camera angles, movements, shot sizes, and visual design for cinematic storytelling
What this skill does
# Shot Composition Skill
## Purpose
Design visually compelling shots that serve the story. Every camera choice—angle, movement, lens, composition—should enhance meaning, create emotion, and guide the viewer's attention.
## Shot Sizes
### The Size Spectrum
```
EWS ─── WS ─── MWS ─── MS ─── MCU ─── CU ─── ECU
│ │ │ │ │ │ │
│ │ │ │ │ │ └── Detail/Eyes
│ │ │ │ │ └──────── Face
│ │ │ │ └──────────────── Head/Shoulders
│ │ │ └──────────────────────── Waist Up
│ │ └──────────────────────────────── Knees Up
│ └──────────────────────────────────────── Full Body
└──────────────────────────────────────────────── Environment
```
### When to Use Each
| Size | Use For | Emotion |
|------|---------|---------|
| EWS | Establishing, scope, isolation | Awe, loneliness |
| WS | Context, geography, action | Objective, neutral |
| MWS | Blocking, movement | Balance |
| MS | Conversation, action | Engagement |
| MCU | Emotion, dialogue | Connection |
| CU | Reaction, intimacy | Intensity |
| ECU | Detail, revelation | Impact |
## Camera Angles
### Vertical Angles
```
Bird's Eye → Looking straight down (god view)
High Angle → Looking down at subject (vulnerability)
Eye Level → Neutral, natural (equality)
Low Angle → Looking up at subject (power)
Worm's Eye → Looking straight up (extreme power)
```
### Horizontal Angles
```
Frontal → Direct, confrontational
3/4 Profile → Most common, dimensional
Profile → Reflective, contemplative
Over Shoulder → POV, conversation
Dutch Angle → Unease, disorientation
```
## Camera Movement
### Movement Types
| Movement | Description | Effect |
|----------|-------------|--------|
| Static | No movement | Stability, observation |
| Pan | Horizontal pivot | Survey, follow |
| Tilt | Vertical pivot | Reveal, scale |
| Dolly | Camera moves forward/back | Intimacy, revelation |
| Track | Camera moves alongside | Follow, accompany |
| Crane | Camera moves up/down | Scope, grandeur |
| Steadicam | Smooth handheld | Immersion |
| Handheld | Naturalistic shake | Urgency, documentary |
| Zoom | Lens change (not movement) | Emphasis, isolation |
### Motivated Movement
Movement should be motivated by:
- Character movement (following action)
- Emotional revelation (moving in for intimacy)
- Story information (revealing new element)
- Point of view (showing what character sees)
## Composition Principles
### Rule of Thirds
```
┌───┬───┬───┐
│ • │ │ • │ Place subjects at intersections
├───┼───┼───┤ for dynamic composition
│ │ ○ │ │
├───┼───┼───┤ Center for stability/confrontation
│ • │ │ • │
└───┴───┴───┘
```
### Leading Lines
```
Lines that guide the eye:
- Roads, hallways, fences
- Arms, gaze direction
- Light beams, shadows
- Architectural elements
```
### Frame Within Frame
```
Use doorways, windows, mirrors
to create visual interest and
focus attention on subject
```
### Depth
```
Foreground │ Midground │ Background
↓ ↓ ↓
Frame Subject Context
```
## Lens Choices
### Focal Length Effects
| Lens | Effect | Use |
|------|--------|-----|
| Wide (14-35mm) | Distortion, space | Environments, unease |
| Normal (35-50mm) | Natural | Dialogue, general |
| Telephoto (85mm+) | Compression, isolation | Portraits, tension |
### Depth of Field
```
Shallow DOF (f/1.4-2.8):
- Subject sharp, background blur
- Isolation, intimacy
- Focus pull for attention
Deep DOF (f/8-16):
- Everything in focus
- Context, geography
- Multiple planes of action
```
## Shot List Format
```markdown
## Scene [Number] Shot List
| Shot | Size | Angle | Lens | Movement | Subject | Action | Duration |
|------|------|-------|------|----------|---------|--------|----------|
| 1.1 | WS | Eye | 35mm | Static | Room | Est. | 3s |
| 1.2 | MS | 3/4 | 50mm | Track | Sarah | Enter | 5s |
| 1.3 | CU | Eye | 85mm | Static | Sarah | React | 2s |
```
## Visual Storytelling
### Show Power Dynamics
```
DOMINANT: Low angle, higher position, larger frame
SUBMISSIVE: High angle, lower position, smaller frame
EQUAL: Eye level, similar frame sizes
```
### Create Tension
```
- Tight framing (claustrophobic)
- Negative space (anticipation)
- Off-center subjects (unease)
- Shallow DOF (isolation)
```
### Guide Emotion
```
JOY: Bright, warm, open framing
FEAR: Dark, tight, unpredictable
LOVE: Soft, close, warm tones
ANGER: Hard, dynamic, extreme angles
```
## Coverage Strategy
### Basic Scene Coverage
1. **Master** - Full scene in one shot
2. **Singles** - Individual close-ups
3. **Over-shoulders** - Conversation coverage
4. **Inserts** - Detail shots
5. **Cutaways** - Reaction, environment
### Action Coverage
1. **Wide master** - Geography
2. **Medium action** - Key moments
3. **Close details** - Impact
4. **Reaction** - Emotional response
## Shot Breakdown Template
```markdown
## Shot [ID]
### Technical
- **Size:** [EWS/WS/MS/MCU/CU/ECU]
- **Angle:** [Eye/Low/High/Dutch]
- **Lens:** [Focal length]
- **Movement:** [Type and direction]
- **Duration:** [Seconds]
### Composition
- **Subject Placement:** [Thirds/Center]
- **Depth:** [FG/MG/BG elements]
- **Leading Lines:** [If any]
### Purpose
- **Story Function:** [What it communicates]
- **Emotional Intent:** [What viewer should feel]
### AI Video Prompt
[Optimized prompt for generation]
```
## Quality Checklist
- [ ] Shot size serves scene purpose
- [ ] Angle reinforces power/emotion
- [ ] Movement is motivated
- [ ] Composition guides eye
- [ ] Coverage is complete
- [ ] Continuity maintained
- [ ] Screen direction consistent
- [ ] Each shot earns its place
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.