multi-institution-manager

Manage six JKKN institutions from one codebase with Supabase and Vercel deployments.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/JKKN-Institutions/jkkn-cas-website --skill multi-institution-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-institution-manager
Source: https://github.com/JKKN-Institutions/jkkn-cas-website/tree/main/.claude/skills/multi-institution-manager
Command: npx skills add https://github.com/JKKN-Institutions/jkkn-cas-website --skill multi-institution-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive guide for managing the JKKN multi-institution architecture within a single codebase, enabling one codebase to serve six distinct websites with isolated deployments, configs, and data boundaries.

Core Features & Use Cases

  • Institution-specific MCP tooling for each Supabase project and per-institution deployment workflows.
  • Centralized migration documentation, SRMD architecture clarity, and cross-institution sync processes.
  • Local development switcher, registry updates, and comprehensive troubleshooting guidance to onboard new institutions efficiently.

Quick Start

Switch to the target institution in the local dev environment and apply the core migrations using MCP to initialize its backend.

Frequently Asked Questions about multi-institution-manager

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

FAQPage Schema
How do I manage multi-tenant deployments for multiple institutions from a single codebase?

Manage multi-tenant deployments by orchestrating a unified platform from a single codebase, applying per-institution deployment workflows, environment configurations, and domain routing across Supabase and Vercel to ensure tenant isolation.

Can I isolate Supabase databases and Vercel deployments for each tenant in a multi-institution setup?

Yes, you can isolate Supabase databases and Vercel deployments by applying institution-specific MCP tooling and per-institution provisioning workflows that maintain strict data boundaries and configuration parity across all six institutions.

How do I switch local development environments between different institutions?

Switch local development environments by using a local development switcher tool that targets the specific institution, allowing you to apply core migrations using MCP and initialize its backend before deployment.

What is the best way to handle database migrations across multiple Supabase projects?

Handle database migrations across Supabase projects by using centralized migration documentation and per-institution MCP tooling to apply schema changes, ensuring cross-institution sync processes maintain architectural clarity and data parity.

Does multi-institution provisioning work with Vercel domain routing and Supabase backend configurations?

Multi-institution provisioning works with Vercel and Supabase by handling environment configuration, domain routing, and deployment workflows, ensuring each institution operates with isolated configs and data boundaries from one codebase.

Why does a multi-institution platform need centralized migration documentation and registry updates?

A multi-institution platform needs centralized migration documentation and registry updates to ensure architectural clarity, streamline cross-institution sync processes, and provide comprehensive troubleshooting guidance for onboarding new institutions efficiently.