supabase-architecture-variants
Execute choose and implement Supabase validated architecture blueprints for different scales. Use when designing new Supabase integrations, choosing between monolith/service/microservice architectures, or planning migration paths for Supabase applications. Trigger with phrases like "supabase architecture", "supabase blueprint", "how to structure supabase", "supabase project layout", "supabase microservice". allowed-tools: Read, Grep version: 1.0.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed Tools
No tools specified
Provided by Plugin
supabase-pack
Claude Code skill pack for Supabase (30 skills)
Installation
This skill is included in the supabase-pack plugin:
/plugin install supabase-pack@claude-code-plugins-plusClick to copy
Instructions
# 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.
## Resources
- [Monolith First](https://martinfowler.com/bliki/MonolithFirst.html)
- [Microservices Guide](https://martinfowler.com/microservices/)
- [Supabase Architecture Guide](https://supabase.com/docs/architecture)