ridendine-modular-architecture

Explain RidenDine's modular monorepo architecture with pnpm workspaces and independent deployments.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Ritenoob/ridedine --skill ridendine-modular-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ridendine-modular-architecture
Source: https://github.com/Ritenoob/ridedine/tree/main/.claude/skills/ridendine-modular-architecture
Command: npx skills add https://github.com/Ritenoob/ridedine --skill ridendine-modular-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you understand and work with RidenDine's complex modular monorepo architecture, enabling efficient development and deployment of its distinct applications.

Core Features & Use Cases

  • Monorepo Structure Understanding: Clarifies the organization of apps, packages, and backend components.
  • Package Management: Explains how pnpm workspaces manage shared code (@home-chef/shared, @home-chef/data).
  • Independent Deployment: Details how Admin, Web, and Mobile apps are deployed separately.
  • Adding New Apps: Provides a step-by-step guide for integrating new applications into the monorepo.
  • Use Case: You're a new developer on the RidenDine project and need to understand where to find the customer-facing web app code, how it shares types with the admin dashboard, and how to deploy a small fix to it without affecting the mobile app.

Quick Start

Use the ridendine-modular-architecture skill to understand how the admin, web, and mobile applications are structured and deployed independently within the monorepo.

Frequently Asked Questions about ridendine-modular-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure independent Next.js and Expo apps in a pnpm monorepo?

Structure a pnpm monorepo by placing independent Admin, Web, and Mobile applications in an apps directory, using workspaces to manage shared packages like @home-chef/shared and @home-chef/data across the distinct applications.

How do I deploy a Next.js web app independently without affecting the Expo mobile app?

Deploy applications independently by targeting specific apps within the monorepo, using Vercel for the Next.js web and admin apps and EAS for the Expo mobile app, ensuring updates to one platform do not affect the others.

Can I share database types between Admin and Web apps using Supabase in a monorepo?

Yes, you can share database types and backend integration logic by centralizing Supabase code within shared workspace packages, allowing both Admin and Web apps to import and utilize the same data structures.

What is the best way to add a new application to an existing pnpm monorepo?

Add a new application by creating a new directory within the apps folder, configuring its package.json, and updating the pnpm workspace configuration to recognize and link the new application with existing shared packages.

Does RidenDine's modular architecture support separate deployment strategies for web and mobile?

Yes, the modular architecture explicitly supports separate deployment strategies, utilizing Vercel for independent Next.js web deployments and EAS for Expo mobile deployments, allowing isolated CI/CD pipelines for each application.

Why use pnpm workspaces for a modular monorepo with shared packages?

Use pnpm workspaces to efficiently manage dependencies and link shared packages like @home-chef/shared across multiple independent applications, preventing version conflicts and reducing duplication within the monorepo.