Prod Forge frontend: React web client, Expo mobile client and design system with production-grade quality gates

★ 326⑂ 29👁 10⑃ 3● 18▤ 2
TypeScriptMITCreated 2026-05-05
Download: Release 1.1.0Release-1.1.0 ↓1.1.02026-11-09
+0
Daily
326
stars
29
forks
10
watchers
3
prs
18
issues
2
releases

README

_AI made writing the code easy. Running it in production is still hard._

This repository holds the web and mobile clients in one NX monorepo, with a shared design system. It answers: how do I build, ship, and keep web and mobile clients healthy?

Part of Prod Forge — start with the organization overview: https://github.com/prod-forge

 Stack


| Layer          | Tools                                            |
| -------------- | ------------------------------------------------ |
| Web Client     | React · Vite · Redux Toolkit · Tailwind CSS · NX |
| Mobile Client  | Expo · React Native · Redux Toolkit              |
| Quality        | ESLint · Prettier · Husky · Commitlint · CI/CD   |

The full stack table is on the organization page: https://github.com/prod-forge

 Getting started

Requires Node 24 and the backend API running (see the backend guide).

shell
npm ci
cp .env.example .env    VITE_API_BASE_URL is required for a build (absolute URL ending with "/"); dev falls back to the /api/v1/ proxy
npm run dev             web client
cp apps/mobile-client/.env.example apps/mobile-client/.env    EXPO_PUBLIC_API_BASE_URL, mobile client only
npm run dev:mobile      mobile client (Expo)


 Table of contents

- 1. Repository Strategy
  - Why Frontend Projects Use a Monorepo
  - What Gets Shared Across Clients
  - What Belongs in a Frontend Monorepo
  - Structure
  - Package Scope
  - Path Aliases



- 2. Architecture Decisions
  - Choosing the Right Architecture
  - Frontend Architecture
    - Feature Sliced Design
    - Feature-based Approach



- 3. Development Workflow
  - NX-Aware Development
  - Visual Snapshots in a Pull Request
  - Storybook in Review
  - Checks Before You Push
  - Documentation Is Part of the Change



- 4. AI-Assisted Development
  - Quality Gates First
  - Architecture Before Generation
  - Workflow
    - Context Belongs to the Repository
    - What Goes into AGENTS.md
    - The docs/ Folder
    - Tune Your Harness
    - Superpowers
  - Pre-Hooks
  - Task Decomposition
    - 1. State the Task at a High Level
    - 2. Let the Agent Write the Plan
    - 3. Answer the Questions
    - 4. Validate and Approve
    - 5. Close with Conclusions
  - Legacy Projects
  - Common AI Problems
  - Cost Optimization
  - Quality Control
    - Commit Frequently
    - Validate Edge Cases
    - Mandatory Code Review
    - Never Trust AI Blindly
  - Recommended Workflow



- 5. Code Quality
  - Layer 1. Formatting
  - Layer 2. Static Analysis
  - Layer 3. Pre-commit and Pre-push
  - Layer 4. Commitlint
  - Layer 5. Continuous Integration
  - Layer 6. Dependency Locking



- 6. Styles Management
  - Design Tokens
  - Tailwind CSS
  - Why Accessibility Is in the Pipeline



- 7. Assets Management
  - When this Matters
  - How it Works
  - Local Development
  - What Belongs in Assets



- 8. Design System
  - What a Design System Is Here
  - Token Pipeline
    - Why Generated Files Are Committed
    - How to Add a Token
  - Theming
    - Mobile
  -

Top issues

Latest release

Release 1.1.0 v1.1.0 2026-11-09
1.1.0 (2026-11-09)

 Bug Fixes

 a11y: put the visible text into the names of Prev and the status toggle (0c3e88a)
 ci: sync assets under the assets/ prefix that CloudFront reads (6173931)
 make the Claude deny hooks actually deny (8925e32)
 mobile-client: install the @sentry/react-native version Expo SDK 58 expects (69bf7b1)
 mobile-client: keep sendDefaultPii explicit under the Sentry 8.28 types (c8806c4)
 paste over-limit descriptions in ui-web tests instead of typing them (89fce8b)
 ui-web: drop aria-pressed from the status toggle whose name changes (d3dc9a0)
 ui-web: remove the

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON