Total 52,363 skills, Product & Design has 1980 skills
Showing 12 of 1980 skills
Facilitates the third step of a proven customer-interview method: translating hypotheses into open-ended, unbiased interview questions — each a miniature experiment designed to test one hypothesis without leading the witness. Two modes: given a single hypothesis, it grills the question into shape and outputs the final question in chat; given a HYPOTHESES.md file, it iterates the whole list, grouping related hypotheses, and maintains a QUESTIONS.md file (numbered Q1, Q2, … mapped to H-numbers) as a live, resumable artifact. Load when the user has hypotheses and wants interview questions, asks how to phrase a question for customers without biasing the answer, or says 'turn my hypotheses into questions' or 'help me ask about X without leading.' Do NOT load for writing goal questions or hypotheses (earlier steps), for conducting or analyzing the interviews themselves, for survey/questionnaire design, or for job interviews.
Builds a customer Needs Stack — the ladder in which every need is a means to the end one level up (buy infrastructure → set up a WordPress site → have a personal website → get a book deal). Anchors the level the user's product satisfies, phrased as the customer's own goal in the customer's own words, then walks downward (the steps the product makes obsolete) and upward (what the customer really wants), crystallizing every level — specific wording, a true means-to-an-end link, named real-world occupants — before moving on. Records the stack in NEEDS-STACK.md with the user's level marked and each level's positioning role: what you do, promise, reference as aspiration, or brag about obviating. Load when the user asks what their customer really wants, what level their product operates at, who their real alternatives (not just competitors) are, or to 'build our needs stack.' Do NOT load to rewrite marketing copy from a finished stack — that is a separate positioning task that consumes this file.
Plan, generate, source, normalize, and validate cohesive visual game assets. Use for art direction, style bibles, sprites, tilesets, backgrounds, UI art, icons, textures, concept art, or 3D asset briefs.
Facilitates the second step of a proven customer-interview method: recording the user's current best guesses — hypotheses — as numbered, falsifiable statements (H1, H2, …), each mapped to the goal questions it addresses, so interviews can confirm or contradict them instead of confirmation bias quietly filtering what's heard. Takes a GOALS.md goal-question list as input (file or pasted), elicits what the user believes goal by goal, sharpens vague beliefs into testable claims, prunes to hypotheses whose resolution would actually change what the user builds, targets, charges, or says, and preserves the result in HYPOTHESES.md. Load when the user has goal questions and wants to write hypotheses, list their assumptions, or record predictions before interviewing customers — 'I have my goals, what's next,' 'help me write down what I believe about my customers.' Do NOT load for writing the interview questions themselves, for analyzing interviews already conducted, or for statistical hypothesis testing.
Facilitates the third step of a proven ideal-customer (ICP) method: refining classified strengths into keystones — the specific characteristics, behaviors, or circumstances that make a customer NEED an extreme version of a strength, badly enough to drive the purchase alone. Takes a strengths chart (S1, S2, … — file or pasted), walks the strengths one at a time asking who requires an extreme version of each, gates every candidate on naming a real market segment that typifies it (no segment = table stakes, cut), and records survivors in KEYSTONES.md (K1, K2, … with [S] references and example segments). Delivers the strategic verdict when few or none survive: the product isn't compelling yet. Load when the user has classified strengths and asks who needs them, who their target market is, or 'turn our strengths into keystones.' Do NOT load to classify strengths and weaknesses (the previous step), to derive deal-breakers or the anti-market (the next step), or to write the final ideal-customer definition (later).
Facilitates the learning step of a proven customer-interview method — the synthesis half: reads a directory of per-interview debrief files against the working HYPOTHESES.md and QUESTIONS.md and proposes evidence-cited updates ONE at a time — double down, tune numbers, mark disproved, park heard-once observations in a 'That's funny' watch section, add new hypotheses with new questions — applying each agreed change directly to the files with a change log, and ending with a stop-or-continue-or-re-aim verdict on the interviewing itself. Load when the user says 'what did we learn from these interviews,' 'update my hypotheses from the interviews,' 'synthesize my interview notes,' or 'should I keep interviewing?' Do NOT load for recording a single conversation into a debrief (the previous step), for writing initial goals, hypotheses, or interview questions (earlier steps), or for deciding what to build next (comes after this method).
Facilitates the first step of a proven ideal-customer (ICP) method: gathering raw, honest, specific observations about what a company and product actually are — before any judgment about strengths or weaknesses. Walks the user through twelve unsparing question categories (what customers praise, the complaint with no defense, what separates your most profitable customers, and more) — or processes a team's write-storm notes one observation at a time — and records the results in OBSERVATIONS.md (numbered O1, O2, …), vivid and unevaluated. For a company operating online, it first scans public reviews and press into an External Research section that seeds it. Load when the user wants to figure out their ideal customer, take an honest look at their company, run a strengths-and-weaknesses exercise from scratch, or says 'who is our Carol' or 'what are we actually good at.' Do NOT load to classify observations into strengths and weaknesses (the next step), or for personal self-reflection unrelated to a company.
Psychological profiling through natural conversation using narrative identity research (McAdams), self-defining memory elicitation (Singer), and Motivational Interviewing (OARS framework). Use when you need to: (1) understand someone's core values and motivations, (2) discover formative memories and life-defining experiences, (3) detect emotional schemas and belief patterns, (4) build psychological profiles through gradual disclosure, (5) conduct user interviews that reveal deep insights, (6) design conversational flows for personal discovery, (7) identify identity themes like redemption and contamination narratives, (8) elicit authentic self-disclosure without interrogation.
Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.