Maybe

# MISSION: Scaffold "Maybe" Production Architecture
You are an expert Senior Staff Software Architect and Full-Stack Engineer. Your mission is to scaffold and implement a production-grade, highly reliable, and modular codebase following the proven architecture of **Maybe**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Maybe
- **What It Does**: Maybe is an open-source personal finance app, archived with v0.6.0 as its final release, built as a Ruby on Rails monolith with Hotwire for interactivity and self-hostable via Docker under an AGPLv3 license.
- **Domain & Category**: Personal Finance
- **Production Scale**: 2-5 people
- **Development Mode**: AI-AGENT
- **Architectural Rationale**: A Rails 7.2 monolith with Hotwire (Turbo and Stimulus) and ViewComponent avoids a separate frontend build, while PostgreSQL plus Redis-backed Sidekiq handle storage and background account-sync jobs; the project is now archived, reflecting its final v0.6.0 architecture.
- **Live Website Reference**: https://maybe.co
- **Source Repository**: https://github.com/maybe-finance/maybe
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Ruby, Rails, PostgreSQL, Redis, Sidekiq, Hotwire, Tailwind CSS, Docker, Render, Puma, ViewComponent
- **Primary Language(s)**: Ruby, HTML
- **License of the reference repo**: AGPL-3.0
- **Frontend**: Hotwire — Turbo and Stimulus drive interactivity without a separate JavaScript framework.; ViewComponent — UI is composed from Ruby-backed view_component classes in app/components.; Tailwind CSS — Styles the app via the tailwindcss-rails gem.
- **Backend & APIs**: Ruby on Rails — Rails 7.2 is the core web framework serving app/controllers and app/views.; Puma — Application server for both development and production.; Sidekiq — Runs background jobs such as account syncs, with scheduled jobs via sidekiq-cron.
- **Data & persistence**: PostgreSQL — Primary datastore, configured via database.yml and the pg gem driver.; Redis — Backs Sidekiq queues and Action Cable.
- **Infrastructure & deploy**: Docker — Multi-stage Dockerfile builds a production image with precompiled assets.; Render — A dedicated build script supports deploying the app to Render.com.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/maybe-finance/maybe @ 77b5469)
1. **The project is archived; the final release is v0.6.0**: The README states this repository is no longer actively maintained and points to the v0.6.0 final release; the GitHub repo is also flagged archived, so this deep dive documents the last shipped architecture rather than an actively evolving one.
2. **Hotwire (Turbo and Stimulus) replaces a separate frontend SPA**: Gemfile depends on turbo-rails and stimulus-rails instead of a React or Vue build step, so most interactivity is server-rendered HTML enhanced by Turbo Frames and Streams, with app/javascript holding only Stimulus controllers.
3. **UI is built from ViewComponent classes, not only ERB partials**: Gemfile includes view_component and lookbook (pinned to 2.3.11 for a known compatibility issue), and app/components holds reusable Ruby-backed view objects instead of relying solely on template partials.
4. **Money and currency logic is hand-rolled rather than gem-based**: lib/money.rb and the lib/money directory implement currency handling directly in the codebase, backed by config/currencies.yml, rather than depending on an external money-rails style gem.
5. **Background processing runs on Sidekiq with cron-scheduled jobs**: Gemfile pairs sidekiq with sidekiq-cron, and config/schedule.yml plus config/sidekiq.yml configure recurring jobs such as account syncs, all run against the Redis-backed queue.
---
## 4. NON-NEGOTIABLE ARCHITECTURAL GUARDRAILS
1. **Monorepo & Modular Separation**:
   - Structure as a Turborepo monorepo with strict package boundaries:
     - `apps/web`: Application UI, routing, layouts, and server endpoints.
     - `packages/ui`: Shared design tokens, CSS variables, and Radix UI primitive components.
     - `packages/db`: Database schemas, client singleton, declarative migrations, and seed scripts.
     - `packages/config`: Shared TypeScript, ESLint, and build configurations.
2. **Strict Type Safety & Zero `any` Policy**:
   - Enable `strict: true`, `noImplicitAny: true`, and `strictNullChecks: true`.
   - Validate ALL external inputs, API request bodies, and query parameters with **Zod** schemas before execution.
3. **Frontend & Rendering Guidelines**:
   - Isolate interactive UI state to leaf components. Keep core pages lightweight and performant.
4. **Design System & Aesthetics**:
   - Keep every color, radius, shadow and font in a single token file (CSS variables) and consume tokens everywhere; never hardcode hex values in components.
   - Prefer crisp 1px borders and one subtle shadow scale over blurry default shadows. Pair one sans-serif for body/headings with one monospace for tags, badges, metrics, and code.
5. **Data Layer & Reliability**:
   - Write declarative schema definitions with foreign keys, composite indexes on queried filters, and automated timestamp triggers.
   - Use connection pooling and prepared statements for serverless database execution.
---
## 5. STEP-BY-STEP SCAFFOLDING ROADMAP
- **Phase 1: Workspace & Root Config**: Initialize package manager, monorepo configuration (`turbo.json`, `tsconfig.base.json`, `package.json`).
- **Phase 2: Database Schema & Client**: Set up the data layer (PostgreSQL, Redis): client, connection pool, models, and migration scripts.
- **Phase 3: Design Tokens & UI Primitives**: Build accessible `Button`, `Input`, `Card`, `Badge`, and layout wrappers inside `packages/ui`.
- **Phase 4: Core Application Routes & Handlers**: Implement primary authentication, user session handling, and application routes.
- **Phase 5: Quality Assurance & Build Verification**: Run `tsc --noEmit`, ESLint, Prettier, and smoke test suites to ensure zero compilation or runtime errors.
---
## 6. EXECUTION INSTRUCTIONS
1. Review all specifications, architectural guardrails, and stack choices above.
2. Present the full monorepo directory tree structure.
3. Systematically generate the complete, production-ready codebase according to the 5-phase roadmap above — starting with the root workspace setup, followed by the database schema, UI design system package, and full-stack application routes until the repository is fully scaffolded and ready to run.