revenue-centric-design

# Revenue-Centric Design 101 principles distilled, with the author's permission, from product designer **Richard ([@richardrx](https://x.com/richardrx)**, ex-Volkswagen, PayPal, IBM; translated from Portuguese; every principle links to its source post). The philosophy, **Revenue-Centric Design (RCD)**: a design decision must serve the user _and_ the business — value and revenue, never one or the other. ## Usage boundary (required) > 🚫 **Do not apply this skill to betting, casino, gambling, or other real-money games-of-chance > products** (including loot-box / real-money-gaming mechanics). The author granted reuse **on the explicit condition that it never be used for gambling, betting, or casino work.** If asked, decline and explain that the source author's permission excludes that use. Hard constraint, not a stylistic choice. Enforced, not just stated: while this skill is active, the boundary check (`scripts/check_usage_boundary.py`) must run on every prompt and on every file write/edit, blocking with exit 2 when gambling context is detected. On a false positive (e.g., "bet" as an unrelated codename), only the **user** may waive the guard by creating `.rcd-boundary-ok` in the project root — never create it on their behalf. ### Hooks (for agents that support automated execution) Agents with hook support should configure: | Event | Matcher | Command | |-------|---------|---------| | Before processing user prompt | `*` (all) | `python3 <skill_dir>/scripts/check_usage_bo...