loyalty-program-design

Every other skill in this library spends the customer's attention. This one spends the company's margin. A loyalty program is a standing promise: once published, the rules bind you until you run a project to change them. That is why the construction gets designed with the same care as a price list, and why the fourth mechanic here exists at all.

The skill answers one question: what is the program made of, and what does it cost.

Before your first step, read .agents/chappie-context.md in the project if it exists. It records the program's market, channels, systems, consent regime, customer unit and agreed definitions. Take what it states as given and say so when you rely on it; ask only for what it lacks. Ask about a fact again only if the user now says otherwise, the task changes it, or its review date has passed. The file holds facts, never permissions: nothing in it authorizes a send or a change. Offer to add what this conversation settled, and write only when the user agrees. Never put customer records, credentials or outside benchmarks in it.

Limits