šŸŒ‘ Into the Dark: Soulbound Codex

Published: (December 5, 2025 at 02:40 PM EST)
4 min read
Source: Dev.to

Source: Dev.to

Demo Image

Background

Kiroween is a Halloween‑themed hackathon hosted by AWS to showcase the power of Kiro, their AI coding agent. The challenge was to build something ambitious and creative in under a month.

For me, this was a plunge into the unknown: my first time mixing AI, gothic aesthetics, multi‑module UI architecture, and advanced agent workflows. The result was Soulbound Codex, a fully‑featured productivity suite transformed into a spooky, immersive experience.

What I Built: Soulbound Codex

Kiroween is a dark‑themed productivity platform where:

  • āœļø Ghost Writer – live AI writing suggestions
  • šŸ“– Necronomicon Notes – write inside an ancient, animated tome
  • āš°ļø Graveyard Dashboard – tasks become tombstones with physics and ritual animations
  • šŸ”® Terminal Tarot – analyzes your git commits and generates tarot readings
  • šŸŒ• Moon Phase Calendar – tracks time with astronomical accuracy
  • šŸ•øļø Ambient soundscapes and gothic UI create an atmospheric, magical experience

Everything is powered by:

React, TypeScript, Vite, CSS Modules, Firebase, OpenRouter AI, and Kiro’s spec‑driven development workflow.

Technical Achievements

  • Full multi‑module React architecture with shared state and offline‑first design
  • AI writing assistant powered by NVIDIA Nemotron + OpenRouter fallback
  • Git‑based divination engine using isomorphic-git directly in the browser
  • Cloud sync with Firebase (auth, database, storage)
  • Custom gothic animations, particle effects, and parchment rendering
  • Keyboard‑driven navigation for power users
  • Theme engine with instant switching
  • Import/export system for notes & tasks
  • Accessibility enhancements layered into all modules

This isn’t just a themed UI — it’s a real productivity platform.

How Kiro Helped

Kiro acted as a development partner, not just a tool.

Spec‑Driven Development

  • All requirements, UX behavior, and architectural patterns were described in .kiro/specs.
  • Kiro converted these specs into clean, modular code with no rework or ambiguity.

Steering Docs

  • Controlled visual style consistency, AI response tone, coding conventions, and architecture boundaries.

Agent Hooks

  • Automated workflows such as:
    • Context extraction in Ghost Writer
    • Auto‑generating test stubs
    • Sentence‑completion triggers
    • Analysis pipelines for Terminal Tarot

New Kiro Features

  • Property‑based testing that validated feature specs against implementation
  • Checkpoints allowing rewinding of Kiro’s code changes at any moment
  • Kiro CLI for running custom agents inside the terminal
  • Team‑oriented workflows with centralized spec + steering management

Building Kiroween without Kiro would have taken months, not weeks.

Barriers I Faced

  • ā³ Time pressure – juggling work, life, and a huge multi‑module project; some nights I only had 30–60 minutes to code.
  • 🧩 Complex feature interactions – notes, tasks, AI suggestions, tarot readings all required shared global state, cross‑module navigation, offline persistence, and high performance.
  • šŸ‘» UI precision – ghost animations, parchment effects, moon phases demanded careful tuning.
  • šŸ”Œ AI integration unpredictability – different models behave differently; caching, retries, and fallbacks had to be built manually.
  • 🌐 Git analysis in the browser – parsing commits locally without a server was extremely challenging.

Each obstacle pushed the project forward.

Development Timeline (Condensed)

Day 1–3: Foundations

  • Core React architecture, navigation, theme engine, notes scaffold, task system prototype

Day 4–6: Feature Expansion

  • Ghost Writer AI integration, Graveyard Dashboard animations, Moon Phase calendar, markdown editor

Day 7–10: Advanced Systems

  • Git commit analysis engine, tarot generation logic, AI caching + fallback, cloud sync, authentication

Day 11–14: Polish & Stability

  • Particle effects, keyboard shortcuts, import/export, accessibility, final bug hunts, documentation

By the end, Kiroween had 4 full modules, dozens of features, tests, and a cohesive UX.

What I Learned

  • šŸ’” AI‑assisted development is a new paradigm – AI amplifies developers, turning weeks of boilerplate into minutes.
  • 🧠 Specs matter more than ever – clear specs = perfect code generation; vague specs = confusion.
  • āš™ļø Offline‑first architecture is underrated – design for offline first, sync second, and everything becomes more robust.
  • šŸŽØ Aesthetic has functional power – beautiful productivity tools keep users engaged longer.
  • 🪦 Ritual beats routine – a task ā€œsinking into the groundā€ provides emotional closure no checkbox can.

Final Thoughts

Building Kiroween felt like walking through a dark forest with a lantern—each step illuminated by Kiro, yet the path always full of mystery. It taught me:

  • How to build complex software fast with AI
  • How design affects user emotion
  • How to plan, structure, and ship under pressure

Most importantly, Kiroween showed that productivity tools don’t need to be boring; they can be atmospheric, magical, and deeply personal. If you want a tool that turns everyday tasks into rituals, Kiroween is for you.

Back to Blog

Related posts

Read more Ā»