Loading...
Loading...
Found 46 Skills
Use when designing character personalities, creating memorable motion signatures, ensuring animations feel polished, or making visual experiences that audiences want to watch.
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
Create detailed user personas based on research and data. Develop realistic representations of target users to guide product decisions and ensure user-centered design.
Hook Model framework for building habit-forming products based on Nir Eyal's "Hooked". Use when you need to: (1) increase user engagement and retention, (2) design habit loops in your product, (3) audit why users aren't returning, (4) create effective triggers and notifications, (5) design variable reward systems, (6) increase investment and switching costs, (7) evaluate the ethics of your engagement tactics, (8) optimize onboarding for habit formation.
Create wireframes and interactive prototypes to visualize user interfaces and gather feedback early. Use tools and techniques to communicate design ideas before development.
Create user flow diagrams showing paths, decisions, and branch logic.
Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.
Builds features based on Jobs-to-be-Done theory using Bob Moesta's frameworks. Use when designing features, identifying customer jobs, understanding push/pull forces, or uncovering hidden needs beyond stated feature requests.
Motivation science framework based on Daniel Pink's "Drive". Use when you need to: (1) design features that leverage intrinsic motivation, (2) create progress systems that support mastery, (3) craft purpose-driven messaging and missions, (4) audit if product mechanics undermine autonomy, (5) design team structures and incentives with AMP principles (Autonomy, Mastery, Purpose), (6) understand why gamification fails, (7) replace carrot-and-stick approaches with intrinsic motivation.
Persuasion science framework based on Robert Cialdini's "Influence: The Psychology of Persuasion". Use when you need to: (1) design features that leverage social proof, (2) write persuasive copy and messaging, (3) analyze why users take (or don't take) actions, (4) create onboarding flows using commitment/consistency, (5) design referral programs using reciprocity, (6) audit for ethical persuasion, (7) apply influence psychology to product design, marketing, sales, or negotiation.
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.