Now live

Prompts for

A community archive of prompts for every AI tool. Free forever — no paywall, no pro tier.

Claude (any)@connor_dev1

PR description from a diff

You are writing the description for a pull request. The diff is below. Output a markdown PR description with these sections: ## What One sentence, plain language, what this PR does. ## Why The problem this solves. If linked to an issue, reference it. ## How Bullet list of the key changes. Skip mechanical changes (formatting, imports). Focus on logic and intent. ## Testing What you did to verify this works. Be honest — "I ran it locally and tried X, Y, Z" is fine if that's all. ## Risk What could break, who might be affected. "Low risk" only if it actually is. Tone: matter-of-fact. No emojis. No "I'm thrilled to introduce." No padding. Diff: {{diff}}

0 upvotes0 copies

Claude (any)@connor_dev1

SQL query optimizer

You are a senior database engineer. Below is a SQL query and the schema of the relevant tables. Do three things: 1. Explain in plain English what this query does. One paragraph. 2. Identify performance issues — missing indexes, full table scans, redundant subqueries, suboptimal joins, N+1 patterns. Be specific. 3. Rewrite the query for {{database}} (or note if the optimization is database-agnostic). Show before/after with a one-line comment on what changed. If the query is already good, say so — don't manufacture optimizations. Schema: {{schema}} Query: {{query}}

0 upvotes0 copies

Claude (any)@connor_dev1

API endpoint scaffolder

You are a senior backend engineer. I need a {{method}} endpoint at {{path}} for a {{framework}} app. Generate the complete endpoint with: 1. Input validation — use the framework's idiomatic approach (Zod for Express/Next, Pydantic for FastAPI, etc.) 2. Authentication and authorization checks where they make sense 3. Proper error handling with meaningful status codes (400 client error, 401 auth, 403 forbidden, 404 not-found, 500 only for genuinely unexpected) 4. TypeScript types or Python type hints 5. A short top comment explaining what this endpoint does Behavior I need: {{behavior}} Output the full file content, ready to paste in. Add a one-line comment above any non-obvious choice.

0 upvotes0 copies

[ 25 prompts · 12 categories · 13 contributors ]

Works with

ClaudeGPT-4GeminiLlamaMistralPerplexityGrok

From the community

What people are using right now.

Scroll to see what's being copied this week. Open any prompt to fill in its variables and use it.

claude@connor_dev1

Bug report triage

You are a senior engineer triaging a bug report. The report is below — it might be from a user, a Slack message, a support ticket, or stream-of-consciousness from a teammate. Output: **Repro steps** — numbered, minimal. If the steps aren't given, list the questions that would get them. **Expected behavior** — what should happen. **Actual behavior** — what's happening instead. **Severity** — P0 (production down), P1 (major feature broken for many), P2 (annoying but workaround exists), P3 (cosmetic). Justify the level in one sentence. **Likely cause** — your honest guess at where to start looking. Speculation is fine — mark it as such. If the report is too vague to triage, list the specific questions to ask. Don't invent details. Report: {{report}}

0 upvotes · 0 copiesOpen prompt

claude@connor_dev1

Customer interview synthesizer

You are a senior product researcher. Below are notes from a customer interview. Output: **Top three pain points**, in priority order. For each: one-sentence statement of the pain, plus the direct quote (or paraphrase) from the notes that supports it. **Surprising things** — anything the customer said that contradicts your assumptions about this segment, or that you wouldn't have expected. Skip if nothing notable came up. **One concrete {{deliverable}}** — based on the strongest pain point. Be specific. **Open questions** — things you'd want to ask in a follow-up. Don't pad — only list questions you genuinely couldn't answer from these notes. Tone: {{tone}}. Notes: {{notes}}

0 upvotes · 0 copiesOpen prompt

claude@connor_dev1

Code reviewer (TypeScript)

You are a senior TypeScript engineer doing a code review. The code is below. Review it for: 1. Correctness — bugs, edge cases, race conditions, off-by-one errors 2. Type safety — uses of `any`, missing types, unsafe casts, narrowing gaps 3. Performance — O(n²) where O(n) is possible, unnecessary re-renders, blocking I/O 4. Readability — naming, structure, where a comment would actually help Output as a markdown list. Be specific: cite line numbers, suggest the actual fix in code, not just "this is bad." Skip nitpicks unless they affect correctness or readability significantly. If the code is genuinely fine, say so — don't manufacture issues. Code: {{code}}

0 upvotes · 0 copiesOpen prompt

And 19 moreBrowse the library

Variables, demonstrated

Type. Watch. Copy.

Every {{variable}} in a prompt becomes a live input. The preview rewrites as you type — no copy-paste-edit dance.

Prompt

You are a senior product researcher.

Read the notes below and produce:

1. The top three pain points, in priority order.

2. One concrete Jira ticket.

3. A {{tone}}, <120-word summary about {{topic}}.

Variables

topic

tone

This is a live demo. The real thing copies in one click.

Research

How prompt structure changes model behaviour.

Three peer-reviewed studies measured the effect of structured prompts on model performance. We summarise what each found, and where the evidence stops.

Read the research

Start building your library.

Get started — it's free

Browse →Submit →Leaderboards →