Curated AI prompts you can run right now.

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.

Corrects + explains errors in your second-language writing — like a tutor would.

Grammar + word choice + idiomatic phrasing. Coaching, not just correction.

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

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

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

For decisions where gut isn't enough.

Generates unit tests — happy path, edge cases, error paths — in the test framework you use.

Covers branches the AI can deduce from the code, not just trivial cases.

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.

Brief for a logo designer — usage, constraints, do's/don'ts, deliverables.

Reduces the "let me do 30 variations" surprise.

Reviews a REST API spec — resource naming, methods, status codes, pagination, errors.

Catches anti-patterns before they ship and become forever-versioned.

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

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

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

For red-teaming an AI tool before launch.

Drafts a clean offer letter — role, comp, equity, start date, conditions, references to policies.

Indian / US conventions. NOT a substitute for employment counsel.

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

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

Converts a list of bullet points into a flowing paragraph.

You wrote your idea as bullets. Get a polished paragraph for a doc, an email, or a launch announcement.

Turn a story or insight into a 1,200-character LinkedIn post that reads like a person wrote it.

Punchy opening line. Short paragraphs. One concrete lesson. No corporate buzzwords.

Cuts an email in half without losing the ask.

Paste any draft email. Get a tighter version that still says everything that mattered.

Responses to the top 5 objections for your offering — empathetic, specific, never defensive.

Each handler acknowledges, reframes, and provides proof.

Writes the management commentary for a P&L — what drove the variance vs plan.

For CFO / board reporting. No "revenue was driven by good performance".

Generates a structured component specification (states, variants, props) ready to hand to a designer.

For when you need someone to build a Button or Card or Modal that doesn't end up reinvented every Sprint.

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

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

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 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.

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

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

Designs an A/B test — hypothesis, variants, primary metric, MDE, sample size, duration.

Stops "let's just see if it converts" experiments that yield nothing.

New-hire onboarding plan for the first 90 days — learn, contribute, own.

Specific deliverables per phase. Stops "shadow people and figure it out".

Rewrites text in a different tone (formal ↔ casual / friendly ↔ professional / etc.).

Same meaning, different register. Useful for code reviews, emails, support replies.

Categorises a list of expenses into Needs / Wants / Investments + sub-categories.

For monthly review, tax prep, or expense report cleanup.

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

For requests on your time you should decline.

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

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

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

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

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

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

Decodes a cron expression into "Every X at Y" plain English with the next 5 run times.

Saves you from cronjob misfires at 03:00 on the wrong day.

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

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

A day-by-day vacation itinerary balanced for activity + rest + local food.

Avoids over-scheduling. Leaves room for spontaneity.

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

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

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

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

Generates a multi-stage, small-image Dockerfile for a given stack.

Multi-stage build, non-root user, .dockerignore, healthcheck, cache layers.

Polite, specific rejection email — preserves dignity + brand goodwill.

Two variants: after first screen vs after final round.

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

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

A system prompt template that pushes the model to show its reasoning before answering.

Higher accuracy on multi-step problems, debuggable when wrong.

A personalised plan to get to inbox zero — triage rules, batching, templates.

Stops constant inbox-checking. Uses Allen + Sunday Edition principles.

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

Stops "wip fix stuff" commit history.

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

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

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.

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".

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

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

A 500-700 word bedtime story tailored to a child's age + favorite themes.

Gentle, age-appropriate vocabulary, satisfying ending, encourages sleep.

Drafts a model card with intended use, limitations, training data summary, evaluation results.

For shipping a model responsibly + onboarding new users.

Designs a system prompt that turns user questions into retrieval queries — multi-query, HyDE, etc.

For RAG systems where retrieval quality dominates answer quality.

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

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

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

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

Senior-engineer code review: bugs, security, style, missed cases — ranked by severity.

Paste a git diff or a code block. Get the kind of review a thoughtful staff engineer would write: real bugs first, nitpicks last.

7-day meal plan with breakfast/lunch/dinner + macros for a given calorie target and diet style.

Currency/region-aware ingredient choices. Includes a grocery list.

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.

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.

Explains a grammar rule with examples + counter-examples + 3 practice sentences.

For language learners — replaces dense textbook explanations.

Generates 12 open-ended discovery questions tailored to a buyer persona.

Built on MEDDPICC / SPIN — uncovers pain, budget, decision process without sounding scripted.

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

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

Scores a list of feature ideas using RICE (Reach × Impact × Confidence / Effort) and ranks them.

Forces honest numbers. Tells you which 2-3 things to ship next and which to drop.

Turns a quarter's focus area into 3 Objectives, each with 3-4 measurable Key Results.

KRs are leading indicators with numbers — not vague aspirations.

A polite, value-first follow-up email after a no-reply — not "bumping this up".

Brings new value with each touch instead of nagging.