domain-ecommerce
Skill1 starsChanged 7 days agoMITView on GitHub
E-commerce and marketplace domain knowledge for Business Analysts — glossary, core processes (catalog, pricing & promotions, cart & checkout, payment, order management, fulfillment, shipping, returns & refunds, marketplace sellers & settlement), business rules (voucher stacking, inventory reservation, split orders, COD, refund routing), data model, integrations (payment gateways, e-wallets, shipping carriers, e-invoice, marketplaces), Vietnamese regulations and a BA question checklist. Use together with any BA task (requirements, user stories, linting, decomposition, diagrams, API/test design) whenever the context is online retail, an online store, marketplace, omnichannel retail, D2C, social commerce — or the user mentions "thương mại điện tử", "TMĐT", "sàn", "đơn hàng", "giỏ hàng", "voucher", "khuyến mãi", "flash sale", "COD", "vận chuyển", "đổi trả", "hoàn tiền", "seller", "tồn kho".
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-specSkill
- ba-diagramsSkill
- bpmn-modelingSkill
- decision-tableSkill
- domain-bankingSkill
- domain-lendingSkill
- domain-logisticsSkill
- domain-paymentsSkill
- edge-case-finderSkill
- functional-decompositionSkill
- meeting-to-requirementsSkill
- requirements-linterSkill
- screen-specSkill
- user-story-writerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 11
Read only the file(s) you need for the current task:
- Distinctive: line 26
If unknown, ask; otherwise state the assumption.
- Distinctive: line 35
Don't name a specific carrier/payment provider as required unless the user did — list them as common options.
≈ “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
Domain Pack: E-commerce & Marketplace / Thương mại điện tử
This skill adds domain knowledge on top of the BA method skills (meeting-to-requirements, requirements-linter, functional-decomposition, user-story-writer, ba-diagrams). It makes their output e-commerce-correct.
How to use the references
Read only the file(s) you need for the current task:
| Task | Read |
| Terminology | references/glossary.md |
| Decompose functions, draw processes, find missing steps | references/processes.md |
| Write/lint requirements, user stories, acceptance criteria | references/business-rules.md + references/checklist.md |
| ERD, data dictionary, API payloads, order/payment statuses | references/data-model.md |
| Context diagrams, sequence diagrams, integration/API specs | references/integrations.md |
| Compliance, consumer protection, tax & invoice | references/regulations.md |
| Business goals, analytics events, success metrics | references/kpis.md |
How to apply domain knowledge
- First identify the business model — it changes almost every rule:
- Single-brand online store (B2C / D2C) · Marketplace (multi-seller) · Omnichannel retailer (online + stores) · B2B ordering. If unknown, ask; otherwise state the assumption.
- Add the scenarios an e-commerce BA would never forget: out-of-stock during checkout, price/promotion changed in cart, voucher stacking, partial payment failure, split orders & partial shipment, COD refusal, failed delivery, return window, refund to original payment method, oversell in flash sale.
- Think in state machines: order, payment, shipment and return each have their own status — and they must stay consistent.
- Ask, don't invent: return windows, voucher rules, shipping fees and commissions are business decisions →
[value — confirm]. - Flag regulatory touchpoints (consumer protection, e-invoice, platform obligations, personal data) and add "verify current regulation with Legal".
Guardrails
- Knowledge is generic (Vietnam focus). Present as typical practice, not as the client's policy.
references/regulations.mdhas a "last reviewed" date; mention it when citing.- Don't name a specific carrier/payment provider as required unless the user did — list them as common options.
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.