[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76SPB57PZCXYZSDYY3K45TM":3,"skill-same:01M76SPB57PZCXYZSDYY3K45TM":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M76SPB57PZCXYZSDYY3K45TM","setup-stripe",null,"Strict NowStack Stripe setup: collect Stripe API keys, store secrets in Convex env, collect billing plans and prices, create Stripe products\u002Fprices, update billing code, verify","zuzu59\u002Fz-skills","zuzu59","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15345233?v=4","01M756RFXRYFCM8DCAHTP0F5YW","Christian Zufferey","01M756RFYZRYH7F070CKQRMW38",0,"MIT","https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: setup-stripe\ndescription: \"Strict NowStack Stripe setup: collect Stripe API keys, store secrets in Convex env, collect billing plans and prices, create Stripe products\u002Fprices, update billing code, verify\"\nargument-hint: \"[test|live]\"\n---\n\n# Setup Stripe - Strict NowStack Billing Setup\n\n\u003Cobjective>\nConfigure Stripe billing for a NowStack app in one strict order: verify the local Convex setup, collect Stripe API keys, write secrets to Convex env, collect the desired plans and prices, update the billing code, create products and recurring prices directly in the user's Stripe account from `convex\u002Fbilling\u002Fplans.ts`, then validate.\n\u003C\u002Fobjective>\n\n\u003Cstrict_order>\nThis workflow MUST follow this order exactly. Do not reorder, merge, or skip steps unless the user explicitly asks to stop or skip the current step.\n\n1. Preflight: verify Convex config, required files, Stripe SDK availability, and current billing plan shape.\n2. API keys: collect `STRIPE_SECRET_KEY`, set it in Convex env, then run the existing webhook helper to create\u002Fupdate the Convex Stripe webhook and set `STRIPE_WEBHOOK_SECRET`.\n3. Plans and prices: ask for the full plan matrix in one structured response.\n4. Code update: update `convex\u002Fbilling\u002Fplans.ts` and UI-only plan features in `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts`.\n5. Stripe creation: create or reuse Stripe Products and recurring Prices in the user's Stripe account from `convex\u002Fbilling\u002Fplans.ts`, then write the resulting Price IDs into Convex env.\n6. Finish: validate, update `CHANGELOG.md`, clean temporary files, and summarize.\n\u003C\u002Fstrict_order>\n\n\u003Cinteraction_rules>\n- Never ask for secrets and plan details in the same message.\n- Never write Stripe secrets to `.env`, `.env.local`, Vercel env, `CHANGELOG.md`, or any git-tracked file.\n- Do not print full secret values. Mask them as `sk_test_...1234` \u002F `sk_live_...1234`.\n- Use `request_user_input` when available and allowed for checkpoint choices. Plain text is the fallback.\n- Keep the user's language for prompts and summaries.\n- If the user provides a publishable key, only record whether it was provided. Do not store it unless the codebase actually needs `VITE_STRIPE_PUBLISHABLE_KEY`.\n\u003C\u002Finteraction_rules>\n\n\u003Chard_execution_contract>\nThe agent MUST treat this workflow as a gated state machine, not loose guidance.\n\nBefore every step, write a compact state summary:\n\n```text\nSTRIPE STATE: step={current_step}; waiting_for={none|api_keys|plan_matrix}; completed={comma-separated completed gates}\n```\n\nRules:\n- Never execute a step if its gate is missing. Go back to the step that collects the missing input.\n- If user input is needed, ask exactly the requested question, then stop.\n- If a command fails, do not skip forward. Fix it, retry when safe, or stop with the blocker.\n- If the user changes a previous answer, update state and resume from the earliest affected step.\n- If conversation context is compacted or unclear, reconstruct state from `SETUP_STRIPE_CHECKLIST.md`, local files, and the latest user messages before continuing.\n\u003C\u002Fhard_execution_contract>\n\n\u003Cchecklist_protocol>\nThe agent MUST use a temporary root checklist file to force strict ordering.\n\nChecklist file:\n- Runtime path: `SETUP_STRIPE_CHECKLIST.md` at the project root.\n- Template path: `templates\u002FSETUP_STRIPE_CHECKLIST.md`.\n- Create it in Step 0 before any setup command if it does not exist.\n- Update it before and after every step by checking boxes and filling the state fields.\n- Update it with normal file edits; do not overwrite the whole checklist unless creating it from the template.\n- At the end, after validation and final summary preparation, delete it with `trash SETUP_STRIPE_CHECKLIST.md`.\n- If `trash` is unavailable, do not delete files; tell the user cleanup could not run.\n\u003C\u002Fchecklist_protocol>\n\n\u003Cstop_gates>\nThese are mandatory stop points:\n\n| Stop Gate | Step | Stop Until |\n| --- | --- | --- |\n| API keys requested | 1 | User provides `STRIPE_SECRET_KEY=...` or says to stop |\n| Plan matrix requested | 2 | User provides complete plan data or explicitly asks for defaults |\n| Stripe creation confirmation when mode is live | 3 | User confirms creating live Stripe objects |\n\u003C\u002Fstop_gates>\n\n\u003Cgate_matrix>\n| Step | Required Before Starting | Required Before Advancing |\n| --- | --- | --- |\n| 0 | Skill loaded | Convex checked, billing files read, Stripe SDK available |\n| 1 | Step 0 complete | `STRIPE_SECRET_KEY` set in Convex env, webhook helper run or blocker documented |\n| 2 | Step 1 complete | Complete plan matrix received and normalized |\n| 3 | Step 2 complete | Billing code updated and TypeScript validation run |\n| 4 | Step 3 complete | Stripe Products\u002FPrices created or reused from `convex\u002Fbilling\u002Fplans.ts`, price env vars set in Convex |\n| 5 | Step 4 complete | Changelog updated, cleanup attempted, final summary complete |\n\u003C\u002Fgate_matrix>\n\n\u003Cstate_variables>\nPersist these values across steps:\n\n| Variable | Description |\n| --- | --- |\n| `{stripe_mode}` | `test` or `live`, detected from `STRIPE_SECRET_KEY` prefix or argument |\n| `{stripe_secret_key_set}` | Whether `STRIPE_SECRET_KEY` was set in Convex env |\n| `{webhook_configured}` | Whether `scripts\u002Fsetup-stripe-webhook.mjs` created\u002Fverified the webhook and Convex signing secret |\n| `{plan_matrix}` | The user-provided normalized plan data applied to `convex\u002Fbilling\u002Fplans.ts` |\n| `{stripe_price_envs}` | Mapping of env var names to Stripe Price IDs created or reused |\n| `{code_files_updated}` | Billing files updated in Step 4 |\n| `{validation_notes}` | Passed\u002Fskipped\u002Ffailed verification commands |\n\u003C\u002Fstate_variables>\n\n\u003Centry_point>\nLoad `steps\u002Fstep-00-preflight.md`.\n\u003C\u002Fentry_point>\n\n\u003Cstep_files>\n| Strict Step | File | Purpose |\n| --- | --- | --- |\n| 0 | `steps\u002Fstep-00-preflight.md` | Verify setup and initialize workflow state |\n| 1 | `steps\u002Fstep-01-collect-keys.md` | Collect Stripe API keys and write secrets to Convex env |\n| 2 | `steps\u002Fstep-02-collect-plans.md` | Collect the plan and price matrix |\n| 3 | `steps\u002Fstep-03-update-code.md` | Update billing plan code and UI plan features |\n| 4 | `steps\u002Fstep-04-create-stripe.md` | Create\u002Freuse Stripe products and prices from code, then set Convex env price IDs |\n| 5 | `steps\u002Fstep-05-finalize.md` | Validate, update changelog, clean up, summarize |\n\u003C\u002Fstep_files>\n\n\u003Cbundled_resources>\n| File | Purpose |\n| --- | --- |\n| `templates\u002FSETUP_STRIPE_CHECKLIST.md` | Runtime checklist template copied to project root during Step 0 and removed at the end |\n| `scripts\u002Fcreate-stripe-plans.mjs` | Idempotently creates\u002Freuses Stripe products\u002Fprices from `convex\u002Fbilling\u002Fplans.ts` and can write price IDs to Convex env |\n\u003C\u002Fbundled_resources>\n\n\u003Cstack_context>\nNowStack stores billing definitions in `convex\u002Fbilling\u002Fplans.ts`. The UI auth plans in `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts` derive core plan data from that Convex module and only add UI-only features\u002Ficons.\n\nStripe is handled by Convex:\n- Checkout and portal flows call Convex actions.\n- Webhooks go to `https:\u002F\u002F\u003Cdeployment>.convex.site\u002Fstripe\u002Fwebhook`, mounted in `convex\u002Fhttp.ts`.\n- `STRIPE_SECRET_KEY`, `STRIPE_WEBHOOK_SECRET`, and `STRIPE_*_PLAN_ID` values belong in Convex env.\n- Stripe Price metadata must include `plan: \"\u003Cplan-name>\"` because webhook processing reads it.\n\u003C\u002Fstack_context>\n\n\u003Cimportant_files>\nFiles this workflow may modify:\n\n| File | Change |\n| --- | --- |\n| `convex\u002Fbilling\u002Fplans.ts` | Plan names, descriptions, prices, limits, trial days, and Stripe env var names |\n| `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts` | UI-only features\u002Ficons and limit display labels when limits change |\n| `CHANGELOG.md` | Required changelog entry |\n| `SETUP_STRIPE_CHECKLIST.md` | Temporary runtime checklist, removed at the end |\n\nFiles this workflow reads:\n\n- `.agents\u002Frules\u002Fstripe-billing.md`\n- `.agents\u002Frules\u002Fchangelog.md`\n- `convex\u002Fbilling\u002Fplans.ts`\n- `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts`\n- `scripts\u002Fsetup-stripe-webhook.mjs`\n- `package.json`\n\u003C\u002Fimportant_files>\n\n\u003Csuccess_metrics>\n- `STRIPE_SECRET_KEY` is set in Convex env.\n- `STRIPE_WEBHOOK_SECRET` is set in Convex env after the webhook helper runs against `VITE_CONVEX_SITE_URL`.\n- Every paid plan has a Stripe monthly Price ID in Convex env.\n- Every paid plan with annual billing has a Stripe annual Price ID in Convex env.\n- `convex\u002Fbilling\u002Fplans.ts` matches the user's plan names, descriptions, limits, trial days, prices, currency, and env var names.\n- `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts` has UI-only feature copy for every visible plan.\n- `pnpm ts` passes, or any failure is documented with the exact blocker.\n- `CHANGELOG.md` has a `FEATURE:` or `CHORE:` entry under today's date.\n\u003C\u002Fsuccess_metrics>\n\n\u003Cfailure_modes>\n- Writing `sk_*` secrets to tracked files instead of Convex env.\n- Creating Stripe prices before `convex\u002Fbilling\u002Fplans.ts` reflects the plan matrix.\n- Creating live Stripe objects without explicit live-mode confirmation.\n- Updating UI features but not `convex\u002Fbilling\u002Fplans.ts`, which is the source of truth.\n- Setting price IDs in local `.env` only; Convex actions will not see them.\n- Forgetting `metadata.plan` on Stripe Prices, which breaks webhook plan mapping.\n\u003C\u002Ffailure_modes>\n\n## NEXT STEP\n\nLoad `steps\u002Fstep-00-preflight.md`.\n","# Setup Stripe - Strict NowStack Billing Setup\n\n\u003Cobjective>\nConfigure Stripe billing for a NowStack app in one strict order: verify the local Convex setup, collect Stripe API keys, write secrets to Convex env, collect the desired plans and prices, update the billing code, create products and recurring prices directly in the user's Stripe account from `convex\u002Fbilling\u002Fplans.ts`, then validate.\n\u003C\u002Fobjective>\n\n\u003Cstrict_order>\nThis workflow MUST follow this order exactly. Do not reorder, merge, or skip steps unless the user explicitly asks to stop or skip the current step.\n\n1. Preflight: verify Convex config, required files, Stripe SDK availability, and current billing plan shape.\n2. API keys: collect `STRIPE_SECRET_KEY`, set it in Convex env, then run the existing webhook helper to create\u002Fupdate the Convex Stripe webhook and set `STRIPE_WEBHOOK_SECRET`.\n3. Plans and prices: ask for the full plan matrix in one structured response.\n4. Code update: update `convex\u002Fbilling\u002Fplans.ts` and UI-only plan features in `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts`.\n5. Stripe creation: create or reuse Stripe Products and recurring Prices in the user's Stripe account from `convex\u002Fbilling\u002Fplans.ts`, then write the resulting Price IDs into Convex env.\n6. Finish: validate, update `CHANGELOG.md`, clean temporary files, and summarize.\n\u003C\u002Fstrict_order>\n\n\u003Cinteraction_rules>\n- Never ask for secrets and plan details in the same message.\n- Never write Stripe secrets to `.env`, `.env.local`, Vercel env, `CHANGELOG.md`, or any git-tracked file.\n- Do not print full secret values. Mask them as `sk_test_...1234` \u002F `sk_live_...1234`.\n- Use `request_user_input` when available and allowed for checkpoint choices. Plain text is the fallback.\n- Keep the user's language for prompts and summaries.\n- If the user provides a publishable key, only record whether it was provided. Do not store it unless the codebase actually needs `VITE_STRIPE_PUBLISHABLE_KEY`.\n\u003C\u002Finteraction_rules>\n\n\u003Chard_execution_contract>\nThe agent MUST treat this workflow as a gated state machine, not loose guidance.\n\nBefore every step, write a compact state summary:\n\n```text\nSTRIPE STATE: step={current_step}; waiting_for={none|api_keys|plan_matrix}; completed={comma-separated completed gates}\n```\n\nRules:\n- Never execute a step if its gate is missing. Go back to the step that collects the missing input.\n- If user input is needed, ask exactly the requested question, then stop.\n- If a command fails, do not skip forward. Fix it, retry when safe, or stop with the blocker.\n- If the user changes a previous answer, update state and resume from the earliest affected step.\n- If conversation context is compacted or unclear, reconstruct state from `SETUP_STRIPE_CHECKLIST.md`, local files, and the latest user messages before continuing.\n\u003C\u002Fhard_execution_contract>\n\n\u003Cchecklist_protocol>\nThe agent MUST use a temporary root checklist file to force strict ordering.\n\nChecklist file:\n- Runtime path: `SETUP_STRIPE_CHECKLIST.md` at the project root.\n- Template path: `templates\u002FSETUP_STRIPE_CHECKLIST.md`.\n- Create it in Step 0 before any setup command if it does not exist.\n- Update it before and after every step by checking boxes and filling the state fields.\n- Update it with normal file edits; do not overwrite the whole checklist unless creating it from the template.\n- At the end, after validation and final summary preparation, delete it with `trash SETUP_STRIPE_CHECKLIST.md`.\n- If `trash` is unavailable, do not delete files; tell the user cleanup could not run.\n\u003C\u002Fchecklist_protocol>\n\n\u003Cstop_gates>\nThese are mandatory stop points:\n\n| Stop Gate | Step | Stop Until |\n| --- | --- | --- |\n| API keys requested | 1 | User provides `STRIPE_SECRET_KEY=...` or says to stop |\n| Plan matrix requested | 2 | User provides complete plan data or explicitly asks for defaults |\n| Stripe creation confirmation when mode is live | 3 | User confirms creating live Stripe objects |\n\u003C\u002Fstop_gates>\n\n\u003Cgate_matrix>\n| Step | Required Before Starting | Required Before Advancing |\n| --- | --- | --- |\n| 0 | Skill loaded | Convex checked, billing files read, Stripe SDK available |\n| 1 | Step 0 complete | `STRIPE_SECRET_KEY` set in Convex env, webhook helper run or blocker documented |\n| 2 | Step 1 complete | Complete plan matrix received and normalized |\n| 3 | Step 2 complete | Billing code updated and TypeScript validation run |\n| 4 | Step 3 complete | Stripe Products\u002FPrices created or reused from `convex\u002Fbilling\u002Fplans.ts`, price env vars set in Convex |\n| 5 | Step 4 complete | Changelog updated, cleanup attempted, final summary complete |\n\u003C\u002Fgate_matrix>\n\n\u003Cstate_variables>\nPersist these values across steps:\n\n| Variable | Description |\n| --- | --- |\n| `{stripe_mode}` | `test` or `live`, detected from `STRIPE_SECRET_KEY` prefix or argument |\n| `{stripe_secret_key_set}` | Whether `STRIPE_SECRET_KEY` was set in Convex env |\n| `{webhook_configured}` | Whether `scripts\u002Fsetup-stripe-webhook.mjs` created\u002Fverified the webhook and Convex signing secret |\n| `{plan_matrix}` | The user-provided normalized plan data applied to `convex\u002Fbilling\u002Fplans.ts` |\n| `{stripe_price_envs}` | Mapping of env var names to Stripe Price IDs created or reused |\n| `{code_files_updated}` | Billing files updated in Step 4 |\n| `{validation_notes}` | Passed\u002Fskipped\u002Ffailed verification commands |\n\u003C\u002Fstate_variables>\n\n\u003Centry_point>\nLoad `steps\u002Fstep-00-preflight.md`.\n\u003C\u002Fentry_point>\n\n\u003Cstep_files>\n| Strict Step | File | Purpose |\n| --- | --- | --- |\n| 0 | `steps\u002Fstep-00-preflight.md` | Verify setup and initialize workflow state |\n| 1 | `steps\u002Fstep-01-collect-keys.md` | Collect Stripe API keys and write secrets to Convex env |\n| 2 | `steps\u002Fstep-02-collect-plans.md` | Collect the plan and price matrix |\n| 3 | `steps\u002Fstep-03-update-code.md` | Update billing plan code and UI plan features |\n| 4 | `steps\u002Fstep-04-create-stripe.md` | Create\u002Freuse Stripe products and prices from code, then set Convex env price IDs |\n| 5 | `steps\u002Fstep-05-finalize.md` | Validate, update changelog, clean up, summarize |\n\u003C\u002Fstep_files>\n\n\u003Cbundled_resources>\n| File | Purpose |\n| --- | --- |\n| `templates\u002FSETUP_STRIPE_CHECKLIST.md` | Runtime checklist template copied to project root during Step 0 and removed at the end |\n| `scripts\u002Fcreate-stripe-plans.mjs` | Idempotently creates\u002Freuses Stripe products\u002Fprices from `convex\u002Fbilling\u002Fplans.ts` and can write price IDs to Convex env |\n\u003C\u002Fbundled_resources>\n\n\u003Cstack_context>\nNowStack stores billing definitions in `convex\u002Fbilling\u002Fplans.ts`. The UI auth plans in `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts` derive core plan data from that Convex module and only add UI-only features\u002Ficons.\n\nStripe is handled by Convex:\n- Checkout and portal flows call Convex actions.\n- Webhooks go to `https:\u002F\u002F\u003Cdeployment>.convex.site\u002Fstripe\u002Fwebhook`, mounted in `convex\u002Fhttp.ts`.\n- `STRIPE_SECRET_KEY`, `STRIPE_WEBHOOK_SECRET`, and `STRIPE_*_PLAN_ID` values belong in Convex env.\n- Stripe Price metadata must include `plan: \"\u003Cplan-name>\"` because webhook processing reads it.\n\u003C\u002Fstack_context>\n\n\u003Cimportant_files>\nFiles this workflow may modify:\n\n| File | Change |\n| --- | --- |\n| `convex\u002Fbilling\u002Fplans.ts` | Plan names, descriptions, prices, limits, trial days, and Stripe env var names |\n| `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts` | UI-only features\u002Ficons and limit display labels when limits change |\n| `CHANGELOG.md` | Required changelog entry |\n| `SETUP_STRIPE_CHECKLIST.md` | Temporary runtime checklist, removed at the end |\n\nFiles this workflow reads:\n\n- `.agents\u002Frules\u002Fstripe-billing.md`\n- `.agents\u002Frules\u002Fchangelog.md`\n- `convex\u002Fbilling\u002Fplans.ts`\n- `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts`\n- `scripts\u002Fsetup-stripe-webhook.mjs`\n- `package.json`\n\u003C\u002Fimportant_files>\n\n\u003Csuccess_metrics>\n- `STRIPE_SECRET_KEY` is set in Convex env.\n- `STRIPE_WEBHOOK_SECRET` is set in Convex env after the webhook helper runs against `VITE_CONVEX_SITE_URL`.\n- Every paid plan has a Stripe monthly Price ID in Convex env.\n- Every paid plan with annual billing has a Stripe annual Price ID in Convex env.\n- `convex\u002Fbilling\u002Fplans.ts` matches the user's plan names, descriptions, limits, trial days, prices, currency, and env var names.\n- `src\u002Flib\u002Fauth\u002Fstripe\u002Fauth-plans.ts` has UI-only feature copy for every visible plan.\n- `pnpm ts` passes, or any failure is documented with the exact blocker.\n- `CHANGELOG.md` has a `FEATURE:` or `CHORE:` entry under today's date.\n\u003C\u002Fsuccess_metrics>\n\n\u003Cfailure_modes>\n- Writing `sk_*` secrets to tracked files instead of Convex env.\n- Creating Stripe prices before `convex\u002Fbilling\u002Fplans.ts` reflects the plan matrix.\n- Creating live Stripe objects without explicit live-mode confirmation.\n- Updating UI features but not `convex\u002Fbilling\u002Fplans.ts`, which is the source of truth.\n- Setting price IDs in local `.env` only; Convex actions will not see them.\n- Forgetting `metadata.plan` on Stripe Prices, which breaks webhook plan mapping.\n\u003C\u002Ffailure_modes>\n\n## NEXT STEP\n\nLoad `steps\u002Fstep-00-preflight.md`.\n",{"name":5,"description":7,"argument-hint":24},"[test|live]","master","46a82833a3f7f6f5f408511246a55e0485c5f7ab","skills\u002Fsetup-stripe",1,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills","https:\u002F\u002Fgithub.com\u002Fzuzu59","2026-09-30 17:58:42",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add zuzu59\u002Fz-skills --skill setup-stripe",{"tool":38,"command":39},"bunx","bunx skills add zuzu59\u002Fz-skills --skill setup-stripe",{"tool":41,"command":42},"pnpm","pnpm dlx skills add zuzu59\u002Fz-skills --skill setup-stripe","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002FSKILL.md",true,[46,52,58,62,66,70,74,78],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"scripts\u002Fcreate-stripe-plans.mjs","SCRIPT","脚本",8204,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Fscripts\u002Fcreate-stripe-plans.mjs",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"steps\u002Fstep-00-preflight.md","REFERENCE","参考文档",2303,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Fsteps\u002Fstep-00-preflight.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"steps\u002Fstep-01-collect-keys.md",2542,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Fsteps\u002Fstep-01-collect-keys.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"steps\u002Fstep-02-collect-plans.md",2765,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Fsteps\u002Fstep-02-collect-plans.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"steps\u002Fstep-03-update-code.md",2718,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Fsteps\u002Fstep-03-update-code.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"steps\u002Fstep-04-create-stripe.md",2656,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Fsteps\u002Fstep-04-create-stripe.md",{"path":75,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":76,"sourceHtmlUrl":77},"steps\u002Fstep-05-finalize.md",1712,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Fsteps\u002Fstep-05-finalize.md",{"path":79,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":80,"sourceHtmlUrl":81},"templates\u002FSETUP_STRIPE_CHECKLIST.md",1618,"https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fsetup-stripe\u002Ftemplates\u002FSETUP_STRIPE_CHECKLIST.md",[83,90,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M76SQGVSKRYNQX4AA4RXV3K0","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M76SQDSAZSA1272D56JY8Q2G","use-style","Apply named visual style guides to landing pages, app shells, and UI. Use for $use-style, \u002Fuseskill, list styles, or styles like ios-app, grid, vercel, black-grid, stripe, linear, raycast, gumroad, dusk, or luma.","https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-style\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M76SQAXDVX02V4JH4PF1MC9G","use-goal","Use when the user asks to create, draft, set, start, or refine a Codex or Claude Code `\u002Fgoal` objective for persistent multi-turn work.","https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-goal\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M76SQ8B11GTTGQ5CZHHGXFXM","use-fable","Orchestrator mode for Fable: Fable thinks, plans, and reviews while Codex CLI and subagents execute all heavy work. Use when the user invokes \u002Fuse-fable, says 'use fable', 'fable mode', 'orchestrator mode', or wants to save Fable tokens\u002Frate limits.","https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-fable\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M76SQ4SB7Q4CXEGGPA75KGFK","use-delegate","Delegation mode: the host agent (Claude or Codex) plans and reviews while heavy work runs on cheap executors: OpenCode Kimi K3, Codex GPT-5.6 terra\u002Fsol. Use when the user invokes \u002Fuse-delegate, says 'use delegate', 'delegate mode', 'orchestrator mode', or wants to save tokens\u002Frate limits.","https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-delegate\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M76SQ24836GDGMGGPV6Z2B7N","use-artifacts","Create Claude-style local HTML artifacts under ~\u002F.agents\u002Fartifacts. Use for plans, prototypes, visualizations, dashboards, diagrams, options, or substantial reusable content, with a portable local runtime and no Anthropic API.","https:\u002F\u002Fgithub.com\u002Fzuzu59\u002Fz-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-artifacts\u002FSKILL.md",[],[]]