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
100 results for “repo-setup” · page 3 of 5
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Builds a transparent market size estimate from discoverable sources, compares top-down and bottom-up methods, and flags weak assumptions before a go or no-go call.
Upload a CSV or XLSX and get a metrics review with variance explanations, data-quality flags, and a decision list for the week. Written for ChatGPT's Advanced Data Analysis.
Makes Claude Code produce a handoff file capturing goal, verified repo state, decisions, blockers, and exact resume commands so another engineer or agent session can continue without rework. Use it before ending a long task.
Turns your source material into a diagnostic quiz with an answer key, a misconception map, and a reteach plan. It helps you decide who needs review and what to reteach.
Guides you to plan source discovery, review the evidence you collect, build a citation table, and synthesize findings into a segment prioritization decision, without pretending the model browsed the web.
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.
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.
Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.
Creates an editorial brief and outline for a researched article. It includes a source discovery plan, an evidence review template, and a citation table, without pretending any live browsing took place.
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.
Guides Codex through reproducing a failing CI job locally, classifying the cause as code, test, environment, or flaky, applying a minimal fix when safe, and producing an evidence-based handoff for anything it cannot resolve.
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.
Has Gemini inspect uploaded images, screenshots, charts, and PDFs, extract what is visible, and verify claims against online sources. Ends in a findings log with confidence ratings and next steps.
Has GitHub Copilot review your branch diff against the base branch, flag defects and missing tests, and draft a PR description with evidence. Use it to decide whether to open the PR or fix issues first.
Plans a birthday, team event or small celebration with a booking timeline, a line-item budget, a shopping list and an hour-by-hour plan for the day.
Plans a big migration so an orchestrating agent can split it into independent chunks for parallel subagents, each with a clear brief, a verification command and merge rules.
Turns a vague GitHub issue into a self-contained task with context, testable acceptance criteria, files to touch, and tests to add, so the Copilot coding agent can finish it.
Turns a pasted feature spec into independent coding-agent tasks with file ownership, interface contracts, a merge order and a done command for each task.
Analyzes a recurring manual task and produces an automation blueprint with trigger, steps, data mapping, error handling, and a test plan. It also helps you decide whether the task is worth automating at all.
Claude Code questions you about a feature's requirements and edge cases, then delivers an implementation plan with acceptance criteria and test commands, without writing code first.
Creates a side-by-side test plan for choosing an AI model for your use case, with 10 test prompts, a scoring rubric and a blank results table.
Explains each pasted lab value and its reference range in plain English and ends with questions to bring to your doctor, without diagnosing.
Produces a set of testable guardrail rules for your coding agent, covering blocked commands, approval gates, secret handling and hook checks.
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.