Marketplace Plugin

Adds production multi-tenant patterns to your Claude Code sessions. Install it once, then use natural language to adopt infrastructure, auth, design tokens, and deployment into your project.

Install

claude install-plugin syncupsuite/webplatform4sync

After installation, start a new Claude Code session. The plugin's skills are available immediately.

Source: syncupsuite/webplatform4sync on GitHub.

What It Does

Four skills handle the core concerns of a multi-tenant SaaS project:

Skill	What it does
multi-tenant-platform	3-tier tenant hierarchy, data isolation, governance
graduated-auth	Anonymous -> OAuth -> Full Account progression
neon-multi-tenant	Neon PostgreSQL schema, RLS, branch isolation, Drizzle ORM
theme-inspired-tokens	Culturally-grounded design token adoption

These are not templates that dump boilerplate into your project. They are AI-native instructions that read your codebase, understand your existing stack, and apply patterns where they fit. If you already have a Drizzle schema, the plugin extends it. If you already have auth, it wires into your existing setup.

Two Command Frames

The plugin ships two mental models over the same four skills. Every command in both frames routes to the same skill file. The difference is the lens -- how you think about when to reach for each skill and how they relate to each other.

Construction Frame

A building goes up in a fixed sequence. You cannot wire a house before you frame it.

site    ->  Ground cleared. Environment ready.
pour    ->  Foundation in. Platform core and data layer.
frame   ->  Skeleton up. Auth, API, and edge.
wire    ->  Systems connected. CI/CD, secrets, integrations.
finish  ->  Livable. Design, accessibility, shipping.

Activate it:

/webplatform4sync:site

Each stage gates the next. The plugin will note when you skip a dependency, but it will not block you.

Subcommands pass as arguments:

/webplatform4sync:site scaffold    # Set up project environment
/webplatform4sync:pour database    # Wire Neon + Drizzle + RLS
/webplatform4sync:frame auth       # Set up graduated auth
/webplatform4sync:wire ci          # Configure CI/CD pipeline
/webplatform4sync:finish theme     # Adopt a cultural identity

Best for: Greenfield projects where you want a clear sequence from ground zero to production. Solo developers who think in phases.

Shu-Ha-Ri Frame

Three stages of mastery, applied per concern. Your project can be Shu on auth and Ha on design at the same time.

Shu (follow)      ->  Adopt patterns without modification.
Ha  (break)       ->  Deviate intentionally. You understand the default.
Ri  (transcend)   ->  Operate the whole system. Compose. Publish.

Activate it:

/webplatform4sync:shu

Subcommands:

/webplatform4sync:shu scaffold     # Adopt the standard project structure
/webplatform4sync:shu auth         # Adopt default auth patterns
/webplatform4sync:ha auth          # Customize auth for your needs
/webplatform4sync:ri               # Full system operation mode

Best for: Teams with mixed experience levels. Existing projects where you are adopting patterns incrementally. When you want per-concern stage tracking instead of global phases.

Choosing a Frame

Situation	Frame
New project from scratch	Construction
Joining an existing project	Shu-Ha-Ri
Solo developer	Either works
Team with mixed skill levels	Shu-Ha-Ri
Want strict phase gates	Construction
Want per-concern flexibility	Shu-Ha-Ri
Start with one, switch later	Both -- no conflict

You can switch frames at any time. Progress is not lost. The underlying skills track their own state.

Natural Language Usage

You do not need to memorize commands. Once the plugin is installed, describe what you want in plain language:

I need to set up a Neon database with tenant isolation for my Vite + React project.

Add Google OAuth to my app. Users should start anonymous and upgrade when they're ready.

Apply a Japanese minimalist design identity to my project.

Claude maps your request to the relevant skill and applies it in context.

Reporting Issues

When a skill produces unexpected output -- wrong file paths, patterns that conflict with your stack, unclear instructions -- use the feedback command:

/webplatform4sync:feedback

This writes a structured report to .platform/feedback/ in your project. Include what you expected, what happened, and which skill was involved. These reports directly inform the next release.

You can also open an issue on GitHub.

Full Command Reference

For a complete listing of every command in both frames, including the side-by-side mapping table and walkthrough examples, see the Skills Reference.