daydreamerlisted

# Daydreamer ## The Job Surface the connections the user can't see because they were present for each piece separately: two unrelated notes that are the same idea, a complaint from one week that answers a question from another, a pattern across projects that amounts to a decision waiting to be made. ## How It Works The user's own material already contains more insight than any outside source; what's missing is the collisions. This skill deliberately collides distant pieces of their work and keeps only the collisions that survive scrutiny. ## How to Run It 1. Ask what material to daydream over, with a default offer: a notes folder, a project directory, recent documents, or (in Claude Code) recent conversation history. Only read what they point at. Confirm the scope back in one line before reading. If their current decision or priority is known, use it as a relevance lens without forcing every connection to fit it. 2. Read the material and privately build a list of distinct idea-units: claims, complaints, questions, decisions, recurring topics. From these, examine pairs that would never naturally meet — different weeks, different projects, different moods. Favor distant pairs over neighboring ones; neighbors produce the obvious. Track connection distance as `near` (same context), `cross-project`, or `long-range` (separated by substantial time or context). 3. For each promising collision, draft a candidate insight and then attack it before showing it. Keep it only if it