Blog Outline Matched to the Search Intent of One Keyword
Builds a blog post outline for one keyword by first deciding the search intent, then structuring headings, questions and examples that match what searchers expect to find.
341 prompts · last added
276 results for “slightly out of focus” · page 1 of 12
Builds a blog post outline for one keyword by first deciding the search intent, then structuring headings, questions and examples that match what searchers expect to find.
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.
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 a pasted pipeline description into JSON schemas for every agent-to-agent handoff, plus validation checks and retry rules for bad output.
Designs the handoff contracts, stop conditions, and review gates for a sequential chain such as researcher, writer, editor, and fact-checker. Helps you decide whether the chain is ready to run.
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 a negotiation script for a job offer: your anchor number with a reason, word-for-word replies to common pushback, and a walk-away line, using market data you supply.
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.
Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.
Designs a three-agent content pipeline where a researcher, writer and editor pass structured handoffs, with the exact fields each agent receives and returns and checks between stages.
Turns pasted account material and a source discovery plan into a evidence-labeled research brief. It helps a rep decide whether to pursue an account, which persona to target, and which outreach angle to use.
Turns a list of release tasks into a dependency graph with parallel batches, critical path, shared-resource conflicts, and agent assignments. Supports the decision on what to run now versus wait on.
Splits a research question across parallel research agents, defines source discovery and evidence review steps, merges findings into a citation table, and produces a decision memo without claiming live browsing.
Turn your job offer and target number into a polite counteroffer email, phone talking points and replies to the three likeliest pushbacks.
Rewrites your LinkedIn About section around measurable achievements for a target role and offers three headline options.
A five-minute end-of-day check that records what got done, captures loose ends, and picks three priorities for tomorrow so you can stop thinking about work.
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.
Runs a behavior-preserving refactor in Codex exec. It pins current behavior with characterization tests, refactors in small verified steps inside an allowed scope, and ends with an evidence-based handoff for the merge decision.
Writes a first-person LinkedIn About section from your background: what you do, for whom, proof, and how to reach you, in under 1,500 characters with three opening options.
Directs Claude Code to reproduce a reported bug with a failing test, apply the smallest fix, and prove the fix with command output. Use it to decide whether a bug is fixed and safe to merge.
Plans 30 days of posts that lead to one offer: content pillars, a mix of value, proof and ask posts, hooks for each day, and the platform and format to use.
Audits an old article for outdated facts and missing subtopics, proposes new sections and rewrites the intro for your target keyword.
Has Claude Code review a branch diff like a skeptical maintainer, producing severity-ranked findings with evidence and a clear merge, fix, or block recommendation. Use it before opening or approving a pull request.
Converts scrappy bullet notes into a clear report with an executive summary, findings, decisions and next steps, without inventing anything.
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.