Codebase Tour for a Specific Task
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
341 prompts · last added
341 results for “If the caption comes out garbled” · page 4 of 15
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Turns a client's rough notes into a structured design brief with goals, audience, deliverables, constraints, references to gather and measurable success criteria.
Creates a vertical three-panel snowy collage from your selfie, made for December stories and reels.
Audits an existing multi-agent pipeline for failure modes and produces retry limits, fallback paths, escalation triggers, and a test plan. Supports the decision on what to harden before wider rollout.
Plans and executes a library or framework version migration in Cursor in small, verifiable batches, with an impact inventory, rollback points, and per-batch test gates instead of one risky bulk edit.
Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.
Maps your current skills to three realistic new roles, shows the gap for each, and gives a 90-day plan to close the smallest gap without quitting your job first.
Scores your essay criterion by criterion against your rubric and names the three fixes that will improve it most, without rewriting anything.
Writes a verified handoff file covering changes, decisions, open issues and next steps so a new Claude Code session can continue without re-reading the whole history.
Creates a same-day recap email and a three-touch re-engagement sequence from meeting notes. It helps a rep confirm commitments and decide whether a quiet deal should be chased, reframed, or closed out.
Rewrites resume bullets to mirror a job posting's keywords only where they are true, and lists the requirements you cannot honestly claim.
Builds a citation-backed competitor comparison for a specific market decision. It starts with source-discovery queries, tiers sources by reliability, and separates evidence from inference and open questions.
Build a research plan that shows where to find competitor evidence, how to judge sources, and how to log citations. It never claims live browsing happened, so you can verify each source yourself.
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Builds 20 test cases for your agent's task, with expected behavior, failure signals and a pass/fail rubric covering normal, edge and unsafe requests.
Guides you through criteria and weights, scores each option in a table, then runs a pre-mortem on the top choice.
Drafts a calm, polite reply that holds your stated boundary and is hard to misread, with a short version and a misread check.
Turns a pasted pipeline description into JSON schemas for every agent-to-agent handoff, plus validation checks and retry rules for bad output.
Produces complete Gemini Gem instructions with a persona, steps, output format and a list of Google Drive files to attach as knowledge.
Creates a four-email follow-up sequence for an unanswered outreach, adding new value in each touch and ending with a polite breakup.
Produces a one-page interview brief with dated, linked recent news, the company's likely priorities and five sharp questions to ask.
Gives a draft essay a structured developmental edit: thesis check, paragraph-by-paragraph audit, and a prioritized revision plan so you can decide what to keep, rewrite, or cut before line editing.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then making small, reversible commits. Helps you decide whether the refactor preserved behavior and is worth merging.
Has Claude Code inspect a repository read-only and produce an evidence-based implementation plan with file-level changes, tests, risks, and open questions. Use it to decide whether to start, split, or clarify a feature before any code is written.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.