habits

Files (3)

• SKILL.md
• routing.yaml · evals/
• habits.skill

SKILL.md (first lines)

# habits

## Core Philosophy
Willpower is a depreciating cognitive asset. Systems relying on sheer discipline inevitably collapse under stress or fatigue. Sustainable habit formation is an engineering discipline governed by environment architecture, identity-based reinforcement, and friction reduction. Following James Clear's *Atomic Habits* and BJ Fogg's *Tiny Habits*, habits must be anchored to existing neurological triggers and engineered to execute in under two minutes during initial activation.

---

## 4-Step Habit Engineering Framework

### Step 1: Identity & Cue Architecture (Make It Obvious)
1. **Identity-Based Stance**:
   - Shift from outcome-focused ("I want to write 1,000 words a day") to identity-focused ("I am a technical writer who ships daily").
2. **Implementation Intentions**:
   - Specify deterministic execution parameters:
     - Formula: *"I will [BEHAVIOR] at [TIME] in [LOCATION]."*
     - Example: *"I will complete 20 minutes of system architecture review at 8:00 AM at my primary desk."*
3. **Habit Stacking**:
   - Anchor the new routine immediately after an immutable existing habit:
     - Formula: *"After [CURRENT HABIT], I will [NEW HABIT]."*
     - Example: *"After I pour my first morning coffee, I will open my terminal and commit yesterday's journal."*

### Step 2: Friction Modulation (Make It Easy / Make It Hard)
1. **The 2-Minute Rule**:
   - Downscale the target behavior until the initial ritual takes $< 120$ seconds:
     - "Read 30 pages" -> "Read 1 page".
     - "Exercise for 45 minutes" -> "Put on running shoes and step outside".
2. **Environmental Friction Engineering**:
   - *Good Habits*: Reduce steps to initiation to $\le 1$ action (e.g. guitar on stand, IDE workspace opens automatically on boot).
   - *Bad Habits*: Increase friction to $\ge 3$ distinct physical barriers (e.g. phone in another room, app blockers, logout after session).

### Step 3: Craving & Reward Loops (Make It Attractive & Satisfying)
1. **Temptation Bundling**:
   - Pair an obligatory habit with an immediate hedonic reward:
     - Formula: *"Only while [DOING NEEDED HABIT], I am allowed to [ENJOY DESIRED ACTIVITY]."*
2. **Immediate Visual Reinforcement**:
   - Use physical habit trackers or lightweight markdown matrices to record completion instantly.
3. **The "Never Miss Twice" Rule**:
   - Missing a habit once is an accident; missing it twice is the beginning of a new, competing habit. If a day slips, execute an emergency micro-version the following day without fail.

### Step 4: Tracking, Accountability & Drift Auditing
1. **Weekly Consistency Score**:
   - Measure completion percentage: Target 80–85% consistency across an 8-week cycle (100% rigidity often induces brittle failure).
2. **Habit Retirement / Graduation**:
   - Once a habit reaches automaticity (typically 66 days), transition it to maintenance mode and introduce a new atomic habit.

---

## Deliverable Format: Habit Architecture Blueprint (`HABIT-SYSTEM.md`)

```markdown
# Personal Habit System Specification

## 1. Identity Thesis & Core Routine
- **Identity Goal**: [Who do you wish to become? e.g. "A disciplined software craftsman"]
- **Primary Keystone Habit**: [The single highest-leverage habit]

## 2. Habit Stack & Implementation Intentions
| Keystone Habit | Anchor Cue (Current Habit) | Time & Location | 2-Minute Starter Version |
|---|---|---|---|
| Deep Work Block | Pour morning tea | 8:30 AM @ Home Desk | Open editor and write 1 line |
| Daily Exercise | Close laptop at 6:00 PM | Living room mat | Put on workout shoes & stretch |
| Nightly Reading | Turn off bedside lamp | 10:30 PM in bed | Read 1 paragraph of book |

## 3. Friction Architecture
- **Positive Habits (Friction Reduced)**:
  - [Action taken to make good habit effortless]
- **Negative Habits (Friction Added)**:
  - [Action taken to introduce 3+ barriers to bad habit]

## 4. Emergency Fallback Protocol ("Never Miss Twice")
- If deep work block is interrupted by emergency: Execute 5-minute markdown reflection before sleep.
```

---

## Worked Example: Daily Technical Writing System

- **Identity**: "I am an engineer who publishes insights publicly."
- **Stack**: "After I push my final git commit of the afternoon, I will draft 1 concrete lesson learned in `journal.md`."
- **2-Minute Rule**: Open markdown file and write 1 sentence summary.
- **Friction Design**: VS Code automatically restores `journal.md` tab on launch; social media sites blocked until file is modified.
- **Consistency**: 26 out of 30 days active; published 4 long-form technical deep dives in the quarter.

---

## Verification Checklist

- [ ] Every habit has a defined implementation intention (Time + Location + Cue).
- [ ] Initial version of the habit passes the 2-minute test.
- [ ] Positive habit requires $\le 1$ physical step to initiate.
- [ ] Competing bad habits have at least 2 physical or digital friction barriers added.
- [ ] "Never miss twice" emergency fallback is documented.

---

## Anti-Patterns

- **Overambitious Overhauls**: Attempting to change 10 habits simultaneously on January 1st.
- **Vague Intentions**: Committing to "eat healthier" or "code more" without an explicit anchor cue.
- **Punitive Shame Loops**: Beating oneself up over a single missed day rather than diagnosing the environmental failure point.

From poorvith-mp/skills-personal, MIT.

More from poorvith-mp/skills-personal