accounting-archetype-mapper

Transforms domain requirements into accounting-style ledger models with accounts, transactions, and reversals.

Updated Nov 19, 2020
One-click install
npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill accounting-archetype-mapper-kwojtasinski-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accounting-archetype-mapper
Source: https://github.com/kwojtasinski-repo/ECommerceApp/tree/main/.github/skills/accounting-archetype-mapper
Command: npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill accounting-archetype-mapper-kwojtasinski-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing value-tracking systems (points, quotas, credits, inventory) often leads to ad-hoc models that lack auditability, reversibility, and traceability. This Skill converts domain requirements into a rigorous double-entry accounting model so every value change is recorded, balanced, and reversible. ## Core Features & Use Cases - Archetype Fit Test: Determines upfront whether a domain is a ledger problem or a state machine, preventing misapplied modeling. - Structured Mapping Workflow: Guides through identifying values, accounts, transaction types, debit/credit entries, reversals, validity periods, and allocation strategies. - Clarifying Questions & Sanity Check: Surfaces business-impacting gaps via targeted questions and audits every design decision for silent assumptions before delivering the model. - Use Case: Given "customers get 10GB monthly data that expires, purchased data lasts 30 days", produce a complete model with accounts, balanced transactions, expiry rules, and FIFO allocation. ## Quick Start Ask the AI to map your domain requirements, for example: model a loyalty points system where users earn, purchase, and redeem points with expiration.

Frequently Asked Questions about accounting-archetype-mapper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I model a loyalty points or credits system as a ledger?

Describe the domain requirements and the skill maps them to accounting archetypes: asset and pool accounts, balanced debit/credit transactions for earn, purchase, and redeem operations, plus reversal and expiry rules. The output is an implementable double-entry model.

When should I use the accounting archetype instead of a state machine?

Use the accounting archetype when you can ask "how much X does subject S have?" and get a meaningful balance with transaction history. If the natural question is "what state is X in?" (e.g., ticket open/assigned/resolved), it is a state machine and the fit test will reject the mapping.

Can the accounting archetype track non-monetary resources?

Yes, the resource does not need to be money. It supports points, data quota, inventory units, leave days, API rate limits, energy units, or any value that accumulates, is consumed, or expires, including multi-unit scenarios with conversion rates.

How are refunds and corrections handled without deleting entries?

Reversals are modeled as compensating transactions that mirror the original with swapped debits and credits, referencing the original transaction ID. The ledger stays append-only, preserving full audit history while undoing business effects.

What happens when business rules vary by situation, like different expiry per user tier?

Variable policies are treated as parameters computed above the ledger, such as valid_to or negative_balance_policy, and passed in at transaction time. The ledger enforces the given policy mechanically without embedding tier or authorization logic.