new-client-site

Orchestrate multi-tenant client site provisioning across backend, messaging, and frontend deployment.

1|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/MikeyMiami/lovable-web-design --skill new-client-site
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-client-site
Source: https://github.com/MikeyMiami/lovable-web-design/tree/main/skills/new-client-site
Command: npx skills add https://github.com/MikeyMiami/lovable-web-design --skill new-client-site

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the complexity of manually provisioning new clients by acting as a central orchestrator that sequences backend configuration, messaging provider setup, and frontend deployment.

Core Features & Use Cases

  • Automated Provisioning: Sequences the creation of client rows, settings, and messaging subaccounts on the shared backend.
  • Frontend Orchestration: Automates the Remixing of marketing sites and design layer application to ensure brand consistency.
  • Launch Verification: Executes a standardized gate check to ensure all compliance, A2P registration, and functional requirements are met before go-live.

Quick Start

Use the new-client-site skill to initiate the launch sequence for a new client after their onboarding data has been captured.

Frequently Asked Questions about new-client-site

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

FAQPage Schema
How do I automate multi-tenant provisioning for new client sites?

Multi-tenant provisioning is automated by sequencing backend configuration, messaging provider registration, and frontend deployment. This central orchestration ensures system integrity by strictly applying onboarding data capture, A2P compliance, and design layer application.

What is the required sequence for launching a new client site on shared infrastructure?

The required launch sequence starts with onboarding data capture, proceeds through backend configuration and messaging provider registration, applies the frontend design layer, and finishes with a standardized gate check verifying A2P compliance and functional requirements.

How do I verify A2P compliance and functional requirements before a client site goes live?

A2P compliance and functional requirements are verified by executing a standardized launch gate check. This check ensures all compliance, A2P registration, and functional prerequisites are fully met before the multi-tenant site goes live.

Can I use orchestration to automate frontend deployment and brand consistency for multiple clients?

Yes, frontend orchestration automates the Remixing of marketing sites and design layer application. This ensures brand consistency across multiple clients while maintaining the strict sequence required for multi-tenant provisioning on a shared backend.

What happens if I skip the onboarding data capture step in the deployment orchestration sequence?

Skipping the onboarding data capture step breaks the strict sequence required for system integrity. The orchestration process requires this data before backend configuration, messaging subaccount creation, and A2P compliance registration can safely proceed.