product-design

Audit a page, screen, screenshot, artifact or URL against conversion heuristics: value proposition on the first screen, one primary action per screen, proof, sign-up and checkout friction, trust, pricing clarity and mobile. Returns prioritized findings, each with the fix, a severity and the metric or event that would prove it. Trigger on "conversion review", "why does nobody sign up", "audit this landing page", "review this pricing page", "will this page sell", "check the funnel on this screen", or before shipping any page whose job is to get a sign-up or a payment.

Design the return loop for a product: trigger, action, variable reward and investment, mapped to the product's real calendar (for a sports product: race weekends, qualifying, results, off weeks). Produces the notification plan with frequency caps and quiet hours, streak rules, and the analytics events for every step (entry, success, failure, drop-out). Trigger on "retention", "why don't people come back", "habit loop", "notification plan", "design streaks", "engagement loop", "make it sticky", or when planning push notifications or email cadence.

Write the structure and copy for a selling landing page: hero, proof, features as outcomes, pricing, FAQ and a final call to action, with variants per audience and an A/B test plan. Trigger on "write a landing page", "landing for", "homepage copy", "page for teams", "page for bookmakers", "B2B landing", "rewrite the hero", "A/B test the landing", or when a product or feature needs a page whose job is to sell.

Design paywalls, Pro gates and pricing pages that sell without annoying: partial or blurred previews instead of hard locks, anchoring and decoy tiers, the annual toggle, trial rules, upgrade moments tied to user success, copy patterns and what to measure. Honest by default, with an explicit list of forbidden dark patterns. Trigger on "design the paywall", "pricing page", "Pro gate", "how should we lock this feature", "upgrade screen", "trial or freemium", "annual vs monthly", "why is nobody buying Pro", or when reviewing any screen that asks for money.

Write or fix product microcopy: empty states, errors, loading, success and confirmation messages, buttons and labels that replace jargon with plain words (for example "average error in places" instead of "MAE"), and dates and times in the viewer's local time and a human format. Final text always goes through the humanizer skill; never em dashes or emojis. Trigger on "write the copy", "microcopy", "error message", "empty state", "rename this label", "this text sounds robotic", "UX writing", or when a screen ships new user-facing strings.