stripe-commercetools-tax-app
CLAUDE.md1 starsChanged 4 months agoMITView on GitHub
Client-owned Stripe Tax connector for commercetools. Deploys two independent CT Connect applications from a single connect.yaml: tax-calculator (service) and order-syncer (event handler). They do not call each other and can be deployed, operated, and read about independently — each has its own context/ and CLAUDE.md. Read the specific module's CLAUDE.md and context/ARCHITECTURE.md before working on it — there is no shared context between the two modules, so reading one does not give you knowledge of the other.
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read the specific module's CLAUDE.md and context/ARCHITECTURE.md before working on it — there is no shared context between the two modules, …
- Very specific: line 34
No Integration-level context/ was created or modified for this module.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
Stripe Tax App
Client-owned Stripe Tax connector for commercetools. Deploys two independent CT Connect applications from a single connect.yaml: tax-calculator (service) and order-syncer (event handler). They do not call each other and can be deployed, operated, and read about independently — each has its own context/ and CLAUDE.md.
Modules
| Module | Type | Trigger | Role |
tax-calculator/ | service | CT API Extension on cart Create/Update (taxMode=ExternalAmount) | Calculates tax via Stripe Tax, returns CT cart update actions |
order-syncer/ | event-handler | Google Pub/Sub push on CT OrderCreated | Commits Stripe tax transactions for completed orders |
Before Every Task
Read the specific module's CLAUDE.md and context/ARCHITECTURE.md before working on it — there is no shared context between the two modules, so reading one does not give you knowledge of the other.
Structure
stripe-commercetools-tax-app/
connect.yaml ← single manifest deploying both applications
tax-calculator/
CLAUDE.md
context/ ← module-level knowledge base (independent)
src/
order-syncer/
CLAUDE.md
context/ ← module-level knowledge base (independent)
src/Notes
- This is the client's deployment of the Stripe Tax connector. Orium's internal development equivalent (
ct-stripe-tax) lives elsewhere in this hub and is a separate codebase — see hub memory for why the two tracks exist. - No Integration-level
context/was created or modified for this module.commercetools-stripe-integration/context/documents Orium's internal connectors only and does not reference this client app.
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.