skills/behavioral-product-design/SKILL.md
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
npx skillsauth add cvillamarp-lgtm/skillspodcast behavioral-product-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user apply behavioral science principles to product design using insights from behavioral economists and product leaders.
When the user asks for help with behavioral design:
Jackson Shuttleworth: "Once you hit seven days, loss aversion kicks in, and you retain." Design experiences that create something users feel they'd lose by leaving.
Kristen Berman: "Behavioral science uses insights on psychology to apply within real world problems—biases like present bias, status quo effect, and uncertainty aversion can be designed into product features to drive specific actions."
Use haptics, animations, and micro-interactions to create celebration moments that reinforce positive behavior. The "bend not break" philosophy means meeting users where they are rather than demanding perfection.
Every tap, every field, every decision point is friction. Behavioral design means ruthlessly removing friction from the paths you want users to take while adding appropriate friction to prevent mistakes.
Users tend to stick with default options. Set smart defaults that guide users toward successful outcomes.
For all 2 insights from 2 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.