Client Project Setup

The Claude Code skill (recommended)

If you have the mg-pm-ops plugin installed, invoke:

/mg-ops-client-infrastructure CAST_0026

It asks for:

Project code (e.g. CAST_0026). Must include the suffix.
Display name (e.g. Community Arts Stabilization Trust).
Firefly x Mangrove? Determines branding and GitHub team access.
Project type: project (default) or proposal.
Collaborators: GitHub usernames for push access.

The skill handles: local folder creation, GitHub repo, overview templates, design system, and initial publish. It reports what it built and what needs a human.

For proposals specifically

Use /mg-ops-new-client-proposal instead. It calls the infrastructure skill first, then layers on voice guides, RFP intake, and compliance checks.

What needs Maiya (Cloudflare access):

Git-connect (push-to-deploy): Dashboard > Pages > project > Settings > Builds & deployments > Connect to Git. Build output directory: published. Once connected, git push = deployed.
Custom domain DNS (if the client wants project.clientdomain.com instead of pages.dev).
First publish if wrangler isn't set up on your machine. After git-connect this is no longer needed.

Everything else the skill does automatically.

Folder structure

~/Dev/_Clients/
  mg-client-CAST Community Arts .../   ← plain folder (not git)
    project-CAST_0026/                 ← git repo
      published/
        <client-token>/        ← client-facing (shared via URL)
        internal/<team-token>/ ← team-only (separate URL, no password)
      working/                 ← never served

Client-level folder = plain directory, named with the display name for scannability.
Project subfolder = git repo, named with project code and type prefix.
project- = ongoing client work. proposal- = bids.
Firefly x Mangrove clients use mg-ff-client- prefix on the folder.

Client project setup

The Claude Code skill (recommended)

For proposals specifically

Folder structure

Design templates

Related docs