deep-productivity
Master deep work productivity through the three types of work framework (Building, Maintenance, Recovery). Use when user needs to: (1) Build a sustainable deep work routine with just 1 hour/day, (2) Create vision/anti-vision for life direction, (3) Structure goals using the 10-year → 1-year → 1-month → 1-week hierarchy, (4) Apply project-based learning to bridge skill gaps, (5) Identify lever-moving tasks that actually progress goals, (6) Balance focus work with necessary recovery for creativity.
What this skill does
# Deep Productivity Mastery
Transform your life with just 1 hour/day of focused building work. This skill applies the three types of work framework—Building, Maintenance, and Recovery—to help you create meaningful progress toward your goals.
## When to Use This Skill
- User wants to build something meaningful (business, creative work, personal project)
- User struggles with focus, distractions, or unclear priorities
- User has limited time (1 hour/day) and wants to maximize impact
- User feels stuck in "doing mode" without real progress
- User wants to design a sustainable productivity system
## Core Framework: Three Types of Work
Before diving into workflows, understand the three types of work:
1. **Building** - Intense bursts of deep work to bring a project to life (products, services, brands, skills)
2. **Maintenance** - Consistent, often repetitive work to keep what you built alive (marketing, customer service, operations)
3. **Recovery** - Rest, leisure, and lack of narrow focused stress that allows breakthrough ideas to form
**Your goal**: Build for 1 hour/day until you can pursue your vision full-time. Then transition to maintenance work.
## Workflow: The 90-Day Deep Work Transformation
Follow this sequence to establish a sustainable deep work practice:
### Step 1: Diagnose Your Current State
Assess where you are on the focus spectrum:
| State | Symptoms | Root Cause |
| ---------- | ------------------------------------------ | ------------------ |
| Distracted | Multiple programs running, attention split | Lack of clarity |
| Anxious | Overwhelmed by goals, paralyzed | Challenge >> Skill |
| Bored | Repetitive work, self-centered thoughts | Challenge << Skill |
| Flow | Challenge ≈ Skill, time flies | Optimal state |
**Key insight**: Humans can process ~50 bits of conscious info/second. Every distraction reduces your potential. You have ~125 billion bits total in a lifetime—use them wisely.
### Step 2: Create Vision & Anti-Vision
**Vision**: Your ideal future (be specific, even if it seems irrational)
**Anti-Vision**: What you don't want, where you'll end up without change
**Exercise** (15 minutes):
1. Write out everything you DON'T want in your life—feel the discomfort
2. Write out your ideal future—be petty, think big, ignore "rational" limits
3. List all distractions standing between you and that future
4. Identify people, apps, activities to temporarily remove
**Rule**: Success is less about discipline and more about removing distractions that make discipline difficult.
### Step 3: Build Your Goal Hierarchy
Create a clear mental frame you can tap into anytime:
```
10-Year Goal → Where you want to be
↓
1-Year Goal → Milestone to reach this year
↓
1-Month Goal → What you must achieve this month
↓
1-Week Goal → Actionable tasks this week
↓
Lever-Moving Tasks → Daily 1-3 priorities that move the needle
```
**Example**:
- 10-Year: Build a global digital education company
- 1-Year: Launch MVP and get 1000 paid subscribers
- 1-Month: Create minimum viable course product
- 1-Week: Record 3 video lessons, set up payment system
- Daily: Record 1 lesson (30 min), promote on social (30 min)
### Step 4: Apply Project-Based Learning
**Principle**: Learn by building, not by consuming tutorials.
**Why tutorials fail**: Endless consumption creates endless options and overwhelm. Most information goes to waste because you can't apply it.
**How to use project-based learning**:
1. Choose something to build that moves the needle toward your vision
2. Brain dump everything you know about it
3. Save 3-5 sources to emulate—study their structure
4. Outline into sections, milestones, knowledge gaps
5. Start building with what you know
6. Let the project expose gaps—search for answers as needed
**A project can be anything**: Your health, a business, a skill, a creative work. A project is simply a structured way to achieve a goal.
### Step 5: Design Your 1-Hour Deep Work Protocol
Structure your daily deep work block using the clarity-importance-urgency framework:
**Before the session (2 min)**:
- Review today's lever-moving task (from hierarchy)
- Ask: "If I could only do one thing today, what would it be?"
**During the session (50 min)**:
- Single-task on that one thing
- If blocked, break into smaller sub-goals
- Apply challenge ≈ skill: if anxious, simplify; if bored, increase challenge
**After the session (8 min)**:
- Journal what you accomplished
- Identify the next micro-step
- Note any ideas that emerged ( Default Mode Network will generate insights during rest)
**Optimal timing**: Morning, after filling your mind with education/ideas, before emptying with planning.
### Step 6: Balance Work with Recovery
**Critical**: Your best ideas come during rest, not during work.
**Daily structure** (the routine of successful creatives):
- **Morning**: Creation, output, focus (deep work block)
- **Afternoon**: Learning, ideas, socialization (fill your mind)
- **Evening**: Journaling, planning, meditation (empty your mind)
**Recovery activities** (not escapism):
- Walking (especially without phone)
- Reading fiction or philosophy
- Daydreaming, imagining futures
- Meaningful conversation
- Solitude without distractions
**The Default Mode Network**: When you stop focusing externally, your brain connects regions for visual thinking and creativity. This is where breakthrough ideas emerge.
## Decision Tree: What to Work On
```
What stage are you in?
├─ Pre-foundation (no clear vision)
│ └─ Focus: Vision & Anti-Vision exercise (Step 2)
│
├─ Foundation (vision set, no project)
│ └─ Focus: Goal hierarchy + First project definition (Steps 3-4)
│
├─ Building (active project in progress)
│ └─ Focus: Daily 1-hour protocol + Lever-moving tasks (Steps 5)
│
└─ Maintenance (project generating value)
└─ Focus: Systematizing, delegating, starting next project
```
## Quick Reference: The Deep Work Checklist
Before starting each session, confirm:
- [ ] I know exactly what one task I'm working on
- [ ] The challenge is just above my current skill level
- [ ] I understand WHY this matters to my future
- [ ] Distractions are removed (phone, tabs, notifications)
- [ ] I have a hard stop time (60 or 90 minutes max)
After each session, confirm:
- [ ] I made measurable progress on my project
- [ ] I identified the next micro-step
- [ ] I captured any ideas that emerged
- [ ] I'm transitioning to recovery (not maintenance work)
## Embracing Uncertainty
**Expect to feel lost, overwhelmed, and like you don't know what you're doing.** This is normal and signals growth.
- Uncertainty is signal, not noise
- Your brain filters reality based on what you're obsessed with
- Invest in your portfolio of failures until you can afford to succeed
- The "certain" life is the least rewarding
**Key insight**: Neurons that fire together, wire together. Being extreme about your goals accelerates neuroplasticity.
## Resources
### references/
- `focus-types.md` - Detailed breakdown of Building, Maintenance, Recovery
- `flow-formula.md` - The challenge ≈ skill equation explained
- `default-mode-network.md` - How recovery generates creative insights
### scripts/
- `assess_focus.py` - Diagnose current focus state
- `generate_hierarchy.py` - Create goal hierarchy from vision statement
- `track_levers.py` - Track lever-moving tasks and progress
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.