Deploy a crouton app to Cloudflare Workers PRODUCTION (<app>.friendlyinter.net). A deliberate, human-initiated action — separate from the default staging /deploy skill. Use ONLY when explicitly asked to ship/release to production. Never run as part of routine work or an automated flow.
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
The only place a crouton app ships to production. Everything routine goes to
staging via the /deploy skill; production is split out here so it can never
happen by accident or as a side effect of an agent flow.
🛑 Gate — run this skill ONLY on an explicit human request to deploy to production ("ship X to prod", "release to production", "promote to prod"). If the ask is just "deploy", that means staging → use
/deploy. Before running anything, confirm: (1) which app, and (2) that production is genuinely intended. When in doubt, ask.
| Env | wrangler env | Worker | Domain | Script |
|---|---|---|---|---|
| production | top-level | <app> | <app>.friendlyinter.net | cf:deploy |
(Staging — env.staging / <app>.pmcp.dev / cf:staging — is not here; that's /deploy.)
main redeploys it), see the smoke go green, re-dispatch. Genuine emergency with
staging itself down → re-dispatch with skip_staging_smoke=true (loud warning on
the run; never routine). The gate applies to the CI path — a local cf:deploy
bypasses it, so hold yourself to the same bar there./deploy Step 2 (the shared mechanics live
in that skill; don't duplicate them).BETTER_AUTH_SECRET, BETTER_AUTH_URL = the
production domain (https://<app>.friendlyinter.net), NUXT_*. Worker secrets
persist across deploys, so this is a one-time bootstrap per worker:
npx wrangler secret bulk secrets.json (no --env = production).CLOUDFLARE_ACCOUNT_ID + CLOUDFLARE_API_TOKEN present (see /deploy → Credentials).workflow_dispatch) with environment = production. Push/PR never deploys prod —
only this manual dispatch does.cd apps/{app}
pnpm cf:deploy # build → wrangler deploy (auto-provision) → sync:ids → d1 migrations apply --remote
# first bootstrap only — commit the written-back ids:
git add apps/{app}/wrangler.jsonc && git commit -m "chore({app}): commit provisioned prod D1/KV ids"
Sandbox / no Cloudflare egress: you CANNOT run a production deploy. Prepare and verify the config, then hand the
workflow_dispatch(orcf:deploy) to the user to run, and confirm the result with them.
<app>.friendlyinter.net is live and the remote migration applied.--with-staff) is a
staging/local-only login and must never run against the prod DB.Pipeline scripts, auto-provisioning, Pages→Workers migration, credentials, and
troubleshooting are documented once in the /deploy skill. This skill only adds the
production trigger and its human gate.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Accessibility review for Vue surfaces — the code-cleaning analog of /code-review and /simplify, pointed at WCAG/ARIA. Reviews just your diff (or a package/file), rates findings by severity, and either comments inline on the PR (--comment) or applies the safe fixes for you (--fix). Steers the depth-aware `a11y` subagent. Use when asked to "check accessibility", "a11y this", "audit ARIA/keyboard", or run /a11y.
中文简介正在准备中。当前显示原文说明。
Emit a blocking question the owner can read in ~10 seconds and answer in one reply — the scannable, recommendation-first handoff every agent posts when it hits a fork it can't own. Leads with the one decision + a recommendation, carries the 🤖 provenance header, doubles as the
中文简介正在准备中。当前显示原文说明。
Audit packages for documentation completeness, detect drift between code and docs, and maintain documentation quality across the monorepo. Use when checking package docs, running audits, or reviewing documentation health.
中文简介正在准备中。当前显示原文说明。
Author a placeable layout block that looks right at ANY pane size. The one hard rule — size to the PANE with container queries (@container), never the viewport — plus list/form playbooks and the sizing contract (minWidth etc.) the viability metric reads. Use when adding/converting a croutonLayoutBlocks block, or when a block overflows/breaks in a narrow pane.
中文简介正在准备中。当前显示原文说明。
When a bug or regression is reported, the FIRST step — before fixing — is to research how and when it was introduced (git archaeology), then record that finding on the tracking issue/PR. Use the moment a bug, error, broken build, or "this used to work" is reported, before writing a fix. Produces a first-bad-commit (or "not a code regression") note you paste onto the issue.
中文简介正在准备中。当前显示原文说明。
Smart, granular git commits following monorepo conventions. Analyzes changes, filters to session-relevant files, groups by intent, and uses conventional commit format. Use when committing code changes.
中文简介正在准备中。当前显示原文说明。