supabase-architecture-variants
Choose and implement Supabase validated architecture blueprints for different scales.Use when designing new Supabase integrations, choosing between monolith/service/microservicearchitectures, or planning migration paths for Supabase applications.Trigger with phrases like "supabase architecture", "supabase blueprint","how to structure supabase", "supabase project layout", "supabase microservice".
When & Why to Use This Skill
This Claude skill provides expert guidance on selecting and implementing validated Supabase architecture blueprints tailored to different project scales. It streamlines the decision-making process between monolith, service layer, and microservice architectures, ensuring your Supabase applications are built for scalability, maintainability, and optimal performance from the start.
Use Cases
- New Project Scaffolding: Use the skill to automatically determine and implement the ideal project layout for new Supabase integrations based on team size and growth projections.
- Scaling Strategy: Transition existing Supabase applications from a simple monolith to a more complex service-oriented or microservice architecture as user demand increases.
- Migration Path Planning: Document and execute clear upgrade paths for legacy Supabase projects to align with modern architectural standards and patterns.
- Infrastructure Assessment: Evaluate current deployment requirements against SLA and DAU targets to select the most cost-effective and performant architecture variant.
| name | supabase-architecture-variants |
|---|---|
| description | | |
| allowed-tools | Read, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Supabase Architecture Variants
Prerequisites
- Understanding of team size and DAU requirements
- Knowledge of deployment infrastructure
- Clear SLA requirements
- Growth projections available
Instructions
Step 1: Assess Requirements
Use the decision matrix to identify appropriate variant.
Step 2: Choose Architecture
Select Monolith, Service Layer, or Microservice based on needs.
Step 3: Implement Structure
Set up project layout following the chosen blueprint.
Step 4: Plan Migration Path
Document upgrade path for future scaling.
Output
- Architecture variant selected
- Project structure implemented
- Migration path documented
- Appropriate patterns applied
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.