| name | pre-deploy |
| version | 1.0.0 |
| description | Adapter-aware pre-deployment checklist for pracht apps targeting Node,
Cloudflare Workers, or Vercel. Catches the issues that only surface in the
production runtime: missing env vars, Node-only APIs in Cloudflare bundles,
ISG manifest absence, oversized edge bundles, missing wrangler/vercel config.
Use when asked to "pre-deploy check", "ready to ship?", "deployment
checklist", "is my build production-safe", or before running `wrangler
deploy` / `vercel deploy`.
|
| allowed-tools | ["Bash","Read","Grep","Glob"] |
Pracht Pre-Deploy
Run this before every production deploy. Each adapter has a different runtime
contract; this skill enforces the contract that matches your build.
Step 1: Detect the adapter
Read vite.config.ts and look for nodeAdapter(), cloudflareAdapter(), or
vercelAdapter(). Confirm with:
pracht inspect build --json
The target field is authoritative. If pracht build has not been run
recently, run it first:
pracht build
Step 2: Run framework-wide checks
pracht doctor --json
pracht verify --json
If the app uses generated typed routes (src/pracht-routes.ts or
src/pracht-routes.d.ts exists), also run:
pracht typegen --check
These catch app-graph wiring problems independent of the adapter. Resolve all
status: "error" entries before continuing.
Step 3: Adapter-specific checklist
Node (@pracht/adapter-node)
dist/server/server.js exists.dist/client/.vite/manifest.json exists.dist/server/isg-manifest.json exists if any route has render: "isg".- Smoke test:
pracht preview --skip-build (or node dist/server/server.js) boots and curl localhost:3000 returns 200.
- Required env vars (grep
process.env.* across src/) are set in the
deployment environment. List them for the user.
- Reverse-proxy / TLS termination configured (out of scope for this skill —
flag for confirmation).
Cloudflare Workers (@pracht/adapter-cloudflare)
wrangler.toml (or wrangler.jsonc) present at repo root.main points to dist/server/server.js.assets.directory points to dist/client.compatibility_date is set and recent.- Bindings declared in wrangler config for every
context.env.* access in
loaders, middleware, and API routes (grep, then cross-check).
- No Node-only APIs in the server bundle. Grep server files for:
fs,
path (Node form), process.cwd, Buffer, __dirname, __filename,
crypto.createHash (use crypto.subtle instead), child_process,
cluster, worker_threads. Flag each occurrence.
- ISG: if ISG routes exist, confirm Workers Caching is wired up on both
sides —
cloudflareAdapter({ cache: true }) in vite config and
"cache": { "enabled": true } in wrangler config. Without it, ISG pages
are static snapshots that never revalidate.
- When Workers Caching is enabled, flag ISG routes reachable through unbounded
query strings. Require a bounded allowlist/canonical redirect or an uncached
gateway with a normalized
cf.cacheKey; also check that markdown-capable
routes normalize Accept at the gateway when variant fan-out matters.
- Bundle size: report the size of
dist/server/server.js. Workers limit is
~1 MB compressed for free tier, ~10 MB on paid. Warn at 80% of the active
limit.
Vercel (@pracht/adapter-vercel)
.vercel/output/config.json exists post-build..vercel/output/functions/render.func/server.js exists..vercel/output/static/ populated.- Required env vars are configured in the Vercel project (cannot verify from
CLI without
vercel env pull — run that and diff against process.env.*
references).
- Edge runtime constraints: same Node-only API check as Cloudflare if the
function is configured for the edge runtime. Check
runtime in the
function's .vc-config.json.
- Build Output API v3 sanity:
config.json has version: 3.
Step 4: Cross-cutting checks
- Run
audit-secrets to confirm no process.env.* or context.env.* values
flow into loader return values.
- Run
audit-headers to confirm applyDefaultSecurityHeaders is in use on
user-facing responses (or that headers() exports cover the same ground).
- Confirm
git status is clean (deploying uncommitted work is a footgun).
Step 5: Report
Produce a checklist with pass/fail per item, grouped by Framework,
Adapter, Cross-cutting. End with a one-line verdict: READY /
BLOCKED (N errors) / READY WITH WARNINGS (N warnings).
Rules
- Always run
pracht build first. Do not lint a stale dist/.
- Detect the adapter — never assume.
- For Cloudflare/Vercel-edge, the Node-only API check is non-negotiable; a
single
Buffer reference will crash the worker on a code path that may
never hit in dev.
- If the app does not use generated typed route files yet, note that
pracht typegen --check is optional; if it does, stale generated files block deployment.
- Do not deploy on the user's behalf. End the skill at the verdict.
- If
pracht doctor reports errors, do not run any other checks until those
are resolved — they will produce noisy false positives.
$ARGUMENTS
