frontmcp-production-readiness

name	frontmcp-production-readiness
description	Pre-production audit, hardening, and go-live checklists for FrontMCP servers. Use before shipping to verify security hardening, performance, reliability, and observability, and for target-specific production checklists: Node server (Docker, graceful shutdown, Redis session scaling), Vercel and edge (cold-start, stateless design), AWS Lambda (cold start, scaling, monitoring), Cloudflare Workers (KV, Durable Objects, runtime limits), CLI binary and local daemon (stdio and socket transport), browser SDK bundle, and embedded npm SDK. Also configuring /healthz and /readyz health and readiness endpoints with custom probes, and distributed high-availability (multi-pod heartbeat, session takeover, notification relay). Triggers: production ready, security audit, hardening, performance check, production checklist, go live, pre-launch review.
tags	["production","security","performance","reliability","observability","audit","best-practices"]
category	production
targets	["all"]
bundle	["recommended","full"]
priority	10
visibility	both
license	Apache-2.0
metadata	{"docs":"https://docs.agentfront.dev/frontmcp/deployment/production-build"}

FrontMCP Production Readiness Audit

Router for production readiness checklists. Start with the common checklist (security, performance, reliability, observability), then follow the target-specific checklist for your deployment environment.

When to Use This Skill

Must Use

• Before deploying a FrontMCP server to production for the first time
• After major feature additions or architectural changes
• During security reviews or compliance audits

Recommended

• As part of PR reviews for infrastructure-touching changes
• Quarterly health checks on production deployments
• When switching deployment targets

Skip When

• Building a prototype or proof-of-concept
• Running in development/local mode only

Decision: Use this skill when preparing for production. Start with common-checklist, then pick your deployment target.

Prerequisites

• A deployable FrontMCP project (build target chosen, see frontmcp-deployment).
• Observability and structured logging available (see frontmcp-observability) — production hardening assumes you can see what the server is doing.
• A staging environment matching production target (Node, Vercel, Lambda, Cloudflare, CLI, browser) to validate the checklist before go-live.

Steps

Step 1: Detect Deployment Target

Check the project to determine the deployment target:

1. Look at package.json scripts for frontmcp build --target <target>
2. Check for target-specific files: ci/Dockerfile (node), vercel.json (vercel), wrangler.toml (cloudflare), ci/template.yaml (lambda)
3. Check if the build target is cli or browser in the build config
4. If unclear, ask the user which environment they're deploying to

Step 2: Run Common Checklist

Always start with the common checklist — it covers security, performance, reliability, and observability that apply to every target.

Step 3: Run Target-Specific Checklist

After the common checklist, run the checklist for your deployment target.

Scenario Routing Table