Meta Title and Description Variants With Character Counts
Writes five meta title and description pairs for a page, each within Google's display limits with character counts, matched to the target keyword and the reason to click.
341 prompts · last added
341 results for “Subtle glare on the glossy print” · page 3 of 15
Writes five meta title and description pairs for a page, each within Google's display limits with character counts, matched to the target keyword and the reason to click.
Uses web search to produce a one-page account brief with priorities, dated news and links, likely stakeholders, and three personalized openers.
Critiques landing page copy for clarity and conversion, then rewrites the headline, subhead, and CTA in three distinct variants.
Builds a playbook that answers the eight most likely objections for your product and buyer, each in four steps with honest evidence.
Holds a casual conversation at your CEFR level, corrects mistakes inline in brackets, and recaps new vocabulary every 10 turns.
Converts discovery notes into a one-page proposal executive summary and a dated mutual action plan. It helps a rep decide whether the deal is ready to propose and what is still missing.
Guides Cursor Agent through reproducing a bug, isolating the root cause with evidence, applying a minimal diff, and adding a regression test, ending with a verification checklist and risks.
Audits an existing or planned onboarding email flow, then rewrites it around a single activation event with segmentation, timing, copy, and a measurement plan.
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.
Analyzes weekly KPI data against targets, separates signal from noise, proposes ranked root-cause hypotheses, and produces owner-assigned actions and an escalation list for a team operating review.
Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.
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.
Compares products you are choosing between using current reviews and spec sheets, with cited sources, real-world complaints and a recommendation based on how you will use it.
Turns a side-business idea into a one-page plan: customer, offer, price, channel, costs, and the cheapest 30-day test that would prove people will pay.
Builds a one-page cheat sheet of your ten most likely sales objections, each with the real concern behind it, a question to ask back, a short answer, and proof to share.
Writes a ready-to-deploy orchestrator system prompt that delegates to your workers, tracks progress in a ledger, merges results and stops on defined conditions.
Builds a day-by-day revision calendar that counts back from your exam date, with spaced reviews and timed practice sessions.
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.
Has the Cursor agent restructure a messy component into smaller pieces while proving the behaviour stays identical, using existing tests or new characterization tests first.
Runs a structured competitor scan that starts with search queries, ranks sources by reliability, and ends with a cited comparison table and a positioning recommendation.
Turns your product facts, customer evidence, and competitor notes into a tested positioning statement, messaging hierarchy, and proof-gap list so a marketing team can decide what to say and what to validate first.
Has Cursor lock in current behavior with characterization tests before restructuring a legacy module in small steps, so you can decide whether the refactor preserved behavior and is safe to merge.
Create a writer-ready content brief from SERP observations you supply. It covers intent, required sections, evidence gaps, and a go or no-go call on whether the page is worth producing.
Runs a read-only Codex investigation that maps the relevant code paths, test commands, and likely root causes for a bug report. It ends with a ranked hypothesis table and a go/no-go recommendation before any edits.
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.