Skip to content

Latest commit

 

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

tstack

Billing team for Claude Code.

tstack is a monetization team for usage-based SaaS products. Two layers: a design chain that builds billing systems from scratch (7 skills, artifact-chained), and a review team that audits, operates, and monitors billing that exists (15 skills, reactive). Derived from real self-serve billing operations.

Install

git clone https://github.com/tansohq/tstack.git
cd tstack
./setup

The setup script symlinks tstack into ~/.claude/skills/tstack and verifies the skills are accessible. Run it again anytime — it's idempotent.

The Chain (Design Workflow)

Run /monetization-engineer to design a billing system from scratch. It walks you through the chain:

meter → pricing → enforcement → credits → [hierarchy] → reconciliation → integration
Skill What it does Artifact
/monetization-engineer Orchestrate the billing design chain
/meter-design Define billing units, event schemas, aggregation METER.md
/pricing-model Structure plan tiers, feature packaging, pricing PLAN.md
/entitlement-enforcement Design allow/deny logic, hard/soft limits ENFORCEMENT.md
/credit-ledger Prepaid credit pools, grants, drawdown, expiry CREDITS.md
/account-hierarchy Parent/child accounts, per-key budgets [optional] HIERARCHY.md
/reconciliation Usage-to-billing drift detection and true-up RECONCILIATION.md
/provider-integration Map design to Stripe subscriptions and invoices INTEGRATION.md

Each skill writes a structured markdown artifact that the next skill reads. Decisions accumulate — every downstream skill has full context from upstream choices.

The Team (Review & Operations)

Run any team skill directly. They read chain artifacts (if they exist) or work from your description of an existing billing system.

Review / Audit

Skill Lens What it does
/billing-reviewer Backend dev Audit for race conditions, double-charges, idempotency gaps
/stripe-correctness Backend dev Detect 14 Stripe API footguns — webhooks, proration, state machine, currency
/state-machine-guard Backend dev Extract and audit subscription state transitions, missing side effects, races
/metering-correctness Backend dev Find idempotency gaps, recursion loops, clock skew, and aggregation bugs in usage metering
/pricing-auditor Rev ops / finance Evaluate unit economics, margins, competitive position
/billing-qa QA Generate edge case test scenarios (proration, timezone, currency)
/alignment-check Cross-functional Check pricing vs sales motion, enterprise vs self-serve conflicts

Operations

Skill Lens What it does
/billing-operations Support / ops / CS Account lifecycle + credit management playbooks
/migration-planner PM Plan pricing changes with grandfathering and rollback

Intelligence

Skill Lens What it does
/revenue-reporter Finance MRR/ARR, revenue recognition with credits, churn decomposition
/account-intelligence CS / growth Account health, churn risk, PQL scoring, credit run-out
/api-health-analyst Reliability Per-account error rates, customer vs platform error attribution

Observability

Skill Lens What it does
/billing-observability On-call / SRE Monitoring, alerting, drift detection, incident investigation

Design & Research

Skill Lens What it does
/billing-ux-designer Design Usage dashboards, plan picker, credit run-out display
/pricing-researcher Market intel Competitive pricing teardowns and model precedent research

How It Works

Nothing touches your codebase. Chain skills produce markdown artifacts. Team skills produce findings and recommendations. No code generated, no deployments, no Stripe changes. Read the output, decide if you agree, implement on your own terms.

When a skill hits a judgment call (hard vs soft limit, billing unit, pricing model, overage behavior), it stops and surfaces the tradeoff. Decisions are made by you, not silently resolved.

Build

bun install              # install dev dependencies
bun run build            # generate SKILL.md from templates
bun test                 # run validation tests
bun run gen:skill-docs --dry-run  # check template freshness

Skills are generated from .tmpl templates via a resolver pipeline. Edit the template, not the output.

About

Tanso's billing team skill pack for Claude Code. Inspired by gstack.

About

Billing engineer skills for Claude Code — entitlement-centered monetization design

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages