Stats
Actions
Tags
From supabase-pack
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".
How this skill is triggered — by the user, by Claude, or both
Slash command
/supabase-pack:supabase-architecture-variantsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Understanding of team size and DAU requirements
Use the decision matrix to identify appropriate variant.
Select Monolith, Service Layer, or Microservice based on needs.
Set up project layout following the chosen blueprint.
Document upgrade path for future scaling.
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Execute choose and implement Supabase validated architecture blueprints for different scales.
npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin supabase-packImplements enterprise Supabase architectures: monorepo layout, multi-tenant RLS, microservices cross-project access, Next.js/SvelteKit integration, edge functions, caching, queues, audit logging.
Guides system architecture design including patterns like monolith/microservices, database selection favoring Postgres/Redis, tech stack choices, TypeScript/Next.js project structure, API design, and caching strategies for scale.
Designs system architecture for tech stack, API contracts, data models, and infrastructure shape. Supports brownfield extensions and engagement modes from Express to Meticulous.