revenue-centric-design
FeaturedRevenue-Centric Design (RCD) — evidence-backed principles for making a SaaS or startup product convert, retain, and monetize. Use when the user works on a landing page or CRO ("my page isn't converting"), onboarding/activation ("users sign up but don't stick"), churn/retention ("customers keep canceling"), pricing/monetization ("how should I price this"), checkout/forms ("dropdowns kill conversion", "annotated checkout"), dashboards/data viz ("cognitive load", "KPI shortlists"), positioning/ICP/go-to-market, feature scope, A/B-test rigor, or AI-era differentiation — or asks for the behavioral-science mechanism behind a design choice. Also use when another skill needs the principle or evidence behind a conversion/retention/pricing/checkout move. Never apply to gambling, betting, or casino products.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- fabricioctelles
- Repository
- fabricioctelles/skills
- Created
- 7 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
ux-design-principles
Apply and enforce a consolidated set of UX/UI rules covering visual hierarchy, typography, spacing, shadows, colour, mobile product pages, bottom navigation bars, and conversion psychology (smart defaults, endowed progress, reciprocity, ownership, loss framing, price anchoring). Use this whenever building, reviewing, restyling or critiquing any user-facing screen, page, layout, component, form, onboarding flow, signup, pricing table, checkout, nav bar or CTA — including when the request is just "build me a landing page", "make this look better", "why does this feel off", or "review my UI". Also use when writing microcopy for buttons, labels, badges or empty states. Do not wait for the user to say "UX" or "design principles"; if the output is something a person will look at and click, this skill applies.
design-craft
UI/UX craft + design-decision communication skill, distilled from Albert Chipman's *UX/UI Design 2022* and Tom Greever's *Articulating Design Decisions*. Five modes: AUDIT a screen/component against visual-hierarchy, typography, readability, alignment/grid, consistency and microcopy rules; RATIONALE — write the 'Big Three' justification for any design decision (what problem it solves, how it affects the user, why it beats the alternative); RESPOND to design feedback or a stakeholder request with the IDEAL response (Thank→Repeat→Prepare, strategy, tactics, ask for agreement); PREP a design review (anticipated objections, alternatives, data, follow-up); INTAKE a new design project (goals, users, metrics, decision-maker). Use when the user says 'audit this UI', 'design review', 'looks amateur/unprofessional/AI-made', 'why did you design it this way', 'justify this design', 'the client/stakeholder wants X', 'present this design', 'readability', 'typography', 'visual hierarchy', 'microcopy', 'design rationale', or
cro-landing-designer
CRO + Landing Page Designer for Solaris - landing page design + build specs, conversion audits (Page Conversion Readiness Index), A/B + multivariate testing with statistical discipline (hypothesis lock, MDE, sample size, SRM, no peeking, ship/no-ship), offer + headline testing (AIDA/PAS/BAB/4Ps, awareness-stage matching), form + signup + checkout optimization (Form Health Index, field cost, progressive profiling), popup + exit-intent strategy, page-speed-for-conversion (LCP/INP/CLS), social proof + pricing-page presentation, heatmaps + session replay. Queries ui-ux-designer's landing.csv (34 patterns) for layout selection. Use when the owner says "landing page", "conversion rate", "CRO", "page converts at X%", "A/B test", "split test", "MDE", "sample size", "form optimization", "signup flow", "popup", "exit intent", "checkout funnel", "heatmap", "PostHog experiment", "VWO", "Optimizely", "GrowthBook", "Unbounce".