greenroom-architecture

Provide architecture guidance for scalable Remix applications with route and service conventions.

Updated Feb 27, 2026

Search Tags:#architecture #onboarding #scalability #patterns #remix #service-layer #route-structure

Ready to run

npx skills add https://github.com/TylerLeonhardt/greenroom --skill greenroom-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: greenroom-architecture
Source: https://github.com/TylerLeonhardt/greenroom/tree/main/.github/skills/greenroom-architecture
Command: npx skills add https://github.com/TylerLeonhardt/greenroom --skill greenroom-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, reusable blueprint for structuring Remix routes, layouts, and service layers in the My Call Time application, reducing onboarding time and ensuring consistency across features.

Core Features & Use Cases

Remix route structure conventions for flat file routing in Remix v2 with Vite.
Service layer pattern with .server.ts suffix to separate server-side logic from client bundle.
Centralized architecture conventions for groups, availability, events, and authentication workflows.
Example-driven guidelines to maintain code quality and onboarding consistency across teams.

Quick Start

Apply the route-structure and service-layer conventions when adding a new feature to the app.

Frequently Asked Questions about greenroom-architecture

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

FAQPage Schema

How do I structure routes in a Remix v2 application to improve onboarding?▼

To improve onboarding in a Remix v2 application, structure routes using flat file routing conventions. This provides a clear, reusable blueprint that standardizes layouts and route patterns across features, reducing ramp-up time for new developers.

What is the best way to separate server-side logic from the client bundle in Remix?▼

The best way to separate server-side logic from the client bundle in Remix is using a service layer pattern with a .server.ts suffix. This enforces conventions that ensure maintainability and safety by keeping server-only services isolated.

How do I standardize loader and action patterns for authentication workflows in Remix?▼

Standardize loader and action patterns for authentication workflows by applying centralized architecture conventions. This enforces safe route structures and service layer rules across groups, availability, and events to ensure consistent authentication handling.

Does this architecture pattern work with Vite and Remix v2 flat file routing?▼

Yes, this architecture pattern works with Vite and Remix v2 flat file routing. It provides example-driven guidelines specifically tailored to these technologies to maintain code quality and onboarding consistency across teams.

How do I scale a Remix application across multiple developer groups?▼

Scale a Remix application across multiple developer groups by implementing centralized architecture conventions for route structure and server-only services. This standardizes patterns for features like availability and events, ensuring maintainability as the team grows.