30 Claude prompts for photographers

You are a wedding photographer building the must-have shot list before a wedding. <context> You're finalizing prep for a wedding next month and want a complete shot list organized by phase of the day so nothing gets missed during the fast-moving reception. </context> <inputs> - Couple names: [Sarah Ellison & Marcus Webb] - Ceremony time and key moments: [Ceremony 4:00 PM, unity candle lighting, no first look planned] - Family group shots needed: [Both sets of parents together, extended family group of 25, bridal party of 8] - Reception details: [First dance, father-daughter dance, bouquet toss, cake cutting at 8:00 PM] </inputs> <task> Build a phase-by-phase shot list covering getting ready, ceremony, family formals, and reception, with each family formal combination listed as its own line so nothing is skipped. </task> <constraints> - List every family formal combination individually (e.g., "Bride with both parents", "Full extended family group"), don't group them as one vague line. - Flag the two shots most likely to be missed if the timeline runs long (typically the first dance and cake cutting) with a note to prioritize them. - Keep the ceremony section shot list to moments only, no posed shots during the ceremony itself. </constraints> <format> A shot list organized under four headers (Getting Ready, Ceremony, Family Formals, Reception), each item as a short checklist line. </format>

You are a family portrait photographer planning an upcoming session. <context> A family of five is booked for an outdoor session and you want a shot list and pose progression that keeps young kids engaged instead of losing them halfway through. </context> <inputs> - Family composition: [Two parents, kids ages 7, 4, and 1] - Session length: [45 minutes] - Location: [Riverside Park, open field and a wooden bridge] - Parents' priority shot: [At least one full-family shot where everyone is looking at the camera and smiling] </inputs> <task> Build a shot list and pose sequence ordered from hardest (full group, everyone looking) to easiest (candid, kids playing), matched to a realistic time budget per segment. </task> <constraints> - Front-load the full-group posed shots in the first 15 minutes, before the youngest child gets tired. - Include at least 3 candid/movement-based shots (walking, piggyback, tickling) as a deliberate reset between posed segments. - Assign an approximate minute count per segment that sums to the 45-minute session. </constraints> <format> A shot list ordered by session minute, with columns: Time, Shot, Pose Direction. </format>

You are a photographer planning an outdoor engagement session around golden hour light. <context> A couple booked an engagement session and you need to plan locations and timing backward from sunset so the best light lines up with the best backdrop. </context> <inputs> - Session date and sunset time: [May 8, 2026, sunset at 8:04 PM] - Locations available: [A downtown brick alley, a lakeside pier, an open meadow] - Couple's stated style preference: [Relaxed and candid, not overly posed] - Session length: [90 minutes] </inputs> <task> Build a location and timing plan working backward from sunset, assigning each location a time block and stating why that light works there, ending with the meadow at golden hour. </task> <constraints> - Calculate actual clock times working backward from the stated sunset time, don't just say "start early." - Match the couple's relaxed, candid preference by noting looser walking-and-talking prompts rather than static poses for at least half the shot list. - Include a 10-minute travel buffer between each location. </constraints> <format> A timing plan table with columns: Time, Location, Light Notes, Shot Style, ending with a short list of 5 candid prompts to give the couple. </format>

You are a product photographer scoping a shoot for an e-commerce client. <context> A skincare brand booked a catalog shoot and you need a shot list that covers every angle their online store requires before you start setting up. </context> <inputs> - Client and product count: [Northfield Skincare, 8 SKUs] - Required shots per product: [Front label, 45-degree angle, lifestyle shot with a hand model, ingredient close-up] - Background requirements: [White background for catalog shots, a styled wood surface for lifestyle shots] - Deliverable format: [High-res JPEG and web-optimized WebP for each final image] </inputs> <task> Build a complete shot list covering every required angle per SKU, grouped by background setup so the shoot day is organized by lighting change rather than by product. </task> <constraints> - Group the shot list by background/lighting setup first, then by product within each setup, to minimize how often lighting gets rebuilt during the shoot. - State the total shot count and confirm it matches 8 SKUs times the required angles. - List both deliverable formats explicitly per shot, not as a general footnote. </constraints> <format> A shot list table with columns: Setup, Product, Angle, Deliverable Formats, grouped by setup. </format>

You are a newborn photographer planning a home session shot list with safety as the top priority. <context> You have a newborn session booked for a 10-day-old baby and need a shot list paired with a safety checklist, since newborn posing carries real physical risk if rushed. </context> <inputs> - Baby's age at session: [10 days] - Location: [Client's home, natural window light] - Parents' requested shots: [Close-up detail shots of hands and feet, a family shot with an older 3-year-old sibling, at least one posed sleeping shot] - Session length: [2 hours, with feeding and settling breaks built in] </inputs> <task> Build a shot list ordered from lowest-risk to any posed shots, paired with a safety checklist item next to any pose that requires spotting or support. </task> <constraints> - Mark every posed shot that requires a spotting hand or parent support directly on the same line, not in a separate section. - Schedule the sibling shot early, before the baby is likely to need a feeding break, since toddlers have a shorter patience window than newborns. - Include at least one buffer break in the 2-hour session explicitly in the shot list, not assumed. </constraints> <format> A shot list table with columns: Order, Shot, Safety Note, ending with the built-in feeding/settling break marked in its slot. </format>

You are a wedding photographer building a client-facing pricing guide. <context> You're updating your pricing guide for the upcoming season and want three clear tiers that make the mid-tier package the obvious best value. </context> <inputs> - Business name: [Hollow Light Photography] - Tiers to build: [Elopement, Classic, Premium] - Base costs to cover: [Second shooter costs $400/wedding, editing takes 15 hours per wedding at a $40/hour internal rate, album production costs $180] - Target price anchors: [Elopement around $1,200, Classic around $2,800, Premium around $4,500] </inputs> <task> Build a three-tier pricing guide with hours of coverage, deliverables, and price for each tier, then a short paragraph on why the Classic tier is the best value, referencing specific deliverables it includes that the others don't. </task> <constraints> - Each price must plausibly cover the stated costs (second shooter, editing hours, album) at that tier's inclusion level. - The best-value paragraph must reference at least two specific included deliverables, not just say "most popular." - List tiers side by side so a client can compare at a glance. </constraints> <format> A three-column pricing table (Elopement, Classic, Premium) followed by a short best-value paragraph. </format>

You are a portrait photographer running a limited seasonal mini-session promo. <context> You're offering fall mini-sessions for a short window and need a pricing sheet that creates urgency without sounding pushy. </context> <inputs> - Promo dates and slots: [October 4 and 5, 2026, 20-minute slots, 12 total spots] - Price and inclusions: [$175, 10 edited digital images, one 8x10 print] - Location: [Maple Hollow Farm, fixed backdrop, no location choice] - Add-on available: [Extra 10-image set for $50] </inputs> <task> Build a pricing sheet stating the fixed price, inclusions, the limited slot count, and the booking deadline, plus the optional add-on. </task> <constraints> - State the total slot count and that it's first-come, first-served, without using pressure language like "don't miss out." - List inclusions as a clear bullet list, not a paragraph. - Note plainly that location and time are fixed for this promo, not customizable. </constraints> <format> A one-page pricing sheet with a headline, bullet list of inclusions, price, and booking deadline line. </format>

You are a photographer building an add-on menu to increase average order value after a session. <context> Clients often ask about extra prints or albums after they see their gallery, and you want a clean add-on menu to send instead of answering the same questions one-off each time. </context> <inputs> - Base package: [Includes 20 edited digital images, no prints or album] - Add-ons and costs to you: [8x10 print $8 cost, album production $180 cost for a 20-page album, extra edited image $15 cost each] - Target margin: [At least 3x cost on physical products, at least 5x on extra digital images] </inputs> <task> Build an add-on menu with client-facing prices for prints, album, and extra digital images, each priced to hit the stated margin target. </task> <constraints> - Show the math for at least one item (cost times target margin equals price) so the pricing logic is checkable. - Round client-facing prices to clean numbers (e.g., $45, not $43.50). - Present the album as a bundled package price, not a per-page rate. </constraints> <format> An add-on menu table with columns: Item, Client Price, and a short pricing-logic note at the bottom. </format>

You are a commercial photographer building a usage-based rate card for brand clients. <context> Brand clients keep asking what it costs for different levels of image usage, and you want a rate card that prices by usage scope instead of negotiating from scratch every time. </context> <inputs> - Base creative fee: [$800 per half-day shoot, covers the shoot itself, not usage] - Usage tiers to price: [Website only, social media ads, print and out-of-home, national campaign] - Term length default: [12 months per usage tier, renewable] - Your positioning: [Mid-market local photographer, not a national agency rate] </inputs> <task> Build a rate card listing the base creative fee separately from usage licensing, with a price for each usage tier scaled to its reach, positioned for a mid-market client. </task> <constraints> - Keep the creative fee and usage fee as clearly separate line items, never bundled into one number. - Scale usage prices so each tier is meaningfully higher than the one before it, reflecting bigger reach. - Keep pricing realistic for a mid-market local photographer, not agency-level national campaign rates. </constraints> <format> A rate card table with columns: Usage Tier, Reach Description, 12-Month License Fee, plus the separate base creative fee stated above the table. </format>

You are a photographer responding to an inquiry from someone comparing your price against a cheaper competitor. <context> A potential client emailed asking if you can match a lower quote from another photographer, and you want to respond without discounting reflexively or sounding defensive. </context> <inputs> - Inquiry detail: [Client says another photographer quoted $1,200 for the same wedding package you quoted at $2,800] - What's actually included in your package that the cheaper quote likely excludes: [Second shooter, a 20-page album, a full-day timeline consultation] - Your stance: [Willing to explain the difference, not willing to match the price] </inputs> <task> Write a response email that asks one clarifying question about what's included in the cheaper quote, then explains the specific differences in your package without disparaging the other photographer. </task> <constraints> - Ask the clarifying question before assuming what the other quote does or doesn't include. - Name the specific inclusions (second shooter, album, consultation) rather than a vague "you get more value with us." - Do not offer a discount or price match anywhere in the response. </constraints> <format> A short, professional email with subject line, ready to send as-is. </format>

You are a photographer responding to a first-time inquiry from a potential client. <context> Someone filled out your contact form asking about availability and pricing, and a fast, specific first response matters more than almost anything else in booking them. </context> <inputs> - Inquiry details given: [Looking for a family session in October, mentioned 3 kids and wanting "natural, not too posed" photos] - Your availability: [Two Saturday slots open in October, the 10th and the 24th] - Starting price to mention: [Sessions start at $350] - Next step you want them to take: [Reply with a preferred date or book directly via your online calendar link] </inputs> <task> Write a warm, specific response email that reflects their stated style preference back to them, offers the two specific open dates, states the starting price, and gives one clear next step. </task> <constraints> - Reference their exact phrase ("natural, not too posed") somewhere in the email, don't paraphrase it away. - Offer the two specific dates by name, not "let me know what works." - End with exactly one call to action, not multiple competing ones. </constraints> <format> A ready-to-send email with subject line. </format>

You are a photographer preparing a pre-session questionnaire for a newly booked client. <context> A client just booked a portrait session and you want to learn their goals and any concerns before the shoot day instead of discovering them on location. </context> <inputs> - Session type: [Personal branding headshots] - Client's stated goal from booking: [Needs new photos for LinkedIn and a speaker bio after a recent promotion] - Session length: [45 minutes, studio location] - Info you still need: [Wardrobe plan, any features they're self-conscious about, whether they want indoor or outdoor-style backdrops] </inputs> <task> Write a short pre-session questionnaire covering goals, wardrobe, comfort concerns, and backdrop preference, framed to make the client feel comfortable answering honestly. </task> <constraints> - Ask the comfort/self-consciousness question gently and normalize it, don't make it feel like a clinical checkbox. - Reference their stated goal (LinkedIn, speaker bio) in at least one question about desired tone. - Keep the questionnaire to 8 questions or fewer. </constraints> <format> A numbered questionnaire, ready to send as a form or email. </format>

You are a photographer sending a pre-session reminder with styling guidance. <context> A family session is coming up in a few days and you want to send a reminder that reduces last-minute wardrobe stress and no-shows. </context> <inputs> - Session date, time, location: [September 12, 2026, 5:30 PM, Riverside Park north entrance] - Family composition: [Two parents, three kids ages 7, 4, and 1] - Season and location backdrop: [Early fall, open field with warm-toned foliage] - Common styling mistakes you want to prevent: [Head-to-toe matching outfits, logos or graphic tees, white sneakers with formal outfits] </inputs> <task> Write a reminder email with the session logistics restated, plus a what-to-wear guide with color palette suggestions that complement the fall foliage backdrop, and what to avoid. </task> <constraints> - Restate the exact date, time, and meeting location in the first two lines. - Suggest a specific color palette (named colors, not just "fall colors") that would photograph well against the described backdrop. - List the styling mistakes to avoid as a short, non-judgmental bullet list. </constraints> <format> A reminder email with logistics up top and a short styling guide below, ready to send as-is. </format>

You are a photographer following up with a lead who inquired but went quiet. <context> Someone inquired about a session two weeks ago, seemed interested, and then stopped responding after you sent pricing, and you want one more low-pressure touch before letting the lead go cold. </context> <inputs> - Original inquiry detail: [Asked about a maternity session, mentioned being due in November] - Last contact: [You sent pricing and availability 14 days ago, no response since] - Availability update: [You now have one additional Saturday open in late October] - Tone you want: [Warm, no pressure, easy to ignore without guilt] </inputs> <task> Write a short follow-up email that references their original interest, mentions the new availability, and gives them an easy way to say "not right now" without feeling awkward. </task> <constraints> - Reference the maternity timing detail (due in November) to show the follow-up isn't generic. - Explicitly give them permission to not respond if timing isn't right, in one sentence. - Keep the email under 80 words. </constraints> <format> A short, ready-to-send follow-up email with subject line. </format>

You are a photographer responding to a client who is unhappy with the retouching on their delivered gallery. <context> A client emailed saying the skin retouching on their portraits looks "too smooth and fake," and you need to respond professionally and offer a fix without being defensive. </context> <inputs> - Client's specific complaint: [Says skin looks "plastic" in 3 of the 20 delivered images] - Your retouching process: [Standard frequency separation smoothing applied uniformly across the gallery] - What you can offer: [Re-edit the flagged images with lighter retouching within 3 business days] </inputs> <task> Write a response that acknowledges the specific complaint without being defensive, explains briefly what happened, and offers the concrete fix with a timeline. </task> <constraints> - Acknowledge the specific images and complaint, don't respond generically to "feedback about the photos." - Do not over-explain or justify the technique at length, one short sentence of context is enough. - State the exact turnaround time for the re-edit. </constraints> <format> A short, professional email with subject line, ready to send as-is. </format>

You are a photographer delivering a finished gallery to a client. <context> A client's gallery is ready and you need a delivery email that explains how to download, what their print rights are, and how long the gallery stays live. </context> <inputs> - Client name and session type: [The Ferraro Family, outdoor family session] - Gallery link and hosting: [Pixieset gallery, link active for 12 months] - Print rights: [Personal use print release included, no rights for resale or commercial use] - Number of images delivered: [42 edited images] </inputs> <task> Write a delivery email that states the image count, the gallery link and how long it stays active, and the exact scope of the print release. </task> <constraints> - State the print release scope precisely (personal use only, no resale/commercial), not just "you can print these." - Mention the 12-month gallery availability explicitly with a note to download a personal backup before it expires. - Keep the email warm but under 150 words. </constraints> <format> A ready-to-send delivery email with subject line. </format>

You are a wedding photographer building a repeatable editing workflow checklist. <context> You just shot a wedding with 2,400 raw images and want a structured editing workflow so the batch process stays consistent and doesn't balloon past your usual turnaround. </context> <inputs> - Raw image count: [2,400 images from an 8-hour wedding] - Target final delivered count: [450 to 500 edited images] - Turnaround promised to client: [6 weeks] - Editing steps you currently use: [Cull in Lightroom, batch color correction, selective retouching on hero shots only, export in two sizes] </inputs> <task> Build a step-by-step editing workflow checklist from import through final delivery, with a rough time estimate per stage and a checkpoint for the culling ratio (aiming for the stated final count range). </task> <constraints> - Include a checkpoint after culling that confirms the selected count is on track for the 450 to 500 target, with a note on what to do if it's off. - Order steps so batch color correction happens before any selective retouching, not after. - Fit the total estimated time within a schedule that supports the 6-week promised turnaround. </constraints> <format> A checklist with stages in order, each with a time estimate and any checkpoint notes. </format>

You are a photographer proposing an album design to a wedding client. <context> A couple's gallery is delivered and you want to pitch a printed album as an add-on, with a proposed spread layout based on their actual top images. </context> <inputs> - Couple names: [Sarah Ellison & Marcus Webb] - Album size and page count offered: [10x10 inch, 20 pages / 10 spreads] - Top image categories from their gallery: [Getting ready, ceremony, family formals, reception dancing, a few candid detail shots] - Price: [$580 for the 20-page album, layflat pages] </inputs> <task> Propose a spread-by-spread album layout allocating pages across the stated image categories, weighted toward the categories most couples want featured (ceremony and reception), with the price stated clearly. </task> <constraints> - Allocate more spreads to ceremony and reception than to getting-ready or detail shots, and state the reasoning briefly. - Show the spread count per category and confirm it sums to 10 spreads total. - State the price once, clearly, not repeated multiple times in the pitch. </constraints> <format> A short proposal with a spread allocation table (Category, Spreads) followed by a one-paragraph pitch and the price. </format>

You are a photographer who is behind on a promised gallery delivery date. <context> You promised a 4-week turnaround and you're now a week past that with no gallery sent yet, and you need to communicate the delay honestly with a real new date. </context> <inputs> - Client and session: [The Ferraro Family, family session shot 5 weeks ago] - Original promised turnaround: [4 weeks] - Reason for the delay: [A backlog from wedding season, being upfront without over-explaining] - New firm delivery date: [Exactly 6 days from today] </inputs> <task> Write an apology email that states the delay plainly, gives one honest reason without over-justifying, and commits to a specific new delivery date. </task> <constraints> - State the new delivery date as a specific date, not "very soon" or "early next week." - Keep the explanation for the delay to one sentence, don't over-apologize across multiple paragraphs. - Offer one small goodwill gesture (e.g., 3 extra edited images) tied to the delay. </constraints> <format> A short, direct apology email with subject line, ready to send as-is. </format>

You are a lead photographer delegating first-pass culling to an assistant editor. <context> You're bringing on a part-time editor to help with first-pass culling and need a written brief so their selections match your standards without you reviewing every single image. </context> <inputs> - Shoot type: [Wedding, 2,400 raw images] - Target cull-down count: [Reduce to roughly 900 images for your own second-pass review] - Known quality issues to reject automatically: [Closed eyes, motion blur, duplicate near-identical frames, backs of heads in a moment meant to be a face shot] - What to flag instead of reject: [Anything technically fine but where they're unsure if it's a "hero" shot] </inputs> <task> Write a culling criteria brief listing automatic-reject conditions, a target count range, and what should be flagged for your review instead of decided independently. </task> <constraints> - List automatic-reject conditions as an explicit, unambiguous checklist, no room for editor judgment on those specific issues. - State the target count range explicitly so the editor has a concrete goal, not just "cull down a lot." - Make clear that "hero shot" judgment calls get flagged, not decided, by the assistant editor. </constraints> <format> A brief document with sections: Automatic Rejects, Target Count, Flag for Review, ready to hand off to a new editor. </format>

You are a photographer building a homepage for your studio's portfolio website. <context> You need a single-page HTML homepage that showcases your work and makes it obvious how to inquire, without hiring a web developer. </context> <inputs> - Studio name and specialty: [Hollow Light Photography, wedding and portrait] - Sections needed: [Hero with tagline, a 6-image showcase grid with placeholder image blocks, a short about blurb, an inquiry call-to-action] - Brand colors: [Warm cream background, deep charcoal text, one terracotta accent color] - Contact action: [A "Start Your Inquiry" button linking to a contact email] </inputs> <task> Build a complete, self-contained single-page HTML homepage with the stated sections, using the brand colors, styled inline or in a style tag, with placeholder colored blocks standing in for the 6 showcase images. </task> <constraints> - Output valid, self-contained HTML with inline or embedded CSS, no external dependencies or broken links. - Use the exact stated color palette, don't substitute different colors. - Make the showcase grid responsive so it doesn't break on a narrow screen. </constraints> <format> A single, complete HTML document that can be opened directly in a browser or previewed as a live artifact. </format>

You are a wedding photographer building a showcase page for a real wedding on your website. <context> You want a dedicated page for a recent wedding that reads like a mini editorial story, to show prospective couples what a full gallery from you looks like. </context> <inputs> - Couple names and venue: [Sarah & Marcus, Cedar Ridge Vineyard] - Story beats to include: [A short intro paragraph, a getting-ready section, ceremony section, reception section, each with a placeholder image block] - Style notes: [Warm, editorial tone, minimal text, let the images (placeholder blocks) carry the page] - Call to action at the bottom: [Link to the pricing guide page] </inputs> <task> Build a single-page HTML wedding showcase with a short editorial intro, three story sections each with a placeholder image block, and a closing call to action linking to the pricing page. </task> <constraints> - Keep all body text minimal, under 40 words per section, so placeholder image blocks are visually dominant. - Output valid, self-contained HTML with embedded CSS, no external dependencies. - Make the closing call-to-action visually distinct from the story sections (different background or button style). </constraints> <format> A single, complete HTML document ready to preview as a live artifact. </format>

You are a photographer writing the About page for your studio website. <context> You need an About page that builds trust with a prospective client, not just a resume of gear and years in business. </context> <inputs> - Photographer name and years shooting: [Dana Whitfield, 7 years] - Personal detail that shapes your work: [Started shooting weddings after doing photojournalism for a local paper, still shoots candid moments over posed ones] - Specialty and location: [Wedding and portrait photography, based in Asheville, NC, travels regionally] - Call to action: [Link to the contact/inquiry page] </inputs> <task> Build a single-page HTML About page with a short bio that leads with the personal detail (photojournalism background) rather than a gear or credentials list, and a closing call to action. </task> <constraints> - Lead the bio with the personal story detail, don't open with years of experience or equipment. - Keep the bio to 3 short paragraphs, no long-form essay. - Output valid, self-contained HTML with embedded CSS. </constraints> <format> A single, complete HTML document ready to preview as a live artifact. </format>

You are a photographer writing social media captions to promote a recent shoot. <context> You just delivered a styled engagement session and want to post it to Instagram with a caption that drives profile visits from engaged couples, not just likes. </context> <inputs> - Session type and location: [Engagement session, downtown brick alley and a lakeside pier] - Couple detail worth mentioning: [They got engaged at that same pier six months ago] - Call to action goal: [Get profile visits from other engaged couples planning a session] - Posting count needed: [One main carousel caption plus 2 alternate short captions for single-image posts] </inputs> <task> Write one main caption referencing the couple's engagement story detail, plus two shorter alternate captions for single-image posts, each ending with a call to action to book a session, and a relevant hashtag set. </task> <constraints> - Reference the specific engagement-at-the-pier detail in the main caption, not a generic engagement session description. - Keep each alternate caption under 30 words. - Provide one hashtag set of 15 to 20 tags mixing location-based and photography-niche tags, no banned or irrelevant tags. </constraints> <format> One main caption, two short alternate captions, and one hashtag set, each clearly labeled. </format>

You are a photographer building a short email campaign to generate referrals and reviews from past clients. <context> You have a list of past clients who haven't been asked for a review or referral yet, and want a simple two-email sequence to prompt both without sounding transactional. </context> <inputs> - Client segment: [Family and portrait clients from the last 12 months, roughly 60 people] - Incentive offered for referrals: [$25 credit toward a future session for both the referrer and the new client] - Review platforms to link: [Google and Facebook] - Sending cadence: [Email 1 now, Email 2 two weeks later only to non-responders] </inputs> <task> Write a two-email sequence: Email 1 asks for a review with direct platform links, Email 2 (for non-responders) pivots to the referral offer with the credit amount stated clearly. </task> <constraints> - Keep the review ask in Email 1 to one clear sentence with both platform links, not a long pitch. - State the exact referral credit amount in Email 2, not "a nice discount." - Make clear Email 2 is only sent to people who didn't respond to Email 1, not the full list again. </constraints> <format> Two labeled emails (Email 1: Review Ask, Email 2: Referral Offer), each with subject line, ready to load into an email tool. </format>