sleep-optimizer
Builds a personalized sleep protocol - a fixed wake time held within 30 minutes daily, a chronotype-aligned sleep window, a light-exposure plan, environment settings, evening input rules, and a scripted wind-down routine - from a baseline assessment. Use when someone says "I can't fall asleep", "I wake up at 3am every night", "fix my sleep schedule", or "I'm exhausted no matter how long I sleep". General wellness education, not medical advice - snoring with gasping, suspected apnea, or chronic insomnia route to a physician or sleep specialist. Do NOT use when racing thoughts and daytime stress are the primary complaint - use stress-management instead; for the broader multi-pillar health routine, use longevity-protocol.
- License 许可
- MIT
- 最近更新
- 2026-10-05
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- sleep-optimizer
- metadata
- { "title": "Sleep Optimizer" }
- description
- Builds a personalized sleep protocol - a fixed wake time held within 30 minutes daily, a chronotype-aligned sleep window, a light-exposure plan, environment settings, evening input rules, and a scripted wind-down routine - from a baseline assessment. Use when someone says "I can't fall asleep", "I wake up at 3am every night", "fix my sleep schedule", or "I'm exhausted no matter how long I sleep". General wellness education, not medical advice - snoring with gasping, suspected apnea, or chronic insomnia route to a physician or sleep specialist. Do NOT use when racing thoughts and daytime stress are the primary complaint - use stress-management instead; for the broader multi-pillar health routine, use longevity-protocol.
03 SKILL.md 正文
Sleep Optimizer
Most people try to fix sleep from the wrong end - chasing an earlier bedtime with willpower while their wake time drifts by hours across the week. Wake-time consistency is the single strongest lever, and everything else in the protocol hangs off it. This skill builds a complete protocol: fixed wake time, light plan, environment, input rules, and a scripted wind-down - then changes one variable at a time so the user can tell what worked.
Operating procedure
Steps run in this order because the wake anchor must exist before the bedtime, light plan, and wind-down can be scheduled against it.
Step 1: Assess the baseline
Collect: typical bedtime and wake time, weekday versus weekend (the gap between them is the social-jetlag number to shrink); time to fall asleep and number of night wakings; caffeine dose and timing, alcohol frequency, and evening screen habits; energy dips and peaks across the day; work constraints (fixed start time, shift work); and bed partner factors (snoring, different schedules). Screen the red flags in Escalation before optimizing anything - protocol work cannot fix apnea.
Step 2: Identify chronotype
Classify as early (lark), intermediate, or late (owl) from the natural wake time on unconstrained days. Align the target schedule with the chronotype where life allows rather than forcing an unnatural one - a forced 5am schedule on a strong owl fails within weeks. Label the classification a guess if the user has no unconstrained days to judge from.
Step 3: Fix the wake time and derive the bedtime
Pick one wake time and hold it every day including weekends, within ±30 minutes - this consistency window is the non-negotiable core of the protocol. Count back 7.5-9 hours to set the target bedtime. If the current schedule is far off, shift in 15-30 minute steps every few days rather than one heroic jump.
Step 4: Build the light plan
Morning: 10-30 minutes of bright, preferably outdoor light within an hour of waking to anchor the circadian clock (through a window is a weak substitute; overcast outdoor light still works). Evening: dim household lights and cut blue-heavy screens 1-2 hours before bed. Bedroom: fully dark - blackout curtains or an eye mask.
Step 5: Set the environment
Temperature 16-19 °C (60-67 °F) - cool wins. Noise controlled with earplugs or steady white noise. The bed is for sleep only: no work, no scrolling; the association between bed and wakefulness is what conditioning-based insomnia is made of.
Step 6: Tune the inputs
Caffeine: none within 8-10 hours of bedtime (its half-life is long - a 3pm coffee is still half-active at 9pm). Alcohol: fragments the second half of the night; keep it modest and away from bedtime. Large meals: finished 2-3 hours before bed. Exercise: strongly pro-sleep, but schedule vigorous sessions earlier in the day.
Step 7: Script the wind-down routine
A 30-60 minute buffer of low-stimulation activities that becomes the cue for sleep. Script it concretely with times, not as a vague intention - see the worked artifact.
Step 8: Install the wakefulness rule and nap policy
Awake in bed more than ~20 minutes: get up, do something calm in dim light, return when sleepy. No clock-watching - turn the clock face away; checking the time raises arousal. Naps: only if nighttime sleep is intact, 10-20 minutes, early afternoon only.
Step 9: Review at 2 weeks
Compare sleep latency, night wakings, and morning energy against baseline. Adjust exactly one variable at a time - changing three things at once makes the protocol unfalsifiable. Improvement typically shows in 1-2 weeks of consistent wake times; no improvement after 4 weeks of genuine adherence is an escalation trigger.
Worked artifact
Example: intermediate chronotype, 8:00 work start, current weekend drift of 2.5 hours.
SLEEP PROTOCOL - [name]
Wake time: 6:45 every day, +/-30 min max (weekends included)
Bedtime: 10:45 (8h window) - shift from current 12:30 in 30-min steps
Morning: coffee on the balcony 7:00-7:20 (light + caffeine together)
Caffeine: last cup 12:45pm (10h before bed)
Evening: dinner by 8:00 / lights dimmed + screens off 9:30
Bedroom: 18C, blackout curtains, phone charges in kitchen, clock turned away
WIND-DOWN (10:00-10:45)
10:00 screens off, tomorrow's top-3 jotted down (closes open loops)
10:10 warm shower
10:25 paper book on the couch, lamp only
10:45 lights out
If awake >20 min: up, armchair + dim lamp, back when sleepy.
Review Sun evening, week 2: latency __ min / wakings __ / AM energy 1-10 __
Change ONE variable next cycle: ______
Deliverable
Produce a one-page protocol containing: the fixed wake time with its ±30 minute rule, target bedtime with the shift plan if needed, the morning and evening light plan, the environment checklist (temperature, dark, noise, bed-for-sleep-only), the evening input rules with their hour cutoffs, the scripted timed wind-down, the 20-minute wakefulness rule and nap policy, and the 2-week review with the one-variable rule.
Do NOT
- Do not anchor the protocol on bedtime; bedtime follows sleepiness, wake time drives the clock.
- Do not allow weekend wake times to float "as recovery" - the Monday cost is a self-inflicted timezone shift.
- Do not change multiple variables per review cycle; the protocol stops being diagnostic.
- Do not prescribe lying in bed trying harder; past 20 minutes that trains the bed-wakefulness association.
- Do not recommend melatonin dosing, sleeping medication, or supplement stacks - that is a physician conversation.
- Do not treat stress-driven rumination with sleep hygiene alone; when racing thoughts are the driver, pair with stress-management.
Quality bar
The protocol ships when: the wake time is a single clock time with the ±30 minute rule stated; every input rule carries its hour cutoff (caffeine 8-10h, meals 2-3h, screens 1-2h); the wind-down is scripted with actual times, not adjectives; the red-flag screen was run and documented; and the review names the date, the metrics, and the one variable eligible to change.
Escalation
This is general wellness education, not medical advice - a licensed physician or sleep specialist owns anything clinical. Refer promptly, before or alongside protocol work, for: loud snoring with gasping, choking, or witnessed breathing pauses (apnea signs - protocol work will not fix a mechanical airway problem); severe daytime sleepiness such as dozing while driving; insomnia persisting 3+ months despite consistent protocol adherence (CBT-I with a specialist is the evidence-based treatment); restless legs or acting out dreams; or shift-work schedules causing serious impairment. Route neighbors: stress-management when daytime stress drives night rumination, longevity-protocol for the full health routine this protocol slots into.
04 同仓库更多 Skills
study-system
Converts a syllabus or topic list into an evidence-based study plan - material atomized into testable units, a spaced-repetition flashcard schedule with expanding intervals, active recall and Feynman-technique prompts instead of rereading, interleaved weekly sessions, and a practice-testing cadence with an error log. Use when someone says "help me study for this exam", "build me a study schedule", "I keep rereading and forgetting everything", or wants to learn a curriculum efficiently. Do NOT use for acquiring a spoken language specifically - use language-learning instead - or for building everyday habits - use habit-builder instead.
stress-management
Builds a personalized one-page stress toolkit - mapped triggers, three rehearsed in-the-moment interventions, a recovery menu, and prevention habits - from a week of trigger tracking. Use when someone says "I'm constantly stressed", "I can't switch off after work", "help me deal with anxiety before meetings", or "I keep snapping at people". General wellness education, not medical or mental-health treatment. Do NOT use when the primary complaint is poor sleep - use sleep-optimizer instead; for building a single recurring habit, use habit-builder; for broader life direction and goals, use life-coach.
second-brain
Sets up a PARA-based second brain in any notes app (Notion, Obsidian, Apple Notes, Logseq) - Projects, Areas, Resources, Archives buckets, a frictionless universal capture inbox, weekly organizing, wiki-link and map-of-content linking, progressive summarization for recall, and maintenance rituals. Use when someone says "help me set up a second brain", "my notes are a mess and I can never find anything", "how do I organize Obsidian with PARA", or captures ideas but never uses them. Do NOT use for designing the underlying Notion database properties and relations - use notion-database instead - or for a task-management workflow - use gtd-system instead.
journal-framework
Designs a sustainable daily journaling practice - morning pages, gratitude, intention setting, evening reflection, and weekly review - matched to the user's goal, with copy-paste templates and a rotating prompt library. Use when someone asks "help me start journaling", "give me journal prompts", "I keep abandoning my journal", or "build me a morning pages routine". Do NOT use for building a general habit or streak system - use habit-builder instead; do NOT use for organizing notes and knowledge into a retrieval system - use second-brain instead; for structured end-of-week planning reviews, see weekly-review.
habit-builder
Turns a vague intention into a one-page habit plan - a specific implementation intention, a habit-stack anchor sentence, cue-craving-routine-reward loop mapping, environment design, a never-miss-twice tracking method, and weekly review questions. Use when someone says "help me build a habit", "I want to exercise more but can't stick with it", "why do my habits keep failing", or wants to break a bad habit by removing its cues. Do NOT use for goal-setting with an accountability structure - use goals-accountability instead; for a full training program, use fitness-program.
goals-accountability
Turns vague intentions into SMART goals with both lagging targets and controllable leading indicators, then keeps them alive with a 10-minute weekly check-in template, an accountability structure (visible goals, public commitments, partner check-ins), and a quarterly reflection that converts the quarter into lessons. Use when someone says "help me set goals I'll actually stick to", "I set resolutions and abandon them by February", "build me a goal tracking system", or wants a weekly review cadence for personal targets. Do NOT use for company or team objective-setting - use okr-builder instead - or for building daily habits - use habit-builder instead.