designedbythanh

acceptance-criteria

Turn a user story into airtight Given/When/Then acceptance criteria covering happy path, errors, and edge cases. Use to define "done" before engineering starts building.

assumption-reversal

Flip your current design assumptions 180° and generate concrete ideas from the reversed perspective. Use when stuck on ideas or wanting to pressure-test the current design direction.

Find 3 solutions from unrelated industries that solve a structurally similar problem, and translate the strongest one into a concrete idea. Use when stuck on ideas or need fresh inspiration outside the category.

Data & Documents Listed

data-interpretation

Interpret metrics or experiment results by separating fact from explanation and ruling out alternative causes before recommending action. Use when reviewing results and need to draw a real conclusion, not just eyeball a chart.

DevOps & Infrastructure Listed

decision-rationale

Document a design decision between 2 options with explicit criteria, scenario testing, and a confidence-rated recommendation. Use when torn between two directions and need a defensible, written rationale - not just a gut call.

design-critique-facilitator

Facilitate a structured design critique across 4 lenses (clarity, hierarchy, consistency, edge cases), separating what's working from what needs attention. Use when presenting work for feedback, to get specific critique instead of vague opinions.

design-scope-negotiator

Sort a design scope into Ship / Fast-follow / Cut buckets using effort vs. impact-if-removed, with opinionated reasoning for each. Use when pushing back on scope creep or negotiating what gets cut before a deadline.

edge-case-finder

Stress-test a feature across 5 failure dimensions (input, permissions, concurrency, dependencies, user behavior) before it ships. Use before handing a spec to engineering, to catch what breaks.

experiment-design

Design a full, statistically-honest experiment plan - hypothesis, control/variant, duration, decision rule - and flag if traffic is too low for a reliable result. Use when planning an A/B test or any product experiment.

explain-to-4-audiences

Translate one design decision into 4 audience-specific explanations (10-year-old, engineering, executive, end user) to pressure-test whether it's actually clear. Use after designing, before presenting, writing docs, or shipping.

five-whys-root-cause

Dig past a stakeholder's feature request to the real underlying need, using 5 consecutive Why questions, then surface alternative solutions. Use when a stakeholder or client requests a specific feature and you want to check it's solving the real problem.

Testing & QA Listed

persona-pretest

Simulate how a specific user persona would react to a design or flow, surfacing likely confusion, objections, and drop-off points before real user testing. Use when you want a fast sanity check on a design before investing in a usability study.

prd-first-draft

Write a PRD first draft that's clear enough for engineers to build from and concise enough for executives to read in 5 minutes. Use when starting to spec a feature or product.

success-metrics-definition

Design a metrics framework (primary metric, leading/lagging indicators, counter-metrics) that proves a feature solved the real problem, not just that it was used. Use when defining what success looks like before building.

user-interview-synthesis

Turn messy interview notes from multiple users into ranked insights, frustrations, and unspoken needs. Use after collecting raw notes from user interviews.