Turning CRO wisdom into agent-readable heuristics
It packages a CRO specialist’s Twitter wisdom into a structured agent skill so your coding assistant stops building SaaS interfaces that look pretty but fail to convert.

What it does
This repo packages 101 distilled principles from Richard (@richardrx), an ex-PayPal and ex-Volkswagen product designer, into an Agent Skill for Claude, Cursor, Codex, and other compatible agents. The material covers SaaS conversion, onboarding, pricing, and churn through the lens of “Revenue-Centric Design” — the premise that an interface must serve the business and the user simultaneously. When invoked, the skill surfaces only the relevant theme and feeds your agent named behavioral levers like the decoy effect, loss aversion, and the peak-end rule instead of generic UX platitudes.
The interesting bit
The project is essentially curation-as-infrastructure: it takes a six-month snapshot of a single X account and forces the unstructured posts into a rigid schema — Principle, Apply when, The move, Evidence, Visual, Source — so an LLM can cite specific heuristics rather than hallucinate design advice. It also carries an unusual ethical guardrail baked into the license: the skill is programmed to refuse requests related to gambling, betting, or casino products.
Key highlights
- 101 principles across 10 themes, from landing-page CRO to AI-era differentiation
- Progressive disclosure: only the theme relevant to your query is loaded into context
- Every principle links back to its original X post; attribution is mandatory, not optional
- Nine “RCD” spine principles anchor the philosophy, including “Neutrality is omission” and “Price is a filter”
- Coverage is frozen at July 1, 2026; newer posts from the source author are not yet included
Caveats
- This is a point-in-time snapshot, so posts published after July 1, 2026 are absent until manually curated
- The custom license explicitly prohibits use for gambling, betting, or casino products
Verdict
Worth a look if you want your agent to reason about conversion psychology and retention mechanics instead of shipping passive SaaS UI. Skip it if you need original research — the value here is disciplined curation and structure, not invention.
Frequently asked
- What is heliocosta-dev/revenue-centric-design?
- It packages a CRO specialist’s Twitter wisdom into a structured agent skill so your coding assistant stops building SaaS interfaces that look pretty but fail to convert.
- Is revenue-centric-design open source?
- Yes — heliocosta-dev/revenue-centric-design is an open-source project tracked on heatdrop.
- What language is revenue-centric-design written in?
- heliocosta-dev/revenue-centric-design is primarily written in Python.
- How popular is revenue-centric-design?
- heliocosta-dev/revenue-centric-design has 680 stars on GitHub.
- Where can I find revenue-centric-design?
- heliocosta-dev/revenue-centric-design is on GitHub at https://github.com/heliocosta-dev/revenue-centric-design.