One-Page Brand Voice Brief Builder from Copy Samples for ChatGPT, Claude and Gemini
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.
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.
28 results · page 1 of 2
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.
Uses web search to produce a one-page account brief with priorities, dated news and links, likely stakeholders, and three personalized openers.
Builds a day-by-day revision calendar that counts back from your exam date, with spaced reviews and timed practice sessions.
Turn a business idea and target customer into a ranked list of risky assumptions, five interview questions and a $100 test to run in two weeks.
Builds a short style guide from three of your writing samples, then writes a new piece in that voice and notes which rules were applied.
Produces a dated, linked summary of the past week's AI model and tool releases that matter to your team, plus one experiment to run.
Turns a repetitive task into a build-ready automation spec with triggers, AI steps, human checkpoints, failure handling and a test plan.
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.
Calculate a sustainable hourly and project rate from your income target and billable hours, covering tax, unpaid admin time and expenses with the math shown.
Guides you through criteria and weights, scores each option in a table, then runs a pre-mortem on the top choice.
Creates a side-by-side test plan for choosing an AI model for your use case, with 10 test prompts, a scoring rubric and a blank results table.
Turns pasted API docs or a function list into agent-ready tool names, descriptions, JSON input schemas and when-to-use and when-not-to-use notes.
Produces Meta and Google ad copy across five distinct angles within platform character limits, plus a simple test plan with decision rules.
Builds a playbook that answers the eight most likely objections for your product and buyer, each in four steps with honest evidence.
Compare the avalanche and snowball methods on months to debt-free and total interest using your own debts and extra payment, as education only.
Converts a successful chat transcript into a reusable prompt template with at most three named variables and a one-line note on when to use it.
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Produces a 3-5 subagent roster with system prompts, minimal tool permissions, model tiers and explicit handoff rules for your project.
Builds a neighborhood-clustered itinerary with downtime and rainy-day backups that fits your budget and travel style.
Designs a four-agent pipeline for your report type with each agent's prompt, inputs, outputs and handoff format.
Names likely blind spots from your goals and struggles, quotes your own words as evidence, and suggests three small experiments as reflective coaching, not therapy.
A SKILL.md that makes Claude write and edit in your brand's voice: it reads a VOICE.md in the project, or builds one from samples, then checks every draft against it.
A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.
Pulls the central claims out of a long report or paper, with page numbers, the evidence behind each claim and how strong it is, so you can cite or challenge it quickly.
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.