Customer Support Macro Set for Refunds, Delays, Angry Customers and Escalation
Writes 10 ready-to-send support reply macros in your brand tone covering refunds, delays, angry customers and escalation.
341 prompts · last added
276 results for “skin tone and hairstyle exactly unchanged” · page 1 of 12
Writes 10 ready-to-send support reply macros in your brand tone covering refunds, delays, angry customers and escalation.
Analyzes your brand copy samples and builds a reusable one-page voice brief with tone rules, banned words, example rewrites and a paste-ready instruction block.
Writes your professional bio in a one-line, short and long version, in first and third person, from your background, with real specifics instead of buzzwords.
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.
Builds a playbook that answers the eight most likely objections for your product and buyer, each in four steps with honest evidence.
Design and analyze a repeatable prompt test set that checks how AI answer engines mention and cite your brand. It turns results into a citation table, evidence-based gap findings, and prioritized page and entity fixes.
Lists the questions buyers ask AI assistants about your product category, checks which sources those answers lean on, and plans the pages and facts you need to be cited.
Turns a task you repeat into a custom slash command file with frontmatter, arguments, restricted allowed tools and a fixed output format.
Diagnoses what a price objection really means and builds response scripts, trade-based concession rules, and escalation criteria. It helps a rep decide whether to hold price, trade scope, or walk away.
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.
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 refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
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.
Plans and executes a library or framework version migration in Cursor in small, verifiable batches, with an impact inventory, rollback points, and per-batch test gates instead of one risky bulk edit.
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
Builds a behavior-based test matrix for a function or module and then generates test code in your framework. Covers edge cases, failures, and mocking boundaries, with coverage gaps stated honestly.
Build a topic cluster from a keyword list and existing content, then rank which cluster and pages to create first. It includes a keyword-to-page mapping table, internal link rules, and cannibalization risks.
Turns rough notes and supplied source excerpts into a send-ready newsletter issue. It compares lead angles, flags unsupported claims, and ends with a go/no-go checklist before you hit send.
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.
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 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.
Turns pasted customer reviews into evidence-based personas, jobs-to-be-done, objections and a bank of exact customer phrases ready to reuse in copy.
Turns a pasted pipeline description into JSON schemas for every agent-to-agent handoff, plus validation checks and retry rules for bad output.
Produces a set of testable guardrail rules for your coding agent, covering blocked commands, approval gates, secret handling and hook checks.
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.