pricing-archetype-mapper

Transforms domain requirements into a structured pricing archetype model with calculators, components, and versioning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing a pricing engine from raw business requirements is error-prone: teams mix calculation logic with business conditions, lose historical reproducibility, and silently assume policies. This Skill guides a structured mapping from domain requirements to a complete, implementable pricing archetype model with explicit decisions and auditability. ## Core Features & Use Cases - Fit Test & Complexity Assessment: Determines whether the pricing archetype applies and classifies the domain into complexity levels 1-9 before any modeling begins. - Full Model Design: Produces Calculator layer, Component tree (Simple/Composite), Validity versioning with half-open intervals, Applicability conditions, context Parameters, and product-pricing mapping scenarios (1:1 through N:M). - Decision Sanity Check: Enumerates every modeling decision and traces it to requirements, clarifying answers, or explicit assumptions, with mandatory Unmapped Concepts reporting. - Use Case: Given EV charging station requirements (startup fee, per-kWh rate, time surcharge, night discount, VAT, changing tariffs), the Skill outputs a complete component tree with calculators, validity rules, and reproducible historical pricing. ## Quick Start Ask the AI to map your pricing domain requirements into a pricing archetype model, for example by describing what is priced, which factors affect the price, and what business questions the system must answer.

Frequently Asked Questions about pricing-archetype-mapper

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

FAQPage Schema
How do I design a pricing engine from business requirements?

Feed the domain requirements to the pricing-archetype-mapper, which runs a fit test, assesses complexity level 1-9, asks clarifying questions, then outputs calculators, a component tree, validity versioning, applicability conditions, and a product-pricing mapping scenario.

When should I use a pricing archetype instead of an accounting ledger?

Use the pricing archetype when the natural question is how much X costs for customer Y at time T in context C. If the question is how much of X does Y have, that is an accounting ledger; if it is what state X is in, that is a state machine.

How do I keep historical prices reproducible after rate changes?

Model each rate change as a new immutable ComponentVersion with a validFrom date and definedAt timestamp instead of overwriting. Calling versionAt with the historical transaction timestamp recomputes the price using the rules active at that time.

Where should tariff selection and eligibility logic live?

Eligibility belongs in the application layer, never inside the pricing engine. The application selects which component tree root applies for a customer and context, then the pricing engine computes the breakdown for that root.

What are the limitations of the pricing archetype approach?

It does not fit accounting ledgers or state machines, and level 1-2 domains with a single static stored price may not need the full archetype. The Skill stops and reports when the fit test fails rather than forcing a mapping.