track-sequencing
Design optimal track order and album flow including opener/closer strategy, energy curves, transitions, and pacing for cohesive listening experiences
What this skill does
# Track Sequencing Design optimal track order and album flow for cohesive listening experiences. ## Overview This skill provides frameworks for sequencing tracks to create compelling album journeys. It covers opener/closer strategy, energy curve design, transition planning, pacing psychology, and format considerations. ## Capabilities ### Opener Strategy - Create immediate impact - Set album tone and expectations - Hook listener attention - Establish sonic palette - Introduce key themes ### Closer Strategy - Provide satisfying resolution - Create lasting impression - Resolve thematic elements - Leave emotional resonance - Consider reprise/callback ### Energy Curve Design - Map intensity across album - Create peaks and valleys - Build to climaxes - Design recovery moments - Balance tension and release ### Transition Planning - Create flow between tracks - Consider key relationships - Match/contrast tempos - Design sonic bridges - Plan crossfades ### Pacing Psychology - Understand listener fatigue - Place breathers strategically - Maintain engagement - Create surprise moments - Reward patience ### Format Considerations - Plan vinyl side breaks - Consider streaming behavior - Account for skip patterns - Design single placement - Create playlist-friendly excerpts ## Sequencing Frameworks ### The Classic Album Arc ``` Track 1: HOOK - Immediate impact opener Track 2: MOMENTUM - Build on opener energy Track 3: PEAK 1 - First major highlight/single Track 4: EXPLORE - New territory, develop themes Track 5: BREATHER - Lower energy, intimate moment Track 6: REBUILD - Regain momentum Track 7: PEAK 2 - Second highlight, emotional core Track 8: DESCENT - Begin resolution Track 9: ASCENT - Final build Track 10: RESOLUTION - Closer, lasting impression ``` ### Energy Intensity Patterns | Pattern | Description | Use Case | |---------|-------------|----------| | Mountain | Low-High-Low | Classic narrative arc | | Double Peak | High-Low-High-Low-High | Epic albums | | Plateau | Consistent intensity | Dance/party albums | | Cascade | High to low descent | Emotional journey | | Climb | Low to high ascent | Building experience | ### Track Role Types | Role | Position | Purpose | |------|----------|---------| | Opener | Track 1 | Set tone, grab attention | | Statement | Tracks 2-4 | Establish album identity | | Single | Tracks 2-4 | Commercial highlight | | Experimental | Mid-album | Push boundaries | | Breather | Mid-album | Provide rest | | Deep Cut | Mid-late | Reward devoted listeners | | Heart | Variable | Emotional core | | Closer | Final | Resolution, lasting impression | | Hidden | Post-closer | Surprise bonus | ### Transition Techniques | Technique | Description | |-----------|-------------| | Key Match | Same key or relative minor/major | | Key Contrast | Dramatic shift for impact | | Tempo Match | Similar BPM for smooth flow | | Tempo Shift | Intentional pace change | | Sonic Bridge | Similar instruments/textures | | Crossfade | Blend endings into beginnings | | Gap Silence | Space for reset | | Thematic Link | Lyrical/motif connection | ## Usage Guidelines ### Sequencing Process 1. List all tracks with key characteristics 2. Identify opener candidates (impact, tone-setting) 3. Identify closer candidates (resolution, memorable) 4. Mark energy levels for each track (1-10) 5. Identify potential singles and highlights 6. Draft energy curve 7. Sequence tracks to create flow 8. Review transitions between adjacent tracks 9. Consider format breaks (vinyl sides) 10. Test full sequence listening ### Sequencing Worksheet ```markdown ## Track Sequencing ### Track Inventory | # | Title | BPM | Key | Energy | Role | Duration | |---|-------|-----|-----|--------|------|----------| | - | [Title] | [BPM] | [Key] | [1-10] | [Role] | [MM:SS] | ### Energy Curve [Visual representation or description] ### Proposed Sequence | Position | Title | Transition Note | |----------|-------|-----------------| | 1 (Opener) | [Title] | Sets tone with... | | 2 | [Title] | Builds via... | | ... | ... | ... | ### Vinyl Side Breaks (if applicable) - Side A: Tracks 1-[X] - Side B: Tracks [X+1]-[Y] ### Pacing Notes - [Observations about flow] - [Potential issues and solutions] ``` ### Quality Checklist - [ ] Opener creates impact - [ ] Energy curve is intentional - [ ] Transitions flow naturally - [ ] Pacing maintains interest - [ ] Closer provides resolution - [ ] Singles are well-placed - [ ] Breathers prevent fatigue ## Integration Points ### Related Skills - SK-MAC-005 (album-conceptualization) - Overall vision - SK-MAC-002 (style-specification) - Track details ### Related Agents - AG-MAC-005 (album-curator-agent) - Primary executor ## Famous Sequencing Examples | Album | Artist | Notable Sequencing | |-------|--------|-------------------| | Dark Side of the Moon | Pink Floyd | Seamless flow, conceptual unity | | OK Computer | Radiohead | Tension build to mid-album peak | | Thriller | Michael Jackson | Front-loaded singles, back-loaded quality | | Abbey Road | Beatles | Medley sequence B-side | | Good Kid, M.A.A.D City | Kendrick Lamar | Narrative chronology | ## References - Album sequencing psychology - Vinyl format considerations - Streaming-era listening patterns
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.