Inspiration

Every pomodoro app I have tried tells me the time. None of them tell me that I just rebuilt my attention span around a notification. The timer is polite, so drifting stays cheap — and at 2am cheap is the whole problem.

So I wanted a timer where distraction has a body. Something in the room moves when I lose the thread. Not a red badge, not a streak that resets — a presence, with a distance.

What it does

A candle is the clock. Four ghosts are the remaining slack.

You pick 25, 50 or 90 minutes and name what you are keeping watch over. That name stays on screen the whole session. Then every time something pulls you away, you press Something caught my eye — and one ghost takes a step toward the flame while the room dims a degree.

The ghosts do not retreat. They only close. At the end you get a verdict and a recap chart of exactly when they found you.

How it was built

The domain is deliberate: src/lib/session.ts holds the whole ladder as pure, immutable transitions with no React, no DOM and no timers. Nineteen tests cover the tolerance curve, the clamp, the paused no-op and the dread monotonicity — written against requirement IDs from .kiro/specs/haunt-ladder/requirements.md.

The reason is the tolerance curve. max(45, floor(totalSeconds / 10 / (step + 1))) — a 25-minute watch gives you 150 seconds of grace on the first rung, then tightens to 45. My first version collapsed to zero on the last rung, which made the final ghost free. The tests caught it; a component-local counter would have hidden it.

The UI is one hand-written stylesheet. Dread flows into two custom properties on :root — --dread and a derived --lamp — and the candle glow, fog opacity and fog speed all read from them. One React commit dims the room.

Challenges

  • Making darkness legible. Early builds got atmospheric but unreadable. The fix was pinning --lamp to a 0.18 floor so the candle is still the brightest thing in the room at maximum dread.
  • The last rung. Covered above — a threshold that degraded to zero made the fourth ghost meaningless.
  • Honest endings. The verdict is chosen from visit count, never from remaining time, so quitting at minute three with a clean slate cannot read as a perfect night.

What I learned

Spec-first paid for itself immediately. Every time the agent tried to inline the tolerance arithmetic into the component, .kiro/steering/tech.md pushed it back to lib/. The hooks ran the suite on each src/lib edit, which is how the rung bug surfaced within a minute of being written.

What's next

A sound cue on each new visit, and the option to leave the tab and get a countdown in the title bar — both deliberately out of v1 to keep the surface small.

Built With

Share this project:

Updates

Submission history