flow-capture
Capture streams of consciousness, tangential thoughts, and hyperfocus output. Extract signal from noise. Use when ideas are flowing faster than they can be organized, or when returning to raw notes/thoughts that need pattern extraction.
When & Why to Use This Skill
Flow Capture is a specialized productivity skill designed to support neurodivergent cognition and high-flow states. It facilitates the seamless recording of non-linear streams of consciousness and tangential thoughts, acting as a 'signal tuner' to extract meaningful patterns from raw mental output. By removing the friction of premature organization, it helps users preserve complex ideas and maintain momentum during hyperfocus periods.
Use Cases
- Capturing rapid-fire ideas during deep work or hyperfocus sessions without interrupting the creative flow.
- Synthesizing messy, non-linear notes into 'constellation' maps that reveal hidden connections between unrelated topics.
- Generating 'resumption anchors' and context snapshots to help users quickly re-engage with complex tasks after a break.
- Extracting actionable insights and recurring themes from raw thought dumps or 'brain dumps' for better knowledge management.
| name | flow-capture |
|---|---|
| description | Capture streams of consciousness, tangential thoughts, and hyperfocus output. Extract signal from noise. Use when ideas are flowing faster than they can be organized, or when returning to raw notes/thoughts that need pattern extraction. |
Flow Capture
This skill provides specialized support for neurodivergent cognition patterns, specifically for capturing non-linear thought streams and extracting meaningful patterns without forcing premature structure.
Purpose
To receive and process streams of consciousness during flow states or hyperfocus periods, then extract actionable patterns without imposing linear constraints that disrupt neurodivergent thinking patterns.
When to Use This Skill
Use this skill when:
- Ideas are flowing faster than they can be organized
- A user is dumping thoughts in rapid, non-linear fashion
- Returning to raw notes or thought streams that need pattern extraction
- Tangential thinking is producing valuable signal mixed with apparent noise
- A user needs to resume work after hyperfocus breaks
How to Use This Skill
Phase 1: Capture (Pure Reception)
During active thought streaming:
Receive without interrupting
- Record exactly as given, without reorganization
- Treat tangents as data, not noise
- Avoid imposing "stay on topic" pressure
- Hold threads while the user spirals across topics
What NOT to do during capture
- Do not ask "what's your goal?" during flow
- Do not force linear structure
- Do not judge "productivity" of tangents
- Do not impose premature organization
Phase 2: Pattern Extraction (After Flow Stops)
Once the stream concludes:
Surface recurring themes
- Identify patterns without judgment
- Map connections the user sensed but didn't articulate
- Extract actionable nodes without flattening complexity
- Preserve the networked nature of the thinking
Output format
- Present patterns as constellations, not hierarchies
- Show connections between seemingly unrelated threads
- Highlight recurring metaphors, terms, or concepts
- Identify energy signatures (where attention clustered)
Phase 3: Resumption Anchors (When Flow Breaks)
When hyperfocus or flow state ends, automatically create:
Context snapshot
- Capture state of mind right before stopping
- Document questions being held
- Record insights forming (even if incomplete)
Energy signature
- Note what felt alive before stopping
- Identify momentum direction
- Mark areas of high engagement
Multiple re-entry points
- Quick win path (low energy return)
- Deep dive path (high momentum return)
- Tangent path (curious about something adjacent)
- Walk away path (if this isn't what's needed now)
RAM contents
- Assumptions made that aren't in code or notes
- Things "about to" be done
- Tradeoffs being considered
- Patterns noticed but not yet documented
Philosophical Foundation
This skill treats neurodivergent cognition as signal reception, not task execution.
Core principle: You are the antenna. Claude is the tuner.
The validation is felt sense, not external metrics. If patterns don't resonate, they may not be ready or the tuning needs adjustment.
Format Guidelines
Use imperative/infinitive form for all instructions. Maintain objective, instructional language.
Preserve essential strangeness - do not optimize away interesting or unusual connections in service of "professional polish."
Validate through resonance - ask "Does this resonate?" rather than imposing external validation criteria.