$npx -y skills add human-avatar/skills-for-humanity --skill s4h-cognition-attentionMaps the attention economy of a mind or situation — what captures it, what depletes it, and how to protect it. Use when asked 'why can't I focus', 'attention keeps getting pulled away', 'how do I protect deep work', 'what's stealing my focus', 'I keep getting distracted', or when
| 1 | # Cognition: Attention |
| 2 | |
| 3 | Attention is the scarcest cognitive resource — and unlike memory or reasoning, it cannot be trained to be unlimited. It can only be allocated, protected, and defended. Most focus problems are not character failures; they are design failures. The environment, the workflow, or the communication system is structured in a way that systematically fragments attention and prevents sustained engagement with what matters most. |
| 4 | |
| 5 | The attention economy framing, developed from William James's foundational work on voluntary and involuntary attention, treats focus as a resource subject to supply and demand. What demands attention is not random: salience (bright, loud, moving things), novelty (what's new or unexpected), emotional charge (threats, social signals, strong affect), and personal relevance all reliably override deliberate focus. Design your attention environment knowing what the competition is. |
| 6 | |
| 7 | The key distinction: attention threats come in two forms. **Capture** — things that involuntarily seize focus through sensory or emotional hooks — and **depletion** — things that gradually drain the capacity for sustained focus even when no single interruption is dramatic. Both matter. Capture is visible and acute; depletion is slow, cumulative, and often invisible until cognitive capacity is exhausted. |
| 8 | |
| 9 | --- |
| 10 | |
| 11 | ## Your Process |
| 12 | |
| 13 | **Step 1: Define the Attention Context** |
| 14 | Identify whose attention, in what context, for what purpose. Individual focus (a person trying to do deep work)? Group attention (a team, a meeting)? Communication attention (an audience you need to hold)? The diagnosis differs by context. |
| 15 | |
| 16 | **Framing check:** Confirm the specific attention context before continuing. State what you've identified — whose attention, in what setting, and what the goal is — in one sentence, then use `AskUserQuestion`: |
| 17 | - **Question:** "I'm reading this as: [your one-sentence framing of whose attention is at issue, in what context, and what you're trying to achieve]. Is that right?" |
| 18 | - **Header:** "Framing" |
| 19 | - **Options:** |
| 20 | - **Yes — proceed** — framing is correct |
| 21 | - **Adjust** — one element is off; user will correct it before you continue |
| 22 | - **Reframe** — different situation than read; incorporate the correction before proceeding |
| 23 | |
| 24 | **Step 2: Map Attention Demands** |
| 25 | List everything currently competing for attention in this context. Separate into: |
| 26 | - **Legitimate demands:** things that genuinely require attention and have claim to the time |
| 27 | - **Capture threats:** involuntary hijacks — notifications, interruptions, ambient noise, social signals |
| 28 | - **Depletion sources:** low-grade cognitive drains — ambient worry, unresolved decisions, low-priority tasks that create background anxiety, decision fatigue |
| 29 | |
| 30 | **Step 3: Assess Current Allocation** |
| 31 | Where is attention actually going versus where it should go? Estimate the proportion of cognitive bandwidth consumed by each category. Identify the gap between actual and ideal allocation. |
| 32 | |
| 33 | **Before narrowing:** Use `AskUserQuestion` to confirm the demand map before proceeding to solutions: |
| 34 | - **Question:** "I've mapped [N] attention demands across legitimate, capture, and depletion categories. Before I prioritise defences, are there any sources I've missed or any you'd flag as especially significant?" |
| 35 | - **Header:** "Demand Map" |
| 36 | - **Options:** |
| 37 | - **Proceed** — the map looks complete |
| 38 | - **Add a demand** — user will name a specific source to include |
| 39 | - **Correct a category** — user will reclassify something |
| 40 | |
| 41 | **Step 4: Diagnose the Core Problem** |
| 42 | What is the primary failure mode? Choose the dominant one: |
| 43 | - **Environment design failure:** physical or digital environment is structured to maximise interruption |
| 44 | - **Boundary failure:** legitimate demands have no protective scheduling; everything competes in real time |
| 45 | - **Depletion spiral:** low-level cognitive load is accumulating to the point where sustained attention becomes impossible |
| 46 | - **Capture vulnerability:** specific high-salience threats (notifications, social media, email) are bypassing deliberate intent |
| 47 | |
| 48 | **Step 5: Design the Defence** |
| 49 | For each identified threat, prescribe a specific structural intervention. Defences fall into four types: |
| 50 | - **Elimination:** remove the demand entirely (unsubscribe, turn off, delete) |
| 51 | - **Batching:** process the demand in a designated window rather than on-demand (email twice daily, messages at noon) |
| 52 | - **Protection:** create structural conditions where capture threats cannot reach (phone in another room, notifications off, closed door) |
| 53 | - **Offloading:** capture open loops |