30 Claude Prompts That Build Reusable Templates

You are a creative director who standardizes campaign work with reusable creative brief templates. <context> I need a reusable creative brief template that aligns everyone before a project kicks off. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Type of work: [CAMPAIGN / AD / VIDEO / DESIGN] - Who fills this in: [MARKETER / CLIENT / PM] - Who executes it: [DESIGNER / AGENCY / WRITER] - Approval chain: [WHO SIGNS OFF] - Detail level: [LEAN / FULL] </inputs> <task> Build a creative brief template with: project name and owner, background/context, the single objective, target audience, the core message/insight, key deliverables and formats, mandatories (logo, legal, brand rules), tone and references, budget and timeline with key dates, and success metrics. Use [bracketed] placeholders and keep each field to a prompt like 'In one sentence...'. </task> <constraints> - Force a single primary objective, not a wish-list. - Every field is a labeled placeholder with a guiding question. - Keep it to one page so people actually fill it in. </constraints> <format> Return the template as a Markdown code block, then a note on the one field that most often gets skipped and why it matters. Ready to use. </format>

You are a senior product manager who standardizes specs with a reusable PRD template. <context> I need a reusable product requirements document template for scoping a feature so engineering and design have one source of truth. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Product area: [WEB / MOBILE / API / INTERNAL TOOL] - Team size and process: [SCRUM / KANBAN / SMALL TEAM] - How you write requirements: [USER STORIES / JOBS-TO-BE-DONE] - Rigor level: [LIGHTWEIGHT / DETAILED] - Reviewers: [ENG / DESIGN / STAKEHOLDERS] </inputs> <task> Build a PRD template with: a header (feature name, author, status, last updated), the problem and why now, goals and non-goals, target users and their job-to-be-done, user stories or requirements list (each with acceptance criteria), UX notes/flows placeholder, success metrics, dependencies and risks, an open-questions list, and a rollout plan. Use [bracketed] placeholders and a checkbox format for requirements. </task> <constraints> - Include an explicit 'non-goals' section to prevent scope creep. - Each requirement needs an acceptance-criteria placeholder. - Add a one-line prompt under each section on what to write. </constraints> <format> Return the template as a Markdown code block, then a filled example user story with acceptance criteria. Ready to use. </format>

You are a design lead who briefs projects with a reusable design brief template. <context> I need a reusable design brief template so every design request arrives with the context a designer needs. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Design type: [BRAND / UI / PRINT / SOCIAL] - Who requests design: [MARKETING / FOUNDER / PM] - Brand assets available: [GUIDELINES / LOGO / NONE] - Deliverable format needed: [FIGMA / PNG / PDF / SIZES] - Detail level: [QUICK / THOROUGH] </inputs> <task> Build a design brief template with: request title and requester, the problem/goal, deliverable(s) and exact specs (sizes, formats, quantity), audience and where it will be used, brand and style constraints (colors, fonts, do's and don'ts), reference examples (links/attachments placeholder), copy or content to include, timeline and review dates, and approval owner. Use [bracketed] placeholders and a guiding question per field. </task> <constraints> - Deliverable specs (sizes, formats) are mandatory placeholder fields. - Include a 'references' slot so requesters show, not just tell. - Keep it to one page. </constraints> <format> Return the template as a Markdown code block, then a note on the fields that prevent the most back-and-forth revisions. Ready to use. </format>

You are an SEO content strategist who briefs writers with a reusable content brief template. <context> I need a reusable content brief template so writers produce on-target, search-optimized articles the first time. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Content type: [BLOG / LANDING / GUIDE / COMPARISON] - Primary keyword focus: [TARGET KEYWORD] - Audience and intent: [WHO / WHAT THEY WANT] - Word count target: [RANGE] - Brand voice: [DESCRIBE] </inputs> <task> Build a content brief template with: working title and target keyword, search intent and audience, word-count range, a suggested H2/H3 outline placeholder, key points and questions to answer (People-Also-Ask style), secondary keywords/entities to include, internal and external links to add, a CTA and next step, tone/voice notes, and SEO fields (meta title, meta description placeholders). Use [bracketed] placeholders and a guiding note per field. </task> <constraints> - Include an outline slot and a 'questions to answer' list to steer structure. - Keyword, meta title, and meta description are mandatory placeholder fields. - Add a one-line instruction under each section. </constraints> <format> Return the template as a Markdown code block, then a note on how to turn the brief into a first-draft prompt for a writer. Ready to use. </format>

You are a staff engineer who standardizes design decisions with a reusable RFC (technical spec) template. <context> I need a reusable technical spec / RFC template for proposing and reviewing engineering designs. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Type of work: [NEW SERVICE / MIGRATION / API / REFACTOR] - Team and stack: [LANGUAGES / SYSTEMS] - Review process: [ASYNC COMMENTS / DESIGN REVIEW MEETING] - Rigor level: [LIGHTWEIGHT / FORMAL] - Reviewers: [WHO SIGNS OFF] </inputs> <task> Build an RFC template with: a header (title, author, status, reviewers, date), a summary, the problem/motivation, goals and non-goals, the proposed design (with a placeholder for a diagram), alternatives considered (short table: option / trade-offs), impact on other systems, security and data considerations, a rollout and rollback plan, testing strategy, open questions, and a decision-log line. Use [bracketed] placeholders throughout. </task> <constraints> - 'Alternatives considered' and 'non-goals' are required sections. - Neutral, evidence-based tone; trade-offs stated explicitly. - Add a one-line prompt under each section on what to write. </constraints> <format> Return the template as a Markdown code block, then a note on how to keep the RFC short enough that people actually review it. Ready to use. </format>

You are an operations lead who runs tight meetings using reusable agenda templates. <context> I need a reusable team meeting agenda template that keeps recurring meetings focused and on time. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields and time boxes. </context> <inputs> - Meeting type: [WEEKLY SYNC / STANDUP / PROJECT] - Duration: [15 / 30 / 60 MIN] - Recurring or one-off: [CADENCE] - Attendees: [TEAM / ROLES] - Priority: [DECISIONS / UPDATES / BLOCKERS] </inputs> <task> Build a team meeting agenda template with: a header (meeting name, date, time, facilitator, note-taker), a one-line objective ('this meeting is a success if...'), a time-boxed agenda table (topic / owner / minutes / desired outcome), a decisions-made section, an action-items table (action / owner / due), and a parking-lot list for off-topic items. Use [bracketed] placeholders and pre-fill the time-box column so the totals match the duration. </task> <constraints> - Every agenda item has an owner and a time box. - Force a single meeting objective at the top. - Include a filling note under each section. </constraints> <format> Return the template as a Markdown code block, then a note on how to run the meeting so it ends on time. Ready to use. </format>

You are an experienced people manager who runs great 1:1s using a reusable agenda template. <context> I need a reusable 1:1 agenda template for recurring manager/report check-ins that stays consistent week to week. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Relationship: [MANAGER-REPORT / SKIP-LEVEL / MENTOR] - Cadence: [WEEKLY / BIWEEKLY] - Focus balance: [SUPPORT / GROWTH / PERFORMANCE] - Who drives it: [REPORT-LED / SHARED] - Tone: [CASUAL / STRUCTURED] </inputs> <task> Build a 1:1 agenda template with: a header (names, date), a 'wins and how you're doing' check-in, 'their topics first' section, 'my topics', a blockers/support-needed area, a growth-and-goals section, feedback both ways, and an action-items list carried over between meetings. Use [bracketed] placeholders and mark which sections the report fills before the meeting. </task> <constraints> - Put the report's topics before the manager's. - Include a carried-over action-items area so nothing drops. - Add a guiding question under each section. </constraints> <format> Return the template as a Markdown code block, then 3 rotating growth questions to keep 1:1s from getting stale. Ready to use. </format>

You are a chief of staff who prepares reusable board and stakeholder meeting agenda templates. <context> I need a reusable board or stakeholder meeting agenda template that keeps senior audiences focused on decisions. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Meeting type: [BOARD / INVESTOR UPDATE / EXEC REVIEW] - Duration: [60 / 90 MIN] - What they need to decide: [DECISIONS] - Metrics they track: [KEY KPIS] - Materials sent in advance: [DECK / MEMO] </inputs> <task> Build a board/stakeholder agenda template with: a header (meeting, date, attendees, pre-reads), an objective line, a time-boxed agenda table (topic / presenter / minutes / decision or discussion), a 'key metrics' dashboard placeholder, 'decisions needed today' called out explicitly, a risks/asks section, and a next-steps and action-items table. Use [bracketed] placeholders and clearly flag which items require a vote or decision. </task> <constraints> - Separate 'FYI' items from 'decision needed' items visually. - Pre-read reference is a mandatory field so meeting time is for discussion. - Include a filling note under each section. </constraints> <format> Return the template as a Markdown code block, then a note on how to structure pre-reads so the meeting stays decision-focused. Ready to use. </format>

You are an agile coach who standardizes ceremonies with reusable agenda templates. <context> I need a reusable sprint planning agenda template that gets the team to a committed, realistic sprint backlog. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Framework: [SCRUM / KANBAN / SHAPE-UP] - Sprint length: [1 / 2 WEEKS] - Team size and capacity method: [POINTS / HOURS] - Tooling: [JIRA / LINEAR / TRELLO] - Include retro?: [YES / NO] </inputs> <task> Build a sprint planning agenda template with: a header (sprint number, dates, facilitator), the sprint goal (one sentence), a capacity check (team availability placeholder), a backlog-review and prioritization block, a commitment table (item / estimate / owner / acceptance criteria), a dependencies/risks list, a definition-of-done reminder, and a section for the sprint goal restated. Use [bracketed] placeholders and pre-label the commitment table columns. </task> <constraints> - Force a single-sentence sprint goal before committing items. - Capacity must be accounted for before scope is set. - Add a one-line instruction under each section. </constraints> <format> Return the template as a Markdown code block, then an optional retro add-on section (what went well / what to change). Ready to use. </format>

You are an account manager who runs polished client kickoffs from a reusable agenda template. <context> I need a reusable client kickoff agenda template that starts a new engagement with alignment and confidence. Build it as a self-contained, copy-paste Markdown artifact with clear placeholder fields. </context> <inputs> - Engagement type: [PROJECT / RETAINER / IMPLEMENTATION] - Who attends: [OUR TEAM / CLIENT ROLES] - Duration: [30 / 60 MIN] - What must be agreed: [SCOPE / TIMELINE / COMMS] - Tone: [FORMAL / RELAXED] </inputs> <task> Build a client kickoff agenda template with: a header (client, project, date, attendees), a welcome and introductions round, a restated project goal and success criteria, a scope and deliverables recap, a timeline and milestones walkthrough, roles and responsibilities (who owns what, incl. client side), a communication and tools plan (cadence, channels, points of contact), risks/assumptions, and next steps with owners and dates. Use [bracketed] placeholders throughout. </task> <constraints> - Confirm the communication cadence and single points of contact explicitly. - Restate success criteria in the client's terms. - Include a filling note under each section. </constraints> <format> Return the template as a Markdown code block, then a note on the one question to ask that surfaces hidden client expectations. Ready to use. </format>

You are a personal-branding writer who builds reusable LinkedIn post templates that get engagement. <context> I need a reusable LinkedIn post template with a proven structure I can refill for any topic. Build it as a self-contained, copy-paste artifact with clearly marked fill-in slots, not a single finished post. </context> <inputs> - Post type: [STORY / LESSON / HOW-TO / HOT TAKE] - My niche and audience: [TOPIC / WHO] - The goal: [FOLLOWERS / LEADS / AUTHORITY] - Voice: [PUNCHY / THOUGHTFUL / CONTRARIAN] - CTA style: [COMMENT / FOLLOW / DM] </inputs> <task> Build a LinkedIn post template with: 3 scroll-stopping hook-line options for the first sentence, a line-break structure guide showing where white space goes, [FILL-IN] slots for the setup, the turning point, the lesson, and 2-3 takeaway bullets, a re-hook/CTA line, and a placeholder for 3-5 hashtags. Add a short note above each slot explaining what to write and keep it optimized for the mobile 'see more' cut-off. </task> <constraints> - The hook must earn the 'see more' click; front-load the payoff. - Short lines and white space; no dense paragraphs. - Include a fill-in legend listing every slot. </constraints> <format> Return the template as a copy-paste block, then the legend and 2 tips for adapting the same template to different post types. Ready to use. </format>

You are a content operations manager who builds reusable content calendar templates. <context> I need a reusable content calendar template to plan and track posts across channels. Build it as a self-contained, copy-paste artifact - a clean table with clearly labeled columns and placeholder rows. </context> <inputs> - Channels I post to: [BLOG / LINKEDIN / X / INSTAGRAM / EMAIL] - Cadence: [POSTS PER WEEK] - Content pillars/themes: [2-4 PILLARS] - Team roles: [WRITER / DESIGNER / APPROVER] - Planning horizon: [MONTHLY / QUARTERLY] </inputs> <task> Build a content calendar as a table with columns for: publish date, channel, content pillar/theme, working title/topic, format (post/video/article), status (idea/drafting/review/scheduled/published), owner, CTA/goal, and asset link. Pre-fill 5-8 placeholder rows spread across the channels and pillars so the pattern is clear. Above the table, add a small 'pillars & cadence' key. Use [bracketed] placeholders in every cell. </task> <constraints> - Fixed column order so it stays consistent as it grows. - Include a status column with the exact stage values to use. - Add a one-line note on how to sort or filter it in a spreadsheet. </constraints> <format> Return the calendar as a Markdown table (copy-paste into Sheets/Notion), then a note on how to turn it into a repeatable weekly workflow. Ready to use. </format>

You are a newsletter editor who standardizes issues with a reusable template. <context> I need a reusable newsletter issue template with a consistent structure my readers recognize each week. Build it as a self-contained, copy-paste artifact with clearly marked fill-in sections. </context> <inputs> - Newsletter name and topic: [NAME + NICHE] - Cadence: [DAILY / WEEKLY] - Recurring segments I want: [E.G. INTRO, MAIN STORY, LINKS, TIP] - Voice: [SMART / FUN / EXPERT] - CTA per issue: [REPLY / CLICK / SHARE] </inputs> <task> Build a newsletter template with: a subject-line + preview-text pair (with 2 alternates), a short personal intro slot, a main-story section with a fill-in headline and body slots, a curated 'links/roundup' block with [Title + one-line why] repeating rows, a quick tip or takeaway box, a single CTA, and a sign-off with a P.S. slot. Add a note above each section on what belongs there and keep segment names fixed for consistency. </task> <constraints> - Subject line and preview text are mandatory paired fields. - Keep recurring segment names identical each issue. - Include a fill-in legend of every section. </constraints> <format> Return the template as a copy-paste block, then the legend and a note on which section drives the most clicks and replies. Ready to use. </format>

You are a B2B content marketer who builds reusable customer case study templates. <context> I need a reusable case study template that turns a customer win into a persuasive, skimmable story. Build it as a self-contained, copy-paste Markdown artifact with clearly labeled fill-in fields. </context> <inputs> - What we sell: [PRODUCT / SERVICE] - Typical customer: [INDUSTRY / SIZE] - The outcome we usually drive: [RESULT TYPE] - Proof we can show: [METRICS / QUOTES] - Length: [SHORT / FULL] </inputs> <task> Build a case study template with: a headline formula ([Result] for [Customer type]), an at-a-glance results box (2-4 metric placeholders), a customer snapshot (industry, size, role), the Challenge, the Solution (how they used us), the Results (with metric placeholders and a pull-quote slot), and a short CTA. Use [bracketed] placeholders throughout and give the headline as a reusable formula, not a fixed title. </task> <constraints> - Follow a Challenge -> Solution -> Results arc. - All metrics and quotes are placeholders; no invented data. - Include a filling note under each section. </constraints> <format> Return the template as a Markdown code block, then a short list of interview questions that will fill in every section. Ready to use. </format>

You are a short-form video strategist who builds reusable script templates for Reels, TikTok, and Shorts. <context> I need a reusable short-form video script template with a hook-retention-payoff structure I can refill for any topic. Build it as a self-contained, copy-paste artifact with clearly marked fill-in slots. </context> <inputs> - Platform: [TIKTOK / REELS / SHORTS] - Video length: [15 / 30 / 60 SEC] - Niche and audience: [TOPIC / WHO] - Goal: [FOLLOWS / SAVES / SALES] - Style: [TALKING HEAD / VOICEOVER / TUTORIAL] </inputs> <task> Build a video script template as a two-column layout (spoken line / on-screen text or B-roll cue) with rows for: a 3-second hook (with 3 hook options), the setup, 2-3 value beats, a pattern-interrupt/retention cue, the payoff, and a CTA. Add a suggested-seconds marker per row and a caption + hashtag slot below. Use [FILL-IN] placeholders and a note above each row on what to say. Keep total spoken length within the chosen duration. </task> <constraints> - The hook occupies the first 3 seconds and must be swappable. - Pair every spoken line with an on-screen or B-roll cue. - Include a slot for caption and hashtags. </constraints> <format> Return the template as a copy-paste block (two-column table), then 2 tips for reusing one script structure across many topics. Ready to use. </format>