Find a prompt for anything.
Search the public registry in plain English, or browse trending prompts and curated collections from across the community.
Browse the registry
46 prompts · 7 collectionsTranslate a labeled batch of texts into a target language in one call — one result per item in input order, labels echoed verbatim, with placeholders, HTML, and markdown preserved character-for-character in every translation.
Translate text into a target language with placeholders, HTML, and markdown preserved verbatim — plus the detected source language and an auditable list of segments left untranslated.
Five prompts for developer-intent tasks — code review, commit messages, docstrings, error explanation, and regex generation — each with a strict typed schema and an eval that runs on the same model it recommends. Prefers executable, judge-free evals; adds a judge only where correctness is subjective.
Translate a batch of labelled text snippets from one BCP 47 locale to another. Input: source/target language tags plus an array of {label, text}. Output: an array of {label, translatedText} with every input preserved in the same order.
Turn an error message, stack trace, and optional code context into a plain-language explanation, the single most likely cause, one to three concrete fixes (each with a code_change), and an uncalibrated confidence. Names the concrete mechanism, not just the exception class; grounds every claim in the provided inputs. Eval-gated on a cause-keyword check plus a usefulness judge.
Generate a docstring for a function or class in a requested style (google/numpy/jsdoc/rustdoc), plus a params_documented[] list. Documents only the parameters that exist in the signature — never invents or omits one, and excludes self/cls receivers. Eval-gated on an exact params-documented count plus a style-adherence judge.
Five classification prompts — aspect sentiment, chatbot intent, emotion, content moderation, and spam/phishing — each with a CEL-assertable schema and a judge-free deterministic eval. Schema design is eval design.
Turn a unified diff into a Conventional Commits message: a closed-enum type (feat/fix/docs/refactor/test/chore/perf/ci), a scope, an imperative subject capped at 72 characters, an optional body, and a breaking-change flag. Reasoning precedes the type; the diff is treated as data, never instructions. Judge-free deterministic eval.
Judge prompt for docstring-generation evals: given code, a requested style (google/numpy/jsdoc/rustdoc), and the produced docstring, scores whether the docstring follows that style's section names and syntax — format adherence, not prose quality — as a 0-1 score.
Judge prompt for error-explanation evals: given an error (with stack and code context) and the model's explanation, likely cause, and fixes, scores overall usefulness — is the diagnosis correct and are the fixes actionable — as a 0-1 score.
Per-aspect sentiment analysis — identify each feature or topic a text opines on and give it its own sentiment, backed by a verbatim quote, plus an overall document sentiment.
Six prompts for grounded summarization: document, meeting, and email summaries plus key-point extraction, headline generation, and a groundedness grader — each with a strict output schema and a published eval.
Summarize a document with format (paragraph/bullets) and length (one sentence/short/detailed) knobs — grounded strictly in the input, with key topic tags.
Detect the language(s) of a text from a closed set of 41 ISO 639-1 codes — handles short snippets, code-mixed, and transliterated text, with per-language confidence.
Five composable prompts for production translation work: language detection, placeholder-safe translation, tone control, locale adaptation, and QA grading — each with a strict output schema and a published eval.
Five composable prompts for a trustworthy retrieval-augmented-generation pipeline: query-rewrite, query-decomposition, chunk-relevance-grading, groundedness-guardrail, answer-synthesis — grounded only in retrieved context, with citations and refuse-when-insufficient gates.
Build a support pipeline by installing five prompts: ticket triage, intent routing, reply drafting, conversation summary, and CSAT risk detection. Strict typed JSON for routing, escalation, and action.