sound-design-direction
Create comprehensive audio design including music cues, sound effects, Foley, and score direction
What this skill does
# Sound Design Direction Skill ## Purpose Design comprehensive audio landscapes that enhance storytelling. Sound is 50% of the film experience—music, effects, dialogue, and silence all shape emotion and meaning. ## Audio Categories ### The Sound Stack ``` DIALOGUE ├── Production dialogue ├── ADR (additional dialogue) ├── Voice-over └── Walla (crowd murmur) SOUND EFFECTS ├── Hard effects (impacts, doors) ├── Backgrounds (ambience) ├── Foley (character movement) └── Designed sounds (stylized) MUSIC ├── Score (composed) ├── Source (diegetic) └── Songs (licensed) ``` ## Sound Design Approach ### Design Philosophy | Approach | Description | Films | |----------|-------------|-------| | Naturalistic | Realistic, grounded | Drama, indie | | Hyperreal | Enhanced reality | Action, thriller | | Stylized | Artistic, expressive | Sci-fi, horror | | Minimal | Sparse, impactful | Art house | ### Diegetic vs. Non-Diegetic ``` DIEGETIC (source in story world): - Characters can hear it - Radio, TV, live music - Environmental sounds - Dialogue NON-DIEGETIC (outside story world): - Characters can't hear it - Score - Voice-over (sometimes) - Sound design elements ``` ## Music Spotting ### Music Cue Sheet Template ```markdown ## Music Cue [M##] ### Identification - **Scene:** [Number] - **Cue Name:** [Descriptive title] - **Timecode In:** [HH:MM:SS:FF] - **Timecode Out:** [HH:MM:SS:FF] - **Duration:** [MM:SS] ### Type - [ ] Score - [ ] Source music - [ ] Song/Licensed ### Direction - **Mood:** [Emotional direction] - **Tempo:** [BPM or feel] - **Instrumentation:** [Key instruments] - **Dynamic Arc:** [How it builds/changes] ### Sync Points - [Timecode]: [What happens musically] - [Timecode]: [What happens musically] ### Transitions - **In:** [How music enters] - **Out:** [How music exits] ### Reference - **Temp Track:** [If applicable] - **Similar To:** [Reference tracks] ### AI Music Prompt (Suno/Udio) [Prompt for AI generation] ``` ### When to Use Music **Start Music:** - Emotional shift - Scene transition - Building tension - Montage - Establishing mood **End Music:** - Before important dialogue - For impact through silence - Scene completion - Emotional peak hit ## Sound Effects Design ### Scene Sound Design Template ```markdown ## Scene [##] Sound Design ### Ambience/Backgrounds - **Primary Bed:** [Main environmental sound] - **Layers:** - [Additional ambient element] - [Additional ambient element] - **Intensity:** [1-10] ### Hard Effects | Timecode | Effect | Description | Priority | |----------|--------|-------------|----------| | 00:00:00 | [SFX] | [Details] | [Hi/Med/Lo] | ### Foley Requirements - **Footsteps:** [Surface type] - **Cloth:** [Material, intensity] - **Props:** [Items handled] ### Designed Sounds | Timecode | Sound | Description | Style | |----------|-------|-------------|-------| | 00:00:00 | [Name] | [What it is] | [Realistic/Stylized] | ### Silence - [Timecode]: [Purpose of silence] ### Special Treatment - [ ] Slow motion audio - [ ] POV/Subjective sound - [ ] Flashback treatment - [ ] Underwater/muffled ``` ## Emotional Sound Design ### Sound and Emotion | Emotion | Sound Approach | |---------|----------------| | Fear | Low frequency rumble, unexpected stingers | | Tension | High-pitched tone, silence, breath | | Joy | Bright, clear, musical | | Sadness | Sparse, echo, minor keys | | Anger | Hard impacts, distortion, chaos | | Love | Warmth, softness, intimacy | ### Signature Sounds Create recurring audio motifs: ``` Character themes (musical) Location sounds (environmental) Object sounds (associated with items) Emotional triggers (sound = feeling) ``` ## Score Direction ### Theme Development ```markdown ## Musical Themes ### Main Theme - **Association:** [Character/concept] - **Mood:** [Emotional quality] - **Instrumentation:** [Core instruments] - **Motif:** [Melodic description] - **Usage:** [When it appears] ### Secondary Themes [Same structure for each theme] ### Theme Transformations - [Context]: [How theme changes] - [Context]: [How theme changes] ``` ### Score Style Guide ```markdown ## Score Direction ### Overall Approach - **Genre:** [Orchestral, electronic, hybrid] - **Era Feel:** [Contemporary, classical, retro] - **Emotional Range:** [Intimate to epic] ### Instrumentation Palette - Primary: [Main instruments] - Secondary: [Supporting instruments] - Special: [Unique elements] ### References - [Film score reference 1] - [Film score reference 2] - [Non-film reference] ### Avoid - [What doesn't fit] ``` ## Mix Priorities ### Dialogue Intelligibility Dialogue is almost always priority: ``` Dialogue first Music ducks for important lines Effects support, don't compete ``` ### Dynamic Range ``` Quiet moments → space for intimacy Loud moments → impact through contrast Build gradually → sustain anticipation Sudden change → shock and surprise ``` ## Output Templates ### Music Cue Sheet Summary ```markdown | Cue | Scene | In | Out | Duration | Type | Notes | |-----|-------|-----|-----|----------|------|-------| | M1 | 1 | ... | ... | 0:45 | Score| Opening | ``` ### Sound Design Summary ```markdown | Scene | Ambience | Key SFX | Foley | Special | |-------|----------|---------|-------|---------| | 1 | City | Cars | Walk | None | ``` ## Quality Checklist - [ ] Every scene has ambience - [ ] Dialogue is prioritized - [ ] Music cues are spotted - [ ] Transitions are smooth - [ ] Silence is intentional - [ ] Emotional arc supported - [ ] Themes are consistent - [ ] Mix priorities clear
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.