Ignition Labs Documentation

Ignition Labs is a founder-led engineering studio. These docs reflect how we think, build, and refine the Ignition Labs OS.

Getting started

If you’re new to the Ignition Labs OS, begin with the why before the how.

Ignition Labs: At a Glance
Who we are, what we stand for, and why the OS exists.
company/at-a-glance
Product Philosophy
How Ignition Labs designs tools that feel calm, confident, and trustworthy.
company/product-philosophy
Guiding Principles
The core beliefs behind every product and engineering decision.
company/principles
Vision
Long-term direction for Ignition Labs and the Ignition Labs OS.
company/vision

Start here to understand the Rainy Day product from a high level, then move deeper into flows and implementation.

Rainy Day: Product Overview
What Rainy Day is, who it serves, and how it solves real financial stress.
apps/rainy-day/rainy-day.md
UX Flows
Core journeys: onboarding, weekly checkup, money timeline, and transaction review.
apps/rainy-day/ux-flows.md
UI Layout
A structural view of the app shell, navigation, and page hierarchy.
apps/rainy-day/ui-layout.md
MVP Implementation Plan
What gets built, in what order, and how it ships.
apps/rainy-day/mvp-plan.md
FCIB CSV Model Mapping
How bank CSV data is normalized into Rainy Day’s internal model.
apps/rainy-day/parsers/fcib-mapping.md

Reference these when building, reviewing, or planning work:

Engineering Process – cycles, branching, reviews, and releases
engineering/engineering-process
Contributing – expectations for code, docs, and collaboration
engineering/contributing
Tracking Work – how Linear and GitHub stay in sync
engineering/tracking
Issue Template – structure for defining new work
engineering/ISSUE_TEMPLATE
Tool Guides
- Linear: workflow & conventions
  engineering/tools/linear
- Obsidian: how we capture early thinking before promoting to docs
  engineering/tools/obsidian

This documentation should feel like a teammate: steady, dependable, and easy to navigate.

BuiltByGervonte • Ignition Labs