agentleFS
Blink-hBlink-h/agent-startup-kit/skills/ship-billing/skill.md

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 -…

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
  1. Distinctive:

    Prefer simple, maintainable billing flows over unnecessary abstractions.

    line 19
  2. Distinctive:

    Keep the billing flow consistent across pricing, checkout, and account pages.

    line 20
  3. Distinctive:

    Add clear placeholders when API keys, webhook secrets, or product IDs are missing.

    line 21
  4. Distinctive:

    Avoid breaking unrelated parts of the project.

    line 22
  5. Distinctive:

    When using this skill, the AI coding tool should:

    line 27

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

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

  1. First inspect the project structure before making changes.
  2. Identify the current framework, payment provider, and routing pattern.
  3. Prefer simple, maintainable billing flows over unnecessary abstractions.
  4. Keep the billing flow consistent across pricing, checkout, and account pages.
  5. Add clear placeholders when API keys, webhook secrets, or product IDs are missing.
  6. Avoid breaking unrelated parts of the project.
  7. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.