Cursor Project Rules Generator for Your Repo's Stack
Has Cursor inspect your repository and write 3-5 scoped .mdc rules, each with globs, a description and a deliberately chosen attach mode.
341 prompts · last added
276 results for “Do not claim to have searched” · page 6 of 12
Has Cursor inspect your repository and write 3-5 scoped .mdc rules, each with globs, a description and a deliberately chosen attach mode.
Turns a raw feature or bug request into a paste-ready Codex task with a goal, constraints, files in scope, definition of done and exact verification commands.
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 60-180 second explainer video script from a brief, with a scene-by-scene table for voiceover and visuals, a fact-check list, and a go/no-go checklist for recording.
Guides GitHub Copilot agent mode to inspect the repository, state assumptions, plan a minimal change, implement it, and add tests. It ends with a verification report you can use to decide whether to open a PR.
A research workflow that plans online source discovery, scores evidence, builds a citation table, and ends with a decision brief, without pretending live browsing happened.
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.
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.
Converts a fuzzy research question into a paste-ready Gemini Deep Research brief with scope, sub-questions, source types, date range and report format.
Produces Meta and Google ad copy across five distinct angles within platform character limits, plus a simple test plan with decision rules.
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Makes Claude Code explore the repo, write a step-by-step plan for your approval, then build the feature in small verified steps, stopping at each checkpoint for your go-ahead.
Sorts a batch of pasted emails by what each one needs from you, drafts short replies for the ones that need an answer, and lists deadlines found in the thread.
Rewrites text that sounds machine-generated by removing the specific tells, like stock words and forced triads, while keeping every claim and the meaning.
Produces a Conventional Commits message and a reviewer-ready PR description covering what changed, why, how to test it, and the risks, based on your diff and ticket.
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.
Turns product facts, audience insight, and competitor context into a positioning statement, messaging hierarchy, and proof map so a team can approve one launch angle.
Turns the transcript of a recorded walkthrough into a numbered SOP with prerequisites, steps, screenshots to capture, decision points, and common mistakes, ready for a team wiki.
Turns a broad topic into five researchable questions sized to your assignment, each with the data or sources it needs.
Turns the changes in a branch into a clear pull request description: what changed and why, how to test it, risks and screenshots to add, in your repo's template if it has one.
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.
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.
Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.
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.