[SYSTEM: SNAPNGO]
CLI to build modular systems: scaffold a spine, add microservices and micro-frontends, generate compose and env, bring the stack up. Faster path from zero to a known, runnable shape.
Portfolio deliverables
Business narrative
Time lost to snowflake stacks — value of scaffolding a known modular system.
Read case study ↓System design
Host, MFEs, gateway, service ownership, packages — topology the CLI generates and runs.
Open architecture →DX / modules
CLI commands, module contract, shared packages — day-one engineer surface.
Open developer →CLI / tooling extras
Case study · business narrative
Problem
Teams burn weeks hand-wiring compose files, env folklore, and service boilerplate for every new modular stack. Auth, gateway, and tenancy get reinvented per product instead of reused as a known shape.
Approach
- CLI surface: init spine, add modules, up, health.
- Generated spine with gateway, auth defaults, observability hooks, org tenancy shape.
- Modules for domain services and optional micro-frontends without rewriting the spine.
- Shared packages so contracts stay consistent across modules.
Shorter path from empty repo to a running modular system. Reusable chassis for multi-service products (e.g. TaxBox, Listia) without redoing platform decisions each time.
What shipped
Portfolio package: architecture white paper, developer surface, quick start, MMUI and modular-systems notes. Reference monorepos implement the chassis; public CLI packaging is open source direction.