Ossuary

Ossuary is a lean skeleton (design system theme.css, versioned store, date/streak math, view shell) plus Kiro steering docs, EARS specs, a tests-on-save hook, and a start-new-app scaffolding skill.

What it does

Three complete apps ship with it: Deadline Crypt (deadlines Alive/Dying/Dead; Dead ones resurrect with a new date), Ritual (daily practice as candle flames; a missed day dims the flame, nothing punishes), and Pantry Ghost (food expiry: Fresh / Use soon / Past date). All local-first, offline, no backend.

How I built it

Built spec-driven in Kiro CLI sessions under the entrant's own account on the free plan (Kiro Web is paid-gated): Session 1 skeleton (72 tests), Session 2 Deadline Crypt (127), Session 3 Ritual (174), Session 4 Pantry Ghost (221, full suite re-run independently after every session). Steering docs carried the rules into every generation: local-first, vanilla JavaScript, no build step, pure logic with tests, calm design, no shame mechanics. A manual finish pass audited copy (no punitive language found) and fixed phone-viewport defects (44px minimum tap targets, 16px phone form controls).

Challenges and what's next

Honest note: the specs' manual-pass checkboxes remain unticked because an eyeball on a physical phone is still owed.

Division of work

The entrant set the product rules and drove the sessions; his assistant Ember authored the design and specs and verified tests; Kiro wrote the app code from those specs in-session.

Built With

• bun
• css
• html
• javascript
• kiro