ship-billing
Skill202 starsChanged 7 months agoMITView on GitHub
You are helping the user implement a standard SaaS billing and subscription flow inside an existing web project. Build a clear and reusable billing setup that includes: - pricing page - checkout flow - subscription status - webhook handling - success and cancel pages - basic billing state handling When using this skill, the AI coding tool should: - understand the project context - propose a clean billing implementation plan - generate the main billing pages and flow structure -…
In this repository2 other files it gives its agents.
- ship-authSkill
- ship-landingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Prefer simple, maintainable billing flows over unnecessary abstractions.
- Distinctive: line 20
Keep the billing flow consistent across pricing, checkout, and account pages.
- Distinctive: line 21
Add clear placeholders when API keys, webhook secrets, or product IDs are missing.
- Distinctive: line 22
Avoid breaking unrelated parts of the project.
- Distinctive: line 27
When using this skill, the AI coding tool should:
≈ “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.
Files
ship-billing skill
You are helping the user implement a standard SaaS billing and subscription flow inside an existing web project.
Objectives
Build a clear and reusable billing setup that includes:
- pricing page
- checkout flow
- subscription status
- webhook handling
- success and cancel pages
- basic billing state handling
Instructions
- First inspect the project structure before making changes.
- Identify the current framework, payment provider, and routing pattern.
- Prefer simple, maintainable billing flows over unnecessary abstractions.
- Keep the billing flow consistent across pricing, checkout, and account pages.
- Add clear placeholders when API keys, webhook secrets, or product IDs are missing.
- Avoid breaking unrelated parts of the project.
- Explain what was added, what still needs manual setup, and how to test it.
Output expectations
When using this skill, the AI coding tool should:
- understand the project context
- propose a clean billing implementation plan
- generate the main billing pages and flow structure
- provide a short test checklist
- clearly mark any missing environment variables or manual steps
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.

