메뉴
Challenge every decision in a design or codebase by asking "Why not do it this other way instead?" one alternative at a time, with pros/cons and a final recommendation. Use when user wants to stress-test decisions, explore alternatives, or mentions "why not".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | why-not |
| description | Challenge every decision in a design or codebase by asking "Why not do it this other way instead?" one alternative at a time, with pros/cons and a final recommendation. Use when user wants to stress-test decisions, explore alternatives, or mentions "why not". |
For every decision in this design/code, ask: "Why not do it this other way instead?" One alternative at a time. Give the pros/cons of your alternative and your final recommendation.
If a decision can be better understood by exploring the codebase, explore the codebase instead.
Design and build world-class SaaS onboarding flows grounded in behavioral science. Covers Aha Moment identification, 7 architecture patterns (including mobile-native), segmented flows, multi-channel sequences (in-app + email + human), copy frameworks, framework-agnostic UI component standards, analytics instrumentation, and A/B testing playbooks. Make sure to use this skill whenever the user mentions onboarding, activation, trial-to-paid conversion, time-to-first-value, TTFV, signup flows, product-led growth, PLG, user activation, first-run experience, welcome flow, setup wizard, onboarding checklist, empty states, mobile app onboarding, push notification opt-in, or wants to improve how new users experience their SaaS product — even if they don't explicitly say "onboarding."
Audit naming in a codebase by finding one inconsistency, ambiguity, or bad name at a time, proposing a better name and explaining why it improves the code. Waits for approval before moving on. Use when user wants to improve naming, audit identifiers, or mentions "name-guard".
Analyze code for performance by identifying one bottleneck or hot path at a time, explaining why it matters, and proposing the exact optimized version. Waits for approval before moving to the next. Use when user wants to optimize performance, profile code, or mentions "perf-tune".
Relentlessly simplify code, concepts, or decisions by asking "Is this strictly necessary?" one question at a time. Use when user wants to reduce complexity, cut unnecessary code, or mentions "simplify me".
