Real-world scenarios showing which skills to use and how to combine them. Each prompt is copy-pasteable.
New here? See README.md for installation and the full skill catalog.
You have an idea, limited runway, and need to move fast. These scenarios walk you from validating a concept through pricing, positioning, and acquiring your first users.
You have a hunch for a B2B product but aren't sure if the pain is real or just your own projection.
Prompt:
I'm building a tool that helps freelancers track unpaid invoices.
Before I write any code, help me uncover the real Job to Be Done.
Who are the likely hiring managers, what's the struggling moment
that triggers the search for a solution, and what competing "hires"
(including non-consumption) should I worry about?
Then design a 10-question customer discovery interview guide
I can use this week.
Use jobs-to-be-done skill.
Skills used: jobs-to-be-done
You've validated demand but don't know what to cut to ship fast.
Prompt:
Here's everything our invoice-tracking tool could do:
[paste feature list].
Identify our riskiest assumption and design the smallest possible
MVP that tests it. Give me a Build-Measure-Learn experiment card
with hypothesis, metric, and success threshold.
Then outline a 5-day sprint plan to go from sketches
to a testable prototype.
Use lean-startup and design-sprint skills.
Skills used: lean-startup, design-sprint
You're guessing at a price point and worried about leaving money on the table.
Prompt:
Our invoice-tracking SaaS saves freelancers an average of
5 hours/month chasing payments and recovers ~$2,000 in late
invoices per quarter.
Using the Value Equation, help me set a price that delivers
at least 10:1 perceived value.
Then design a Grand Slam Offer with 3 bonuses,
a risk-reversing guarantee, and ethical urgency.
Use hundred-million-offers skill.
Skills used: hundred-million-offers
Prospects keep saying "we just use Excel" or comparing you to a large competitor.
Prompt:
Our competitive alternatives aren't just other invoice tools —
freelancers also use spreadsheets, sticky notes, and "just remembering."
Walk me through the Obviously Awesome positioning exercise:
- List competitive alternatives
- Identify our unique attributes
- Map them to value themes
- Define our best-fit customer segment
- Recommend whether we should position in an existing category
or create a subcategory
Then write positioning for pragmatist buyers who need proof
before switching.
Use obviously-awesome and crossing-the-chasm skills.
Skills used: obviously-awesome, crossing-the-chasm
Every niche seems taken and you're struggling to differentiate.
Prompt:
Here are the top 6 competitors in the freelancer finance space
and the factors they compete on: [paste list].
Build a Strategy Canvas plotting all of us.
Then apply the Four Actions Framework (Eliminate-Reduce-Raise-Create)
to find a blue ocean move we can make with limited resources.
Use blue-ocean-strategy skill.
Skills used: blue-ocean-strategy
Your demo day pitch is in a week and it needs to be crisp and memorable.
Prompt:
Here's our current 2-minute pitch: [paste draft].
Score it on the SUCCESs checklist (Simple, Unexpected, Concrete,
Credible, Emotional, Stories).
Rewrite it so the core message passes the "Commander's Intent" test —
if investors remember only one thing, what should it be?
Make the opening unexpected and the proof concrete.
Use made-to-stick skill.
Skills used: made-to-stick
You've launched but have zero marketing budget and need word-of-mouth.
Prompt:
We just launched our freelancer invoice tool. Budget is $0.
Design a launch strategy that combines:
(1) A STEPPS-based referral mechanic built into the product —
what's the Social Currency for users who share?
(2) A simple 1-page marketing plan covering target market, message,
and the 3 cheapest media channels for reaching freelancers.
Use contagious and one-page-marketing skills.
Skills used: contagious, one-page-marketing
You've been pitching your idea in meetings and everyone says "that's a great idea!" but nobody's buying.
Prompt:
I've talked to 20 potential customers about my project
management tool for construction teams. They all said
they'd use it. But when I launched a landing page,
only 2 signed up.
Review my interview approach using Mom Test rules:
- Am I talking about their life or pitching my idea?
- Am I asking about specifics in the past or hypotheticals?
- Am I deflecting compliments and digging into real behavior?
Then rewrite my 5 key interview questions so they extract
signal without leading the witness.
Use mom-test skill.
Skills used: mom-test
You're pre-revenue and talking to users sporadically — some weeks a lot, some weeks not at all.
Prompt:
I'm a solo founder building an expense-tracking app
for freelancers. I talk to users when I remember to,
but there's no system.
Help me set up a sustainable weekly discovery cadence:
(1) Build an Opportunity Solution Tree with my desired
outcome at the top, opportunities in the middle,
and solution ideas at the bottom
(2) Design a 20-minute interview snapshot template
I can use in 2 calls per week
(3) Show me how to run Mom Test-compliant questions
within that snapshot format
Use continuous-discovery and mom-test skills.
Skills used: continuous-discovery, mom-test
You're past product-market fit and focused on retention, feature prioritization, team alignment, and competitive moats.
60% of signups never complete setup, and you don't know why.
Prompt:
Here's our 5-step onboarding flow: [describe steps].
Diagnose the drop-off using B=MAP — for each step, assess whether
the barrier is:
- Motivation (do they want to?)
- Ability (can they do it easily?)
- Prompt (are we asking at the right moment?)
Then map each step to the Hook Model — are we completing a full
Trigger→Action→Reward→Investment cycle before asking users
to come back?
Give me a prioritized fix list.
Use improve-retention and hooked-ux skills.
Skills used: improve-retention, hooked-ux
Your backlog has 40 feature requests and stakeholders are pulling in different directions.
Prompt:
Here's our feature backlog: [paste top 15 requests].
For each, identify the underlying Job to Be Done — what progress
is the customer trying to make?
Group features by job, then rank the jobs by frequency
and importance.
Finally, turn the top 3 jobs into SMART quarterly Rocks
we can commit to.
Use jobs-to-be-done and traction-eos skills.
Skills used: jobs-to-be-done, traction-eos
A well-funded competitor just launched a similar product and your sales team is panicking.
Prompt:
A new competitor just raised $20M and launched a product that
overlaps with 60% of our features.
Help me re-run our positioning:
- What are the competitive alternatives now?
- What unique attributes do we still own?
- Which customer segment values those attributes most?
Write a short internal positioning brief the sales team can use
on calls starting tomorrow.
Use obviously-awesome skill.
Skills used: obviously-awesome
Users love the product during their first session but don't come back the next day.
Prompt:
Our task management app has high Day-1 engagement but Day-7
retention is 18%.
Design a Hook cycle:
- What internal trigger should we attach to (emotion/routine)?
- What's the simplest core action?
- What variable reward keeps it interesting?
- What investment makes the product better with use?
Then create a Tiny Habits recipe
(After I [anchor], I will [tiny behavior])
for our ideal daily action.
Use hooked-ux and improve-retention skills.
Skills used: hooked-ux, improve-retention
You've grown from 5 to 25 people and coordination is breaking down.
Prompt:
We're a 25-person SaaS company and teams are drifting.
Help me create:
(1) A Vision/Traction Organizer with our 10-year target,
3-year picture, and 1-year plan
(2) A team structure evaluation — are people in the right seats?
Then audit our current incentive structure using
Autonomy-Mastery-Purpose: are we accidentally using controlling
rewards that undermine intrinsic motivation?
Use traction-eos and drive-motivation skills.
Skills used: traction-eos, drive-motivation
Users constantly misconfigure a critical settings panel and then blame the product.
Prompt:
Here's our settings panel: [describe or paste screenshot path].
Users frequently select the wrong options, leading to
support tickets.
Analyze using Norman's framework:
- What affordances are misleading?
- What signifiers are missing?
- Where is the conceptual model mismatched with the user's
mental model?
Recommend constraints that make errors impossible rather than
just showing error messages.
Use design-everyday-things skill.
Skills used: design-everyday-things
You have 3,000 churned users and want to re-engage the salvageable ones.
Prompt:
We have 3,000 users who churned in the last 90 days.
Help me design a win-back campaign:
(1) Segment churned users by their last completed action
to identify who's salvageable
(2) Diagnose the likely B=MAP failure for each segment
(3) Design a STEPPS-based re-engagement email that gives them
social currency for returning ("You're in the top 10%
of power users who...")
Use improve-retention and contagious skills.
Skills used: improve-retention, contagious
Your team ships whatever stakeholders request, but nobody measures outcomes and morale is dropping.
Prompt:
Our product team is a feature factory — we take requests
from sales and executives, build them, and move on.
Nobody tracks whether features actually move metrics.
Help me design a transition plan:
(1) Assess our current team against Cagan's empowered team
model — do we have a product manager, designer,
and engineers with decision-making authority?
(2) Create an opportunity assessment template for the next
3 feature requests in our backlog
(3) Draft a product vision statement that gives the team
strategic context to make their own prioritization decisions
Use inspired-product skill.
Skills used: inspired-product
You do user research in big batches before major releases but lose touch with customers in between.
Prompt:
We do a big research sprint every quarter but go weeks
without talking to a single customer in between.
Set up a continuous discovery system:
(1) Create an Opportunity Solution Tree for our Q3 goal
of reducing churn by 20%
(2) Design an assumption map — what are our riskiest
assumptions and how do we test them cheaply?
(3) Build a weekly interview snapshot template that
our PM can run in 2 customer calls per week
Then show me how to integrate this with our 2-week
sprint cycle using Lean UX hypothesis statements.
Use continuous-discovery and lean-ux skills.
Skills used: continuous-discovery, lean-ux
Your team debates design decisions endlessly — you need a framework to test instead of argue.
Prompt:
Our team spent 3 weeks debating whether to redesign
our onboarding flow. We have two competing mockups
and no data.
Help me turn this into a Lean UX experiment:
(1) Write a hypothesis statement: "We believe that
[change] for [users] will achieve [outcome]
as measured by [metric]"
(2) Design the smallest possible MVP to test it
(not a full redesign)
(3) Define success criteria and a timeline
Then show me how to run a collaborative design studio
so both sides feel heard before we test.
Use lean-ux skill.
Skills used: lean-ux
Users say your app "works fine" but nobody describes it as "delightful" or recommends it to friends.
Prompt:
Our task management app is functional but feels flat.
Users complete tasks but never say "I love this product."
Audit these 5 key interactions for micro-interaction
opportunities:
- Completing a task (checkbox)
- Adding a new item
- Switching between views
- Receiving a notification
- Reaching inbox zero
For each, design the micro-interaction using
Trigger → Rules → Feedback → Loops/Modes.
What feedback makes the action feel satisfying?
What loop keeps them coming back?
Use microinteractions skill.
Skills used: microinteractions
You're optimizing funnels, writing copy, running campaigns, and obsessing over conversion rates.
Your landing page gets traffic but converts at 1.2% and you don't know where it's leaking.
Prompt:
Here's our landing page: [paste URL or describe layout].
Run a full CRO audit:
- Identify the top 5 visitor objections this page fails to address
- List missing persuasion assets (testimonials, guarantees,
credentials, specificity)
- Check which of Cialdini's 7 influence principles are absent
Prioritize fixes by expected impact.
Use cro-methodology and influence-psychology skills.
Skills used: cro-methodology, influence-psychology
Your PDF lead magnet converts at 4% and you want something better.
Prompt:
We sell marketing automation software to agencies.
Design a complete scorecard funnel:
(1) A quiz concept with a compelling title using the 3 Cs formula
(2) 12 assessment questions across 4 categories that qualify leads
by maturity level
(3) Landing page copy
(4) Three result-tier descriptions (Beginner/Intermediate/Advanced)
with tailored CTAs for each
Use scorecard-marketing skill.
Skills used: scorecard-marketing
You're launching a new feature and want organic buzz, not just paid ads.
Prompt:
We're launching a collaborative whiteboard tool next month.
Audit our launch plan against the STEPPS framework:
- Where's the Social Currency (what makes sharing feel like bragging)?
- What Trigger will link us to a daily routine?
- What's our Trojan Horse Story?
Then make the core message sticky using the SUCCESs checklist —
rewrite our launch tagline to be Simple, Unexpected, and Concrete.
Use contagious and made-to-stick skills.
Skills used: contagious, made-to-stick
You're capturing emails but have no follow-up system — leads go cold.
Prompt:
We capture leads through a free trial signup.
Design a 7-email nurture sequence using the StoryBrand framework:
- Email 1: Establish the customer's problem
- Emails 2-5: Position us as the guide with a plan
- Emails 6-7: Direct CTA and consequences of inaction
Also map this sequence to the "During" phase (nurture → convert)
of the 1-Page Marketing Plan.
Use storybrand-messaging and one-page-marketing skills.
Skills used: storybrand-messaging, one-page-marketing
People visit the pricing page but don't click "Start Trial" — you suspect it's the offer structure.
Prompt:
Here's our current pricing page: [describe tiers and pricing].
Audit it twice:
(1) Using CRO methodology, create an objection/counter-objection
table for each tier — what's stopping people from clicking?
(2) Using the Value Equation, evaluate whether each tier's perceived
value justifies the price.
Suggest restructured tiers with bonus stacking and a guarantee
that reverses risk.
Use cro-methodology and hundred-million-offers skills.
Skills used: cro-methodology, hundred-million-offers
You're relying on one channel and need to diversify before it dries up.
Prompt:
We currently get 80% of leads from Google Ads.
Using the 1-Page Marketing Plan's "Before" phase, help me:
- Define our ideal customer using the PVP Index
(Personal fulfillment, Value, Profitability)
- Craft a USP that differentiates us
- Select 3 additional media channels worth testing
For one of those channels, design a scorecard lead magnet
that qualifies leads automatically.
Use one-page-marketing and scorecard-marketing skills.
Skills used: one-page-marketing, scorecard-marketing
You have testimonials on your site but they feel generic and ignorable.
Prompt:
Here are our 10 best customer testimonials: [paste them].
Evaluate each against Cialdini's social proof principle —
which ones are specific, relatable, and from credible sources?
Rewrite the weakest 3 to be concrete and outcome-focused.
Then recommend placement on the page using CRO methodology
(where objections peak, social proof should appear).
Use influence-psychology and cro-methodology skills.
Skills used: influence-psychology, cro-methodology
You're designing interfaces, auditing usability, choosing type, and building experiences that feel effortless.
You inherited a product and need to quickly identify the worst UX problems.
Prompt:
Here's our web app's main dashboard and settings flow:
[describe or paste screenshot path].
Run a dual audit:
(1) Apply Nielsen's 10 heuristics and rate each violation
0-4 severity
(2) Check for missing affordances and signifiers using Norman's
framework — where might users not realize something is
clickable, draggable, or editable?
Combine findings into a single prioritized fix list.
Use ux-heuristics and design-everyday-things skills.
Skills used: ux-heuristics, design-everyday-things
Users complain the app feels "hard to read" but you can't pinpoint why.
Prompt:
Here's our current CSS for body text and headings: [paste styles].
Evaluate the typeface choices for screen readability, check
line-height, measure, and font-size ratios.
Recommend a type scale that creates clear hierarchy.
Then apply Refactoring UI's hierarchy principles — are we relying
too much on font-size alone instead of weight, color, and spacing?
Deliver updated CSS.
Use web-typography and refactoring-ui skills.
Skills used: web-typography, refactoring-ui
You're building an iPhone app and want it to feel like it belongs on the platform.
Prompt:
We're designing a recipe-saving app for iOS.
Review our current wireframes: [describe screens].
Check:
- Navigation patterns (tab bar, sidebar, or navigation stack?)
- Touch targets meet 44pt minimum
- Dynamic Island and safe areas handled correctly
- Where to use standard SF Symbols vs. custom icons
Use ios-hig-design skill.
Skills used: ios-hig-design
Users complete onboarding but never develop a daily usage pattern.
Prompt:
Our project management app has a 4-screen onboarding wizard.
Users complete it but only 15% return on Day 3.
Redesign the onboarding so it completes a full Hook cycle
(Trigger→Action→Variable Reward→Investment) before the user leaves.
For each screen, identify what tiny behavior we should prompt
and how to celebrate completion so users feel successful.
Use hooked-ux and improve-retention skills.
Skills used: hooked-ux, improve-retention
Your product is great but the website looks like a template — you want it to feel premium.
Prompt:
We need a marketing site for a design tool that competes
with Figma and Framer.
Design a homepage that would score on Awwwards:
- Typography system (dramatic scale contrast, custom font pairing)
- Hero section composition
- Scroll-based reveal strategy
- Micro-interactions
Specify exact CSS properties for the type scale, spacing rhythm,
and animation easing curves.
Use top-design skill.
Skills used: top-design
Your app has 12 different button styles, 4 shades of gray, and no spacing system.
Prompt:
Here's a list of our current UI components:
[paste component names and descriptions].
Audit them using Refactoring UI principles:
- Define a constrained spacing scale (e.g., 4/8/12/16/24/32/48/64)
- A color palette with 9 shades per hue
- A type scale with clear hierarchy levels
Then create a decision framework: when to use primary
vs. secondary vs. tertiary button styles.
Use refactoring-ui skill.
Skills used: refactoring-ui
You need to pass an accessibility review before an enterprise deal closes.
Prompt:
Here's our main user flow: [describe 5 key screens].
Audit for accessibility:
- Color contrast ratios against WCAG AA
- All interactive elements have proper labels for VoiceOver
- Dynamic Type support
- Touch targets are at least 44pt
Then run the Trunk Test on each screen — can a VoiceOver user
answer "What app is this? What page am I on? What can I do here?"
Use ios-hig-design and ux-heuristics skills.
Skills used: ios-hig-design, ux-heuristics
Your checkout flow is functional but feels mechanical — users hesitate at the payment step.
Prompt:
Here's our 4-step checkout flow:
Cart → Shipping → Payment → Confirmation.
Conversion drops 30% at the Payment step.
Design micro-interactions that build confidence
and reduce hesitation:
For each step, specify:
- Trigger: what initiates the interaction?
- Rules: what happens and what are the edge cases?
- Feedback: how does the user know it worked?
- Loops: does anything change on repeat visits?
Pay special attention to the payment button —
what feedback happens between click and confirmation?
Use microinteractions and ux-heuristics skills.
Skills used: microinteractions, ux-heuristics
Stakeholders want a complete redesign, but you suspect targeted changes would be more effective.
Prompt:
Leadership wants a full redesign of our dashboard.
I think 80% of it works fine and we should only fix
the broken parts.
Help me make the case with a Lean UX approach:
(1) Identify assumptions behind the "full redesign" plan
(2) Write 3 hypothesis statements for targeted experiments
we can run in 2 weeks instead of 3 months
(3) Design a minimum viable experiment for the riskiest
hypothesis
(4) Define success metrics that prove whether the targeted
approach works before committing to a full redesign
Use lean-ux and ux-heuristics skills.
Skills used: lean-ux, ux-heuristics
You're building pipeline, closing deals, handling objections, and scaling a sales organization.
You're hiring your first SDR and need a repeatable outbound playbook.
Prompt:
We sell a $15K/year B2B analytics platform to mid-market companies.
Design a Cold Calling 2.0 outbound process:
- Define the ideal customer profile
- Write a 3-email prospecting sequence targeting referrals
(not decision-makers)
- Create a lead qualification framework
- Calculate the pipeline math — how many emails per day
to generate 5 qualified meetings per week?
Use predictable-revenue skill.
Skills used: predictable-revenue
Prospects keep saying "the price is too high" and your reps don't know how to respond.
Prompt:
Our top 3 sales objections are:
- "It's too expensive"
- "We need to think about it"
- "We're already using [competitor]"
For each objection, write a response using tactical empathy:
start with a label ("It sounds like..."), follow with a calibrated
question ("How" or "What"), and aim for a "That's right" moment.
Then identify which Cialdini principle (commitment, social proof,
scarcity) to deploy alongside each response.
Use negotiation and influence-psychology skills.
Skills used: negotiation, influence-psychology
Your sales cycle is 45 days and prospects keep "needing more time."
Prompt:
Our product is a $2,000/month marketing platform.
The core offer is just "access to the software."
Rebuild it as a Grand Slam Offer:
- Stack 3-4 bonuses that solve adjacent problems
(onboarding, templates, strategy call)
- Add a risk-reversing guarantee that makes saying yes
feel safer than saying no
- Create ethical urgency
Name the new offer using the MAGIC formula.
Use hundred-million-offers skill.
Skills used: hundred-million-offers
A key customer is threatening to leave over price and your instinct is to discount.
Prompt:
Our largest customer ($180K/year) says they've received
a competing bid at 30% less.
Help me prepare:
- Write an accusation audit for the renewal meeting
- Draft 5 calibrated questions to uncover what's really
driving the switch
- Design an Ackerman bargaining plan with my target price,
three decreasing increments, and a non-monetary concession
to throw in at the end
Use negotiation skill.
Skills used: negotiation
Leadership wants $2M in new ARR next quarter and you need to staff accordingly.
Prompt:
We need $2M in new ARR next quarter.
Our average deal size is $24K, close rate is 25%, and it takes
4 qualified opportunities to close 1 deal.
SDRs currently generate 15 qualified meetings/month.
Walk me through the pipeline math:
- How many SDRs, AEs, and total pipeline do we need?
- What's the right team structure (SDR:AE ratio)?
- Should we hire or redistribute?
Use predictable-revenue skill.
Skills used: predictable-revenue
Reps present a 20-slide deck and prospects forget everything by the next call.
Prompt:
Here's our sales deck outline: [paste slide titles].
Score each slide on the SUCCESs framework.
Rewrite the opening 3 slides to:
- Lead with an Unexpected insight
- Make our differentiator Concrete with a specific customer story
- Close with a clear Emotional appeal
Then restructure the narrative using the StoryBrand framework —
customer as hero, us as guide, a clear plan, and consequences
of inaction.
Use made-to-stick and storybrand-messaging skills.
Skills used: made-to-stick, storybrand-messaging
You've won early adopters but enterprise prospects want "whole product" solutions.
Prompt:
We have 50 startup customers but just got our first 3 enterprise
inbound leads.
Using the Chasm framework: are we ready for pragmatist buyers?
Map our current product against the "whole product" model —
what's missing (integrations, SLAs, onboarding, migration support)?
Then identify a beachhead segment where we can win a dominant
position before expanding.
Use crossing-the-chasm skill.
Skills used: crossing-the-chasm
You're writing brand copy, headlines, email sequences, and content that needs to resonate and spread.
You're rewriting an entire website and need a messaging foundation first.
Prompt:
We're a meal-kit delivery service for busy parents.
Walk me through the full StoryBrand framework:
- Who is the hero (customer)?
- What do they want?
- What's the external/internal/philosophical problem?
- How do we position as the guide (empathy + authority)?
- What's the 3-step plan?
- What's the direct CTA?
- What's at stake (success vs. failure)?
Deliver a complete brand script I can hand to a copywriter.
Use storybrand-messaging skill.
Skills used: storybrand-messaging
Your blog posts get clicks but readers can't remember what they read.
Prompt:
Here are our last 10 blog post headlines: [paste list].
Score each on the SUCCESs framework and identify which principle
is weakest across the set.
Then rewrite the bottom 5 to be stickier — each should use
a different principle:
- One Simple
- One Unexpected
- One Concrete
- One Credible
- One Emotional
Use made-to-stick skill.
Skills used: made-to-stick
You publish weekly but nothing gets shared beyond your existing audience.
Prompt:
Here's our last 5 social media posts: [paste content].
Audit each against the STEPPS framework.
Then create 3 new content pieces designed for virality:
- One that gives Social Currency (insider knowledge)
- One with a strong Trigger tied to a weekly routine
- One wrapped in a Trojan Horse Story that people retell naturally
Use contagious skill.
Skills used: contagious
You have customer results but your copy doesn't use them persuasively.
Prompt:
Here are 5 customer success metrics: [paste data points].
Turn each into a persuasive copy block using Cialdini's principles:
- Social proof (how many others achieved this)
- Authority (who endorses this)
- Specificity (exact numbers, not "many customers")
Write them as modular sections I can drop into landing pages,
emails, or ads.
Use influence-psychology skill.
Skills used: influence-psychology
You're doing random acts of marketing with no strategy behind your content.
Prompt:
We're a B2B HR tech company targeting companies
with 50-200 employees.
Using the 1-Page Marketing Plan, fill out all 9 squares
but focus on the content strategy for each phase:
- Before: What content attracts prospects?
- During: What content nurtures leads?
- After: What content turns customers into advocates?
Give me a 90-day content calendar with 2 pieces per week.
Use one-page-marketing skill.
Skills used: one-page-marketing
You have 5,000 free users and no email nurture — you're leaving money on the table.
Prompt:
We have 5,000 freemium users who've been active for 30+ days.
Design a 5-email conversion sequence:
- Use StoryBrand's narrative arc (problem → guide → plan → CTA)
as the overall structure
- Within each email, apply the SUCCESs checklist to make
the message sticky
Email 1 should name their frustration.
Email 5 should paint the consequences of staying on the free plan.
Use storybrand-messaging and made-to-stick skills.
Skills used: storybrand-messaging, made-to-stick
You're launching a major feature and the announcement needs to generate buzz and press coverage.
Prompt:
We're launching AI-powered reporting in our analytics platform.
Write a launch announcement optimized for sharing:
- Build Social Currency (make early adopters feel like insiders)
- Create a Trigger phrase that links to their daily workflow
- Wrap the feature story in an Emotional narrative about
the pain of manual reporting
Write three versions:
1. A press release
2. A tweet thread
3. An email to existing customers
Use contagious and influence-psychology skills.
Skills used: contagious, influence-psychology
You're wearing every hat — marketing, design, sales, product. These scenarios help you do it all without a team.
You have no marketing plan and need one before you burn more money on random tactics.
Prompt:
I run a one-person web design studio targeting local restaurants.
Walk me through the complete 1-Page Marketing Plan:
- Before: Who's my ideal customer using PVP? What's my USP?
Which 2 channels should I focus on?
- During: How do I capture leads? What's my nurture sequence?
How do I convert?
- After: How do I deliver a great experience? Increase lifetime
value? Generate referrals?
Keep everything executable by one person.
Use one-page-marketing skill.
Skills used: one-page-marketing
Your site looks "homemade" and you can't afford a designer.
Prompt:
Here's my current website: [describe layout and styles].
Audit it using Refactoring UI principles:
- Fix the visual hierarchy (am I using size, weight,
and color correctly?)
- Constrain my spacing to a proper scale
- Simplify the color palette
Then evaluate my typography: is my body font readable
at the current size and line-height, and does my heading/body
pairing work?
Give me the exact CSS changes to make.
Use refactoring-ui and web-typography skills.
Skills used: refactoring-ui, web-typography
You know your product is different but can't articulate why in a way customers care about.
Prompt:
I built a CRM specifically for real estate agents.
My competitors are Salesforce, HubSpot, and spreadsheets.
Walk me through the Obviously Awesome positioning exercise solo:
- List competitive alternatives
- Identify my unique attributes
- Run the "So what?" test to map attributes to value
- Define my best-fit customer segment
- Pick the right market category
Write a one-paragraph positioning statement I can use everywhere.
Use obviously-awesome skill.
Skills used: obviously-awesome
You need leads but don't have time to write a 30-page ebook.
Prompt:
I'm a business coach for first-time founders.
Create a complete scorecard funnel I can build this weekend:
- A quiz title using the 3 Cs formula
- 10 questions across 4 categories
- Scoring logic with 3 result tiers
- Landing page headline and subhead
- A 3-email follow-up sequence customized per tier
Keep everything simple enough to implement in a tool
like Typeform or ScoreApp.
Use scorecard-marketing skill.
Skills used: scorecard-marketing
You sell hourly consulting and clients always haggle on price.
Prompt:
I charge $150/hour for marketing consulting and clients
constantly negotiate me down.
Help me restructure my services as a Grand Slam Offer:
- Package my consulting into a fixed-price "Marketing Sprint"
with a clear deliverable
- Stack 3 bonuses (templates, recordings, follow-up)
- Add a guarantee that eliminates risk
- Apply ethical scarcity (limited to 5 clients/month)
Use the MAGIC naming formula for the package name.
Use hundred-million-offers skill.
Skills used: hundred-million-offers
Users sign up for your app but stop using it after the first week.
Prompt:
I run a solo habit-tracking app with 500 users.
Day-1 retention is 40%, Day-7 is 12%.
I can't hire engineers, so solutions must be simple
(email, push notifications, UI copy changes).
Diagnose the problem using B=MAP:
- Is my core action too hard (Ability)?
- Poorly timed (Prompt)?
- Not motivating enough (Motivation)?
Design 3 low-effort interventions I can implement with email
automation and a simple UI tweak.
Use improve-retention skill.
Skills used: improve-retention
You're ready to launch but don't know whether to go niche or broad.
Prompt:
I built a project management tool for architecture firms.
I have $0 marketing budget and no team.
Help me decide: should I target a narrow beachhead segment
(small firms, 5-10 people) and dominate it before expanding,
or go broad?
Map my current product against the "whole product" requirements
for my target segment.
Then apply the ERRC grid to differentiate from Asana
and Monday.com without needing more features.
Use crossing-the-chasm and blue-ocean-strategy skills.
Skills used: crossing-the-chasm, blue-ocean-strategy
You write code every day — feature work, bug fixes, refactoring, and reviews. These scenarios help you write cleaner, more maintainable software.
A teammate submitted a 400-line pull request and you want to give useful feedback beyond "looks fine."
Prompt:
Here's a module from our codebase: [paste code or file path].
Review it using Clean Code principles:
- Are the names meaningful and intention-revealing?
- Are functions small and doing one thing?
- Are there comments that should be code instead?
- Is error handling clean (no swallowed exceptions,
no returning null)?
Score it 0-10 and list the top 5 improvements
in priority order.
Use clean-code skill.
Skills used: clean-code
You need to add a feature to a 200-line function but you're afraid to touch it because it's fragile.
Prompt:
Here's a function I need to modify: [paste code].
It's too long, has nested conditionals, and no tests.
Before I add my feature, help me refactor it safely:
(1) Identify the code smells (Long Method, Feature Envy,
Divergent Change, etc.)
(2) Suggest a sequence of named refactoring transformations
(Extract Method, Replace Conditional with Polymorphism, etc.)
(3) Tell me which tests to write BEFORE each transformation
so I don't break anything
Apply the transformations one at a time.
Use refactoring-patterns skill.
Skills used: refactoring-patterns
You inherited a module with 15 tiny classes, 8 interfaces, and 3 levels of abstraction for what should be a simple feature.
Prompt:
Here's a module that handles user notifications:
[paste code or describe structure].
It has too many layers and abstractions for what it does.
Analyze it using A Philosophy of Software Design:
- Which classes are "shallow" (complex interface,
simple implementation)?
- Where is information leaking between modules?
- Are we programming "tactically" (quick hacks)
or "strategically" (managing complexity)?
Recommend how to consolidate into deeper modules
with simpler interfaces.
Use software-design-philosophy skill.
Skills used: software-design-philosophy
You're starting a greenfield project and want to set up good habits from the start.
Prompt:
I'm starting a new backend service in [language/framework].
Before I write code, help me apply pragmatic principles:
- What's my "tracer bullet" — the thinnest possible
end-to-end slice I should build first?
- How do I keep the architecture orthogonal so changing
one thing doesn't break another?
- Where should I apply DRY and where should I tolerate
duplication (hint: across service boundaries)?
- What reversibility decisions should I make now
vs. defer?
Give me a project setup checklist.
Use pragmatic-programmer skill.
Skills used: pragmatic-programmer
You're building an e-commerce system and every meeting uses different terms for the same concepts.
Prompt:
We're building an order management system and the team
uses "order," "purchase," "transaction," and "booking"
interchangeably. Checkout, warehouse, and billing
each have different assumptions about what an "order" is.
Help me apply DDD:
(1) Define the Ubiquitous Language — one glossary
the whole team agrees on
(2) Identify Bounded Contexts — where do the meanings
of "order" legitimately differ?
(3) Design the Aggregates for the checkout context —
what's the aggregate root and what are the invariants?
(4) Map the relationships between contexts
(shared kernel, customer-supplier, anti-corruption layer)
Use domain-driven-design skill.
Skills used: domain-driven-design
You're designing a new service and defaulting to PostgreSQL because "that's what we always use."
Prompt:
We're building a service that handles:
- User profiles (relational, read-heavy)
- Activity feeds (time-series, write-heavy)
- Product recommendations (graph relationships)
- Full-text search across 10M documents
Should we use one database or multiple?
For each workload, evaluate:
- Which data model fits best (relational, document, graph)?
- What storage engine characteristics matter
(B-tree vs LSM tree)?
- What replication and partitioning strategy
do we need at our scale?
- What consistency level is required?
Use ddia-systems skill.
Skills used: ddia-systems
Your web app takes 6 seconds to load and Core Web Vitals are all red.
Prompt:
Our web app scores 35 on Lighthouse. LCP is 5.2s,
INP is 380ms, and CLS is 0.42.
Run a systematic performance diagnosis:
(1) Network: are we making too many round trips?
Should we add preconnect, preload, or HTTP/2?
(2) Critical rendering path: what's blocking first paint?
Which scripts should be deferred?
(3) Caching: are static assets properly cached
with content hashes?
(4) Core Web Vitals: what specific changes will bring
LCP under 2.5s, INP under 200ms, and CLS under 0.1?
Prioritize fixes by impact.
Use high-perf-browser skill.
Skills used: high-perf-browser
You design systems, review architecture, mentor engineers, and make decisions that are expensive to reverse.
You need to design a system that handles 100M URLs and 10K redirects/second.
Prompt:
Design a URL shortener that supports:
- 100M stored URLs
- 10K reads/second, 100 writes/second
- Custom aliases
- Analytics (click counts, referrer, location)
Walk me through the structured approach:
(1) Back-of-the-envelope estimation: storage, bandwidth,
QPS, cache sizing
(2) High-level design: API, database schema, encoding strategy
(3) Deep dive: how to generate unique short codes,
handle collisions, and scale reads with caching
(4) Bottleneck analysis: what breaks first at 10x load?
Use system-design skill.
Skills used: system-design
You're about to launch a new service and the last launch caused a 2-hour outage.
Prompt:
We're launching a new payment processing service next week.
Our last launch took down the checkout for 2 hours.
Audit our production readiness:
(1) Stability: do we have circuit breakers, timeouts,
and bulkheads on every integration point?
(2) Deployment: can we deploy with zero downtime
and roll back in under 60 seconds?
(3) Observability: do our health checks verify
dependency connectivity? Are we alerting on
symptoms (error rate) not causes (CPU)?
(4) Capacity: have we load tested to 3x expected peak?
Give me a pre-launch checklist with pass/fail criteria.
Use release-it skill.
Skills used: release-it
Your monolith is becoming a big ball of mud — everything depends on everything.
Prompt:
Our Node.js monolith has grown to 200 files and we can't
change the payment logic without breaking the notification
system. Everything imports everything.
Help me restructure using Clean Architecture:
(1) Draw the dependency graph — where are the violations
of the Dependency Rule?
(2) Identify Entities (business rules), Use Cases
(application rules), and Adapters (HTTP, DB)
(3) Define component boundaries using the Component
Cohesion principles (CCP, CRP)
(4) Show me how to refactor one module as a template
for the rest
Use clean-architecture skill.
Skills used: clean-architecture
You need to process 50K events/second and serve dashboard queries with sub-second latency.
Prompt:
We receive 50K clickstream events/second and need to:
- Store raw events for replay
- Compute real-time aggregations (clicks per page per minute)
- Serve dashboard queries with sub-second latency
- Handle late-arriving events gracefully
Design the pipeline:
(1) Should we use batch, stream, or Lambda architecture?
(2) What's the right partitioning strategy for the event store?
(3) How do we handle exactly-once processing?
(4) What storage engine serves the dashboard queries fastest?
Use ddia-systems and system-design skills.
Skills used: ddia-systems, system-design
Your microservices work fine in dev but cascade failures in production under load.
Prompt:
We have 8 microservices. When the recommendation service
slows down, it causes timeouts that cascade through
checkout, cart, and the API gateway. Last week this
took down the whole site for 45 minutes.
Design a resilience strategy:
(1) Add circuit breakers: what thresholds and recovery
timeouts for each service-to-service call?
(2) Add bulkheads: how should we isolate thread/connection
pools so one failure can't drain the system?
(3) Design a retry strategy with exponential backoff
and jitter that won't create a thundering herd
(4) Plan a chaos engineering experiment to verify
these patterns work
Use release-it and pragmatic-programmer skills.
Skills used: release-it, pragmatic-programmer
Your services are organized by technical layer instead of business capability, and cross-team changes take weeks.
Prompt:
Our backend is split into: api-gateway, auth-service,
data-service, notification-service, and worker-service.
Every feature requires changes to 3-4 services and
coordination across 2 teams. Something is wrong
with our boundaries.
Help me redesign:
(1) Identify the bounded contexts in our domain
(what are the natural business boundaries?)
(2) Check if our current services respect the
Dependency Rule — or are they a distributed monolith?
(3) Propose a new service decomposition aligned
with domain boundaries
(4) Design anti-corruption layers between contexts
that need to communicate
Use domain-driven-design and clean-architecture skills.
Skills used: domain-driven-design, clean-architecture
Quick reference showing where each skill appears in the examples above.
| Skill | Appears In |
|---|---|
| jobs-to-be-done | Startup Founders, Product Managers |
| mom-test | Startup Founders (x2) |
| cro-methodology | Online Marketers (x3) |
| refactoring-ui | UX/UI Designers (x2), Solopreneurs |
| ios-hig-design | UX/UI Designers (x2) |
| scorecard-marketing | Online Marketers (x2), Solopreneurs |
| storybrand-messaging | Online Marketers, Sales Leaders, Content Creators (x2) |
| hooked-ux | Product Managers (x2), UX/UI Designers |
| improve-retention | Product Managers (x3), UX/UI Designers, Solopreneurs |
| ux-heuristics | UX/UI Designers (x4) |
| web-typography | UX/UI Designers, Solopreneurs |
| top-design | UX/UI Designers |
| microinteractions | Product Managers, UX/UI Designers |
| negotiation | Sales Leaders (x2) |
| influence-psychology | Online Marketers (x2), Sales Leaders, Content Creators (x2) |
| lean-startup | Startup Founders |
| design-sprint | Startup Founders |
| inspired-product | Product Managers |
| continuous-discovery | Startup Founders, Product Managers |
| lean-ux | Product Managers, UX/UI Designers |
| crossing-the-chasm | Startup Founders, Sales Leaders, Solopreneurs |
| blue-ocean-strategy | Startup Founders, Solopreneurs |
| traction-eos | Product Managers (x2) |
| design-everyday-things | Product Managers, UX/UI Designers |
| predictable-revenue | Sales Leaders (x2) |
| made-to-stick | Startup Founders, Online Marketers, Sales Leaders, Content Creators (x2) |
| drive-motivation | Product Managers |
| hundred-million-offers | Startup Founders, Online Marketers, Sales Leaders, Solopreneurs |
| obviously-awesome | Startup Founders, Product Managers, Solopreneurs |
| contagious | Startup Founders, Product Managers, Online Marketers, Content Creators (x2) |
| one-page-marketing | Startup Founders, Online Marketers (x2), Content Creators, Solopreneurs |
| clean-code | Software Engineers |
| refactoring-patterns | Software Engineers |
| software-design-philosophy | Software Engineers |
| pragmatic-programmer | Software Engineers, Tech Leads |
| domain-driven-design | Software Engineers, Tech Leads |
| ddia-systems | Software Engineers, Tech Leads |
| system-design | Tech Leads |
| clean-architecture | Tech Leads (x2) |
| release-it | Tech Leads (x2) |
| high-perf-browser | Software Engineers |