What problem does it solve? Setting up a branded admin panel for each new client normally means rebuilding authentication, layout, theming, and module wiring from scratch. This Skill codifies a reusable, config-zero admin architecture so a new tenant's panel is provisioned with only a brand-bridge CSS file and a modules registry. ## Core Features & Use Cases - New tenant provisioning: Step-by-step checklist for installing the client-admin SDK, writing brand-bridge.css, creating AuthShell and modules.ts, setting Vercel env vars, and whitelisting operators in the app_admins table. - Module extension: A repeatable pattern for adding modules (e.g., bookings) via a page wrapped in AuthShell plus an entry in the MODULES registry and optional proxy API handlers. - Brand token mapping: Defines the four critical layering variables (--admin-surface, --admin-bg, --admin-surface-2, --admin-bg-deep) plus text, border, and CTA tokens, with a visual smoke test and a list of vetoed anti-patterns (no gradients, no rounded active nav buttons). - Use Case: A new client signs up; you insert their tenant_branding row, copy the SDK, map their brand palette to the admin tokens, and their panel at /admin is live with magic-link auth against admin.ebecerra.es. ## Quick Start Provision an admin panel for a new client by following the tenant provisioning checklist, starting with the tenant_branding seed row and the brand-bridge.css token mapping.