Curated AI prompts you can run right now.

Turns your product description into a clean Free / Pro / Business pricing table with anchor logic.

Avoids the typical "more of the same feature" trap. Each tier ladders by *use case* not by raw quota.

Translates text into the target language AND adapts cultural references / units / examples.

Not just word-for-word — adjusts examples, currencies, and idioms.

Generates a structured SWOT (Strengths, Weaknesses, Opportunities, Threats) from a 2-3 sentence business description.

Useful for board prep, founder strategy days, or pitch-deck slides. The output is structured so you can drop it directly into a doc.

12 subject-line variants across 4 styles (curiosity, value, urgency, personal).

For email A/B tests. Real, not "🔥 You won't believe this".

Generates 3 Google Search Ads (headlines + descriptions) sticking to character limits.

Outputs in Google's exact format. Each variation tests a different angle (feature, benefit, urgency).

Flags concerning clauses in a vendor contract — pricing, lock-in, liability, data, exit.

Not legal advice — but catches obvious traps before signing.

Pulls action items out of an email thread or meeting transcript — who, what, by when.

Goes after "todos" that hide behind "let me know" / "circle back".

Generates 20 brandable name ideas for a product, grouped by style (descriptive / abstract / portmanteau).

Each name includes the .com / .ai availability heuristic (not authoritative).

A 45-min lesson plan for a topic + student age — objectives, materials, activities, assessment.

Ready to print and hand to a substitute teacher.

Builds a weighted decision matrix — options × criteria × weights → scored recommendation.

For decisions where gut isn't enough.

Writes a 500-word short story in the genre + style requested.

Tight structure, beginning-middle-end. No exposition dump.

Drafts an on-call runbook for a specific failure mode — detect, diagnose, mitigate, recover.

Saves the 3am scramble of "what do I do?".

Writes a 1-page Amazon-style narrative memo for a non-trivial decision.

6-pager light. Used to replace status meetings with a written decision.

Turn metrics + notes into a polished monthly investor email — concise, scannable, no fluff.

Investors skim. Format follows the Patio11 / Sequoia template: TL;DR, Highlights, Lowlights, Asks.

Writes a polite-but-firm "no" reply — preserves relationship without saying yes.

For requests on your time you should decline.

Speech celebrating a retiree's career — specific achievements, personality, wish for next chapter.

For colleagues or family. Lands somewhere between roast and tribute.

A 2-3 week recovery plan for a common minor injury — rest, mobility, return-to-activity.

Mild ankle sprain, runner's knee, lower-back tweaks. NOT for serious injuries.

Suggests 10 thoughtful gift ideas across budgets for a specific person.

Goes beyond generic "buy them a gift card". Considers interests + relationship.

Fills in all 9 boxes of the Osterwalder Business Model Canvas from a business description.

For early-stage thinking, repositioning workshops, or onboarding investors.

Constructive critique on a design — structured by goal, hierarchy, contrast, copy.

Avoids "I don't like the blue" feedback. Goes to root cause.

Reduces any long article to a 3-bullet TL;DR plus a single-sentence one-liner.

For when you have to brief someone before a meeting. Captures the *implications*, not just the facts.

Turns raw stand-up notes into a Linear-ready ticket with title, description, and acceptance criteria.

Drop it straight into Linear, Jira, or GitHub Issues.

Generates a SEO-friendly outline: title, slug, H2/H3 structure, target word count per section.

Stops you from writing a 2,000-word post you have to restructure later. The outline is ready to expand.

Breaks a top-line metric (e.g. ARR) into a tree of contributing inputs the team can act on.

Stops "improve revenue" being the only thing in the company OKRs.

Audits a design for visual accessibility — contrast, focus states, color-only signals, motion.

WCAG 2.2 AA spot-check before dev handoff.

Question set for a JTBD interview that uncovers the real "switch" moment.

Classic Bob Moesta / Switch interview format — anatomy of a purchase.

A complete CI pipeline YAML — lint, test, build, scan, deploy — for a Node/Python/Go service.

Caching, matrix builds, secrets handling, deploy gates.

Decodes a regex into plain English, character-class by character-class.

No more squinting at /^\d{3}-\d{4}$/.

Writes a clean conventional-commits message (feat/fix/chore/etc.) from a diff or description.

Stops "wip fix stuff" commit history.

Reads a CSV sample and surfaces 5-7 non-obvious insights with the supporting numbers.

Stops "I have the data, what do I do with it?" paralysis.

Designs a 6-tile dashboard layout for a stakeholder, with each tile's metric + viz type.

Stops the "let's just add another widget" creep.

Takes a vague prompt and rewrites it to be specific, structured, and reliable.

Adds output format, examples, constraints, and edge-case handling.

Generates a 50/30/20 (or custom) budget allocation for a given monthly income, with category targets.

Currency-aware. Realistic Indian/US/EU defaults.

Writes a non-corporate, scannable job description that good candidates actually want to read.

No "rockstar ninja". Real expectations, what the team does, comp range upfront.

Compress a long plan into a 1-page exec summary stakeholders actually read.

For board decks, M&A teasers, internal sponsorship — the version people skim before deciding.

Explains a complex concept using analogies a 5-year-old would understand — no jargon.

For when you need to brief a non-technical stakeholder or pitch to your parents.

Turns a cryptic stack trace into a plain-English explanation of what went wrong and where to look.

Cuts the time from "stack trace appeared" to "you know where to look" by 80%.

Generates a professional README.md with all the expected sections (install, usage, API, license).

No more "TODO: add README" sitting in your repo for 6 months.

Generates 5 hero-section variants (headline + sub-headline + CTA) for a product description.

Each variant uses a different copywriting framework: PAS, AIDA, Before-After-Bridge, Promise-Proof-Push, and a plain-English one.

Drafts a 2-page board pre-read from raw metrics + a quarter's notes.

TLDR + traffic-light metrics + key decisions needed.

Builds a structured eval rubric to grade LLM outputs for a specific task.

Stops vibes-based "did the AI do good?" review.

Generates an Ash Maurya Lean Canvas — designed for early-stage startups, not big corps.

Same canvas, leaner: Problem, Solution, Unique Value Prop, Unfair Advantage, Channels, Customer Segments, Key Metrics, Cost Structure, Revenue Streams.

Crafts a click-worthy SEO title (≤60 chars) + meta description (≤155 chars) targeting a keyword.

Title prioritises Google ranking factors. Meta prioritises CTR.

AP-style press release for a product launch, fundraise, or partnership.

Headline, dateline, lede, body, boilerplate, contact — the format reporters expect.

Writes a pitch email to a podcast host that gets a "yes" instead of "noted".

Specific show reference, why-you-why-now, 3 angle ideas, easy yes.

10 CTA copy variants for a single button, sorted by intent (high vs low).

For A/B tests on landing pages, modals, emails.

Writes a firm but polite follow-up email for an overdue invoice.

Three escalation levels: gentle nudge, second reminder, formal final notice.

10 tagline variants in 4 styles for one product.

Each ≤ 8 words. Tested for memorability, not "creativity".

15 adversarial test cases for an LLM feature — jailbreaks, prompt injection, harmful asks.

For red-teaming an AI tool before launch.

Builds a customer case study from raw notes — Problem, Solution, Results, Quote.

PSR format with concrete numbers + 1 strong pull quote.

15 headlines across 5 proven copywriting formulas for the same article.

Useful before publishing — A/B test the top 3 in email subjects + LinkedIn.

Explains what a SQL query does in plain English — useful for code reviews and onboarding.

Especially helpful for queries with nested CTEs and window functions.

Designs an empty state — illustration, headline, sub, primary action — for any screen.

Empty states are first impressions for new users. They deserve more than a sad cloud.

Designs error-state UI text — title, body, recovery action — for common app errors.

Network errors, validation errors, permissions errors. Each gets a human voice.

Drafts a starter privacy policy from a product description — GDPR + CCPA-aware.

Not a substitute for a lawyer. A solid starting point that covers the standard sections.

Suggests 8-10 microinteraction ideas for a screen — what fires, when, why it delights.

Confetti is for one screen. Most microinteractions should be calm + clear.

Reorganises a product's navigation — top-level, sub-nav, footer — based on user tasks.

Card-sort thinking — by task, not by team org chart.

Reviews a form for length, field order, error handling, mobile readiness.

The single biggest conversion lever on most pages.

Plans how a desktop layout adapts at tablet + mobile — what stacks, what hides, what changes.

Not just "mobile-first" — actual decisions per breakpoint.

Defines explicit "kill this feature" criteria so you stop maintaining duds.

Most teams ship 100x more than they kill. This forces honest cleanup.