Total 52,548 skills, Product & Design has 1986 skills
Showing 12 of 1986 skills
Facilitates the first step of a proven customer-interview method: deciding exactly what you're trying to learn, written as numbered goal questions (G1, G2, …) that your hypotheses and interview questions will later be designed to answer. Interviews the user about their business — new idea or established company, B2B or B2C — then drafts a tailored goal-question list, critiques and revises it with them, and preserves the result in a GOALS.md file. Load when the user wants to interview customers, plan customer discovery or customer development, validate a startup idea, or answer unaskable questions like what to charge, how to position, who the ideal customer is, or what to build. Do NOT load for job or hiring interviews, for writing survey questionnaires, for analyzing customer interviews that have already been conducted, or when a goal-question list already exists and the user wants the next step (hypotheses).
Facilitates the fifth step of a proven ideal-customer (ICP) method: mapping inciting events — the specific trigger moments that move a perfect-fit customer from could-buy-someday to buying-today. Takes a keystones file (K1, K2, … with market segments) and, when available, customer-interview findings; walks the keystones one at a time, harvesting real trigger stories from interview evidence (marked observed) and working backward through brainstorm lenses — crises, seasonal cycles, strategic windows, personal life-changes — for the rest (marked hypothesized), recording each event with the keystone it couples to and how to find prospects in that condition, in INCITING-EVENTS.md (E1, E2, …). Load when the user has keystones and asks what makes customers buy now, what triggers a purchase, or 'run the inciting-events step.' Do NOT load to derive keystones or deal-breakers (previous steps), to write the final ideal-customer definition (next step), or to write the ads themselves.
Facilitates the second step of a proven ideal-customer (ICP) method: distilling raw company observations into the few deep-truth attributes that matter, then classifying each as a strength, a weakness, or deliberately both. Takes an observations list (O1, O2, … — file or pasted), proposes attributes one at a time with their supporting observations, kills generic ones with the Opposite Test ('we love our customers' dies), classifies each with a concrete rubric (a third of the market sees it that way, or some customers buy/refuse for it alone), and records the result in STRENGTHS-WEAKNESSES.md (S1, S2, … / W1, W2, …). Load when the user has raw observations and wants to distill them, asks 'what are our real strengths and weaknesses,' or wants to classify what they learned from the honest-look exercise. Do NOT load to gather the raw observations (the previous step), to derive keystones or deal-breakers from classified attributes (later steps), or for a person's individual strengths and weaknesses.
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.
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.
Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick, influence-psychology, high-perf-browser, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, DESIGN.md, POSITIONING.md, IMPROVE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a clunky product, cut UX friction, sharpen in-app copy and prompts, or says 'the app works but feels rough'. Do not use for code, tests, or production hardening - use improve-code-quality (fresh prototype) or remove-technical-debt (aged codebase); no app yet, create-app; needs growth loops, grow-app; marketing-site friction, improve-website. For one framework in isolation, invoke that skill directly.
Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says 'users sign up then disappear'. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.
Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (POSITIONING.md, WEBSITE.md, DESIGN.md, CREATE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new website or landing page from scratch, turn a validated idea into a page that converts, or says 'build me a landing page for my SaaS'. Site already exists: use improve-website to fix conversion/UX or grow-website for more traffic; building a software product, not a marketing site: use create-app; no positioning yet: run create-business first or the positioning phase here. For one framework in isolation, invoke that skill directly.