# Nap Ticket

> A planner for one daytime nap that fits the time you actually have. Enter when you can lie down, when you must be up and functioning, and your bedtime tonight; the page prices four fares - quiet rest, a power nap, a coffee nap and a full sleep cycle - says which fit, and punches its pick onto an old-style tram ticket with every stage's clock time. One metered run reads your short note and writes your ticket: the fare by a fixed rule, steps for before and after, and a line about tonight. Not medical advice.

URL: https://nap-ticket.skillsafe.ai/
API: https://nap-ticket.skillsafe.ai/api.html
Built on: @refoundai/energy-management (https://skillsafe.ai/skill/@refoundai/energy-management) - manage your energy, not only your time: notice the dips and recover on purpose.

## Free, in the browser

- Rules of thumb (estimates, not measurements): about 10 minutes to drift off. Power nap: alarm 30 minutes after lying down (about 20 asleep), 10 minutes to shake off grogginess, alarm at least 5 hours before bed. Coffee nap: a cup of coffee drunk quickly, lie down 5 minutes later, alarm 20 minutes after that, 10 minutes to clear, at least 6 hours before bed. Full cycle: alarm 100 minutes after lying down (about 90 asleep), 15 minutes to clear, at least 6 hours before bed. Quiet rest: up to 20 minutes lying still with eyes closed; always fits.
- The page's pick, in order: quiet rest when no nap fits; a full cycle when it fits and last night was under 6 hours or a late night or night shift is next; a coffee nap when it fits and driving or focused work is next, or a power nap does not fit; otherwise a power nap.
- The ticket: eight numbered stage boxes (coffee, lie down, drifting off, light sleep, deep sleep, back to light, alarm, clear-headed) punched for the stages the fare stops at, with clock times; the stub shows tonight's bedtime and, when driving is next, the earliest time to drive (15 minutes after the alarm).
- Exports: a calendar event (.ics) from lying down to the alarm with an alarm at its end, Markdown and JSON.

## The one paid task: plan

Input (all strings): task "plan", free_from, back_by, bedtime (HH:MM), last_night, next, coffee, note, page_facts (one "key | ..." per line: the window, each fare's fit and times, a word-search hint for trouble sleeping at night, the page's pick and the rule).
Reply (one JSON object): title, verdict (quiet_rest, full_cycle, coffee_nap or power_nap), verdict_reason, lie_down, alarm (copied from the fare board), before (2-4 steps), wake (2-4 steps), if_awake, caution (the 15-minute driving wait when driving is next), tonight (names the bedtime), announcement.
The run also reads the note: if it says the person often has trouble sleeping at night, the rule gives quiet rest even when a nap fits.
The page re-checks every reply: the fare against its rule and its fit, the times against the board, the step counts and word limits, the driving wait, the bedtime, every number in the prose, names the note never uses, and any mention of sleep aids, alcohol or supplements.

## Who it is for

Anyone with a gap in the day who wants to rest and still be clear for what comes next: students before a study block, parents after a broken night, shift workers before a late shift, and people with a drive ahead.