stripe-go-live-workflow
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Operational workflow for taking a working test-mode Stripe integration to live AND for verifying an already-live integration end-to-end. Covers the Dashboard walkthrough, the "never see the live key" safety rule, the test-mode dry run, the live deploy ritual, and the Express/Node verify-the-pipes ritual. Load when a user says "go live," "flip to live," "launch payments," "we're ready for real cards," "real money now," "production time," "I need money," "verify the live Stripe pipes," "smoke test the checkout," or "show me money," or has either a working test-mode Stripe integration that needs to ship OR an already-live Express/Worker integration that needs end-to-end verification. Default assumption when a user says "go live" is wrong: the integration may already be live from a previous session. Always audit state first. Skip for API design questions, key-management theory, or pure code-review tasks — those are covered by `stripe-best-practices`.
- Reads credentials
- Commits and pushes
In this repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-sdkSkill
- ai-visibility-for-small-sitesSkill
- ce-brainstormSkill
- ce-code-reviewSkill
- ce-commit-push-prSkill
- ce-commitSkill
- ce-compound-refreshSkill
- ce-compoundSkill
- ce-debugSkill
- ce-doc-reviewSkill
- ce-dogfood-betaSkill
- ce-ideateSkill
- ce-optimizeSkill
- ce-planSkill
- ce-polishSkill
- ce-product-pulseSkill
- ce-promoteSkill
- ce-proofSkill
- ce-resolve-pr-feedbackSkill
- ce-riffrec-feedback-analysisSkill
- ce-setupSkill
- ce-simplify-codeSkill
- ce-strategySkill
- ce-test-browserSkill
- ce-test-xcodeSkill
- ce-workSkill
- ce-worktreeSkill
- cloudflare-email-serviceSkill
- cloudflareSkill
- computer-useSkill
- conjecture-to-careSkill
- dogfoodSkill
- domain-availability-checkerSkill
- durable-objectsSkill
- agent-introspection-debuggingSkill
- agent-sortSkill
- api-designSkill
- article-writingSkill
- backend-patternsSkill
- brand-discoverySkill
- brand-voiceSkill
- coding-standardsSkill
- competitive-platform-analysisSkill
- competitive-report-structureSkill
- content-engineSkill
- crosspostSkill
- e2e-testingSkill
- eval-harnessSkill
- frontend-patternsSkill
- frontend-slidesSkill
- investor-materialsSkill
- investor-outreachSkill
- market-researchSkill
- mcp-server-patternsSkill
- product-capabilitySkill
- security-reviewSkill
- tdd-workflowSkill
- verification-loopSkill
- video-editingSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 9 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.