50 Winning AI Prompts: The Mega Library That Saves Hours Every Week

Fifty proven prompts, organized by job: writing, coding, research, planning, and coaching. Each one is deliberately layered — role, context, task — so you can adapt it in a minute. Copy the winners, tune the parameters, and save the result into your own prompt library. These are the hours saved: zero reinvention, every week.

Every prompt below follows the layered prompt method. Test them how you like — here is how to compare outputs — then keep the winners permanently in a prompt library.

Writing (1-10)

• Rewrite for clarity: 'You are a senior editor. Rewrite this text to be shorter and more direct, keeping all facts. Keep the tone.'
• Summarize for an exec: 'You are a chief of staff. Summarize this doc in 5 bullet points, one line each, for a busy executive.'
• Repurpose a blog as a newsletter: 'You are a content strategist. Turn this blog into a 300-word newsletter with a subject line.'
• Strict constraints: 'You are a copywriter. Write 3 subject lines, max 45 characters each, no emojis, no questions.'
• Audience-aware rewrite: 'You are a technical writer. Rewrite this for engineers who hate jargon. Plain English, short paragraphs.'
• Slug and title generator: 'You are an SEO analyst. Give 5 title options and a URL slug for this article. Match the existing style.'
• Tone shift: 'You are an editor. Rewrite this in a friendly, not hype tone: everyday words, no exclamation marks.'
• Google doc format: 'You are a document writer. Turn these notes into a Google-doc-ready memo with headings and bullet lists.'
• Cold email: 'You are a growth associate. Write a 90-word cold email to a CTO about a tool that saves API token spend.'
• Frequently asked: 'You are a support lead. Turn this changelog into 5 FAQ entries customers will actually ask.'

Coding (11-20)

• Code review: 'You are a staff engineer. Review this diff for bugs, performance, and readability. No style nitpicks.'
• Explain unfamiliar code: 'You are a senior engineer. Explain this function to a junior dev: what it does, why, and what could break.'
• Refactor for readability: 'You are a refactoring specialist. Simplify this function without changing behavior. Show a before/after.'
• Write tests: 'You are a test engineer. Write unit tests for this module, covering the edge cases in this list.'
• Debug with context: 'You are a debugging expert. Here is the error, the input, and the file. Find the root cause, not the workaround.'
• Add Types: 'You are a TypeScript specialist. Add proper types to this file and find two places where typing prevents a bug.'
• SQL to ORM: 'You are a backend engineer. Convert this SQL query to an ORM query and explain the trade-off in one line.'
• Performance: 'You are a performance engineer. This endpoint is slow. Profile the likely causes and give a ranked fix list.'
• Explain a stack trace: 'You are a debugger. Translate this stack trace into plain English and the most likely fix.'
• Architecture sketch: 'You are a solutions architect. Sketch the data flow for this feature in 8 steps, no code.'

Research (21-30)

• Gap analysis: 'You are an analyst. Compare these two documents and list only the differences that matter to decisions.'
• Competitive scan: 'You are a market researcher. List 5 competitor capabilities on this feature and how each of ours compares.'
• Unknown marking: 'You are a researcher. Answer this question and explicitly mark anything you are not sure about.'
• SWOT: 'You are a strategy consultant. Build a SWOT for this launch, max 4 items per quadrant.'
• Trade-off matrix: 'You are an analyst. Build a table comparing these 4 options across cost, speed, quality, and risk.'
• Sources wanted: 'You are a research assistant. Summarize this topic and list the 3 most authoritative sources to verify.'
• Interview prep: 'You are an interviewer coach. Give 10 questions that reveal how a candidate actually shipped things.'
• Sales enablement: 'You are a solutions consultant. Turn this product spec into 3 customer stories with quoted outcomes.'
• Requirements gleaning: 'You are a product manager. Extract explicit and implicit requirements from this user note.'
• Decision memo: 'You are a chief of staff. Write a one-page decision memo: context, options, recommendation, risks.'

Planning (31-40)

• Project kickoff: 'You are a project lead. Break this goal into a 4-week plan with a deliverable per week and a success metric.'
• Risks: 'You are a risk manager. List 8 risks for this plan, ranked by likelihood and impact, each with a mitigation.'
• Launch checklist: 'You are a launch operator. Build a pre-launch checklist of 20 items, ordered by dependency.'
• Meeting agenda: 'You are a facilitator. Draft a 30-minute agenda for a decision meeting with one clear outcome.'
• Backlog triage: 'You are a product owner. Rank these 12 items by value-effort and give the top 3 to start.'
• Roadmap draft: 'You are a PM. Draft a 3-quarter roadmap from these goals, marking what could slip.'
• Retro: 'You are a facilitator. Run a retro on this release: what worked, what didn't, one action per finding.'
• Estimation: 'You are a planner. Estimate this feature in t-shirt sizes and flag the two least-certain tasks.'
• Content calendar: 'You are an editorial planner. Turn these 12 topics into a monthly calendar with format and angle.'
• Onboarding plan: 'You are an enablement lead. Design a 7-day onboarding plan for a new hire on this team.'

Coaching (41-50)

• Second opinion: 'You are a neutral coach. I made this decision. Push back on it: what am I not seeing?'
• Trade-off reasoning: 'You are a decision coach. Walk me through choosing between A and B using expected value, not gut feel.'
• Skill ladder: 'You are a growth coach. Map the steps from where I am to senior-level on this skill, with a check at each step.'
• Bias check: 'You are a critical reviewer. Find three assumptions in my reasoning that could be wrong.'
• Goal breakdown: 'You are an execution coach. Break this annual goal into weekly actions with a review cue.'
• Feedback draft: 'You are a comms coach. Draft direct, kind feedback for a teammate on this issue.'
• Negotiation prep: 'You are a negotiation coach. Prepare me for this conversation: my leverage, their leverage, and a fallback.'
• Delegation: 'You are a management coach. Suggest 5 tasks I should delegate this week and how to hand them off.'
• Productivity audit: 'You are a productivity coach. Review my week list and find the top 3 time leaks.'
• Career narrative: 'You are a career coach. Turn my bullet points into a 2-minute story that shows impact, not activity.'

How to build your own mega library

1. Keep 50 max — a library you actually use beats a collection you scroll.
2. Organize by domain (writing, coding, research) with tags for model and failure mode.
3. Attach cost and output evidence to each prompt so you know it won.
4. Version every improvement so you never lose a winning rewrite.
5. Review quarterly and archive anything unused for 90 days.