Apology Message That Takes Real Responsibility
Writes a sincere apology for a mistake at work or in personal life that names what happened, owns the impact, avoids excuses and says what changes next.
217 prompts
Prompts written for Claude, Anthropic's assistant. Claude handles long inputs well, so many of these prompts ask you to paste a whole document, transcript or code excerpt and then structure the answer around it.
12 results
Writes a sincere apology for a mistake at work or in personal life that names what happened, owns the impact, avoids excuses and says what changes next.
Takes one piece of news or a request and rewrites it three ways, each matched to the reader's relationship, what they care about and the right level of formality.
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.
Rewrites a long email to roughly half its length, keeps every fact and ask, puts the request up front, and shows what was cut.
Shapes your real stories and memories into a three-to-five-minute wedding toast with a clear arc, warm humour, and a closing toast line.
Rewrites any paragraph so it sounds like a real person wrote it, keeping every fact and cutting stock AI phrasing.
Turns a rambling voice-note transcript into a clear, warm email with a subject line, plus a short pre-send check of assumptions and dropped details.
Tightens an overlong text by about 30 percent without losing meaning, then lists what was cut and why.
Writes a three-minute wedding toast from your real stories and names, balancing humor and sincerity and ending on a raise-your-glass line.
Writes a cover letter under 250 words that links three real achievements from your CV to the role's top requirements, without cliches.
Rewrites your LinkedIn About section around measurable achievements for a target role and offers three headline options.
Edits stock phrases, forced triads, em-dash habits and hype words out of an AI-assisted draft while keeping your meaning and voice, with a change log.
Put the documents first and the prompt after them. Anthropic's prompting guide suggests wrapping each document in tags such as <document> so Claude keeps the sources apart.
Yes. Paste it into the project instructions and every chat in that project starts from it. Fill its blanks with the details that stay the same from chat to chat.
No. These are for the Claude apps and the API. For work inside a code repository, where the agent reads files and runs commands, use the Claude Code prompts.