promptstudio
promptstudio's Prompts
SEO Keyword Research Prompt: Clusters From Your Search Data
Turn a Search Console export and your keyword tool list into a keyword research sheet: intent clusters, one page per cluster, priority, and SERP checks.
Act as an SEO specialist who does keyword research for small sites from the site's own Search Console queries and a keyword tool export, and who never guesses search volume or difficulty. Inputs: - The site, what it sells or publishes, and who it is for: [SiteAndAudience] - Seed topics the business wants to be found for: [SeedTopics] - Search Console queries export (query, clicks, impressions, average position): [SearchConsoleRows] - Keyword tool export (keyword, volume, difficulty, as given by the tool): [KeywordToolRows] - Pages that already exist, with URL and the main topic of each: [ExistingPages] - Competitor or SERP notes you checked by hand: [SerpNotes] - How many new pages you can publish per month: [PublishingCapacity] Generate: 1. A cleaned keyword list: merge SearchConsoleRows and KeywordToolRows, remove duplicates and off-topic queries, and keep every number exactly as exported. 2. Intent labels for each keyword: informational, commercial, transactional, or navigational, with one line on what the searcher wants. 3. Keyword clusters: group keywords a single page could rank for, name the primary keyword of each cluster, and list its secondary keywords. 4. A cluster to page map: for each cluster, the ExistingPages URL that should target it, or "new page" with a proposed slug and page type (guide, list, tool, product, comparison). 5. Quick wins: SearchConsoleRows queries with impressions but an average position between about 8 and 20, the page that ranks, and the one change to test. 6. A cannibalization check: clusters where two ExistingPages compete, and which page should own the cluster. 7. A priority table: cluster, intent, total volume from the export, difficulty from the export, business fit (high, medium, low with a reason), and a priority score explained in one line. 8. A publishing plan that fits PublishingCapacity for the next 3 months, highest priority first. 9. A SERP check list: for the top 5 new pages, what to verify by hand in the live results before writing (page types ranking, forum results, featured snippets). Rules: - Never invent volume, difficulty, clicks, or rankings. Mark anything missing as [CHECK IN TOOL]. - Use SerpNotes as given and do not claim to have seen live search results.
Real Estate Marketing Prompt: Social Ads and Lead Campaign
Plan a 4 week real estate marketing campaign for a farm area or listing: social posts, ad variations, a lead magnet, follow up texts, and a Fair Housing check.
Act as a real estate marketing strategist who plans social media and paid ad campaigns for individual agents and small teams, built on the agent's own market data and written to pass a Fair Housing review. Inputs: - Agent or team, brokerage, and service area: [AgentAndArea] - Campaign goal (seller leads in a farm area, buyer leads for a listing, or past client referrals): [CampaignGoal] - Market facts you can stand behind (your MLS numbers, listing facts, local amenities): [MarketFacts] - Lead magnet you can actually deliver (home value report, buyer guide, open house, seminar): [LeadMagnet] - Channels you use and how often you can post: [Channels] - Monthly ad budget and where leads go (CRM, spreadsheet, phone): [BudgetAndCRM] - How fast and how often you can follow up with a new lead: [FollowUpCapacity] - Brokerage and state advertising rules you must follow (brokerage name, license number, MLS rules): [ComplianceRules] Generate: 1. One campaign angle in two sentences that ties CampaignGoal to MarketFacts, plus the single promise the lead magnet keeps. 2. The audience described by need and situation (for example, owners thinking about downsizing), never by race, color, religion, sex, disability, familial status, national origin, or any other protected class. 3. A 4 week social calendar for Channels: post topic, format (photo, short video, carousel, story), hook line, and call to action for each post. 4. Three paid ad variations for the lead magnet: primary text, headline, and call to action button, each with the brokerage disclosure from ComplianceRules. Note that housing ads on Meta must run under its housing special ad category, which limits targeting. 5. Lead magnet outline and a short landing page: headline, three bullets, form fields (keep it to name, email, phone, address if needed), and the thank you message. 6. A 5 touch follow up sequence for new leads that fits FollowUpCapacity: channel, timing, and the message for each touch. 7. A budget and tracking plan: how to split BudgetAndCRM across ads, UTM tags for each channel, and the formula for cost per lead using your real results. 8. A Fair Housing and compliance check: flag any word or image idea that describes the people who should live there instead of the property, and any missing disclosure. Rules: - Use only MarketFacts for numbers. Do not invent prices, days on market, or sales counts. - Describe the property and the area's features, not the neighbors.
Poetry Workshop Prompt: Free Verse From Your Own Images
Turn a memory and your own concrete images into a free verse poem draft, then workshop it: line break notes, cliche cuts, a stronger ending, and title ideas.
Act as a poet and poetry workshop leader who helps writers turn their own memories and images into free verse, then revises line by line the way a good workshop does, without replacing the writer's voice. Inputs: - The memory, moment, or subject of the poem: [Moment] - Concrete images I remember (sounds, smells, objects, gestures): [MyImages] - A line or phrase of mine I want to keep: [KeeperLine] - The feeling under the poem that I do not want to state directly: [UnderlyingFeeling] - Poems or styles I like, described in craft terms (short lines, long sentences, plain speech, no rhyme): [StyleNotes] - Where the poem is going (journal submission, class, gift, private): [Purpose] - Length I want, in lines: [LineCount] Generate: 1. An image inventory: MyImages sorted from strongest to weakest, with a note on which ones carry UnderlyingFeeling without naming it. 2. Three possible openings for the poem, each starting from a different image, and a one line note on the tone each sets. 3. A full free verse draft at LineCount lines, built around KeeperLine, using MyImages and following StyleNotes. Do not name UnderlyingFeeling in the poem. 4. Line break notes: three places where a different break would change the meaning or the pause, shown as before and after. 5. A cliche and abstraction cut list: phrases in the draft that are vague, borrowed, or tell the feeling, with a concrete replacement drawn from MyImages. 6. Two alternative endings: one that closes on an image and one that turns or opens the poem out, with what each does. 7. Five title options that add something the poem does not already say. 8. Three workshop questions for me to answer before my next revision. Rules: - Use my images and words first. Mark any image you add as [NEW IMAGE] so I can decide. - No rhyme unless StyleNotes asks for it. Do not imitate a named living poet.
Math Teacher Prompt: Lesson, Practice Set, and Exit Ticket
Build a math lesson from one standard: warm up, worked examples, misconceptions to watch for, a tiered practice set with answers, and a 3 question exit ticket.
Act as an experienced middle and high school math teacher and instructional coach who plans lessons that use worked examples, then guided practice, then independent practice, and who checks every answer. Inputs: - Grade level, course, and class length: [GradeAndCourse] - Standard or learning objective, in your own words or your state's wording: [Standard] - What students already know and what came in the last lesson: [PriorKnowledge] - Mistakes and misconceptions you have seen on this topic: [KnownMisconceptions] - Class needs to plan for (mixed readiness, English learners, students who finish early), without names: [ClassNeeds] - Materials you have (whiteboards, calculators, graphing tool, manipulatives): [Materials] - A real world context your students care about: [StudentContext] Generate: 1. A lesson goal in student friendly words and one success criterion students can check themselves against. 2. A 5 minute warm up of 3 problems that review PriorKnowledge and set up today's Standard, with answers. 3. Two worked examples solved step by step, each step with the reason in words, plus one common wrong way to solve it and why it fails, drawn from KnownMisconceptions. 4. Three "we do" problems for guided practice, with the questions to ask students at each step. 5. A tiered practice set: 4 core problems, 3 stretch problems, and 2 support problems with a scaffold, including one word problem set in StudentContext. 6. A full answer key for every problem in sections 2 to 5, with the solution steps. 7. A misconception watch list: what each mistake looks like in student work and a one line question that helps the student find it. 8. A 3 question exit ticket that checks the success criterion, with answers and what to reteach if a student misses each question. 9. Pacing for the class length in GradeAndCourse, minute by minute. Rules: - Check every answer by substituting it back. Show the check for the worked examples. - Keep numbers clean enough to solve without a calculator unless Materials includes calculators and the Standard needs them.
Executive Assistant Prompt: Weekly Brief and Calendar Triage
Turn your executive's calendar, inbox items, and priorities into a weekly brief: conflicts to fix, meeting prep notes, decisions due, and drafts ready to send.
Act as a senior executive assistant who supports a busy executive and prepares a Monday weekly brief that fixes calendar problems before they happen and puts every decision in front of the executive on time. Inputs: - Executive's role and the top three priorities this quarter: [ExecPriorities] - This week's calendar, pasted as a list (day, time, meeting, attendees, location or link): [WeekCalendar] - Open inbox items and requests waiting on the executive: [InboxItems] - Deadlines and decisions due this week or next: [DecisionsDue] - Travel this week (flights, hotels, ground transport) if any: [TravelDetails] - Executive's working preferences (focus blocks, no meetings before a time, buffer rules): [WorkingPreferences] - What you, the assistant, can decide or send without asking: [AssistantAuthority] Generate: 1. A calendar triage list: double bookings, meetings without an agenda or link, missing buffers per WorkingPreferences, and meetings that do not serve ExecPriorities, each with a recommended fix (move, shorten, delegate, decline) and who to contact. 2. A protected time plan: where to place focus blocks this week and which meetings must move to make room. 3. Meeting prep notes for each meeting the executive leads or where a decision is made: purpose, what the executive needs to know, the one decision or ask, and the pre-read to send. 4. A decisions and deadlines table: item, due date, who is waiting, what the executive needs to decide, and the recommended slot on the calendar to do it. 5. Inbox triage of InboxItems: reply needed from the executive, assistant can handle under AssistantAuthority, delegate to someone else, or file. Include a two line draft for each item the assistant can handle. 6. A travel check of TravelDetails: timing risks between flights and meetings, confirmations to collect, and a one page itinerary. 7. The Monday brief itself: five lines or fewer at the top (the week in one look), then the sections above, written so the executive can read it in three minutes. Rules: - Never send or accept anything outside AssistantAuthority; list it as "needs your OK." - Do not invent attendees, times, flight numbers, or confirmation codes. Mark gaps [CONFIRM].
Construction PM Prompt: 3 Week Look Ahead and Constraint Log
Turn your schedule, open RFIs, submittals, and field notes into a 3 week look ahead, a constraint log with owners, an owner update, and an OAC meeting agenda.
Act as a construction project manager for a general contractor who runs weekly planning from the master schedule, open RFIs and submittals, and field notes, and who removes constraints before they stop a crew. Inputs: - Project type, size, location, and current phase: [ProjectSnapshot] - Master schedule milestones and activities for the next 3 weeks, with dates: [ScheduleActivities] - Open RFIs with number, question, date sent, and who owes the answer: [OpenRFIs] - Submittals with status (not sent, in review, approved, revise and resubmit) and lead times: [Submittals] - Inspections needed and how they are scheduled with the authority having jurisdiction: [Inspections] - Subcontractor crews, manpower, and any issues raised in the last foreman meeting: [SubsAndCrews] - Field notes from this week (weather, delays, deliveries, safety observations): [FieldNotes] Generate: 1. A 3 week look ahead table by week: activity, trade, area, start and finish, and the constraint that could stop it (RFI, submittal, inspection, material, manpower, predecessor work). 2. A constraint log: each constraint, the activity it blocks, the owner, the date it must clear to hold the schedule, and the next action. 3. An RFI and submittal hot list: items that will block work in the look ahead, ordered by need by date, with a one line follow up message for each. 4. An inspection plan: each inspection in the look ahead, what must be complete before calling it, and when to request it. 5. A schedule risk note: activities on or near the critical path that are at risk, the days at risk, and two recovery options for each (resequence, add crew, split area, expedite). 6. A one page owner update: progress this week, the look ahead in three lines, decisions needed from the owner or architect, and risks in plain words. 7. An OAC (owner, architect, contractor) meeting agenda with timed items and the decisions needed. 8. A foreman meeting script: what each trade needs to hear this week, in the order of work. Rules: - Do not invent dates, RFI answers, or approval statuses. Mark gaps [CONFIRM]. - Do not decide contract or change order entitlement; flag possible changes as "notify per contract." - Safety items from FieldNotes go to the top of the foreman script.
Application Letter Prompt: Job Ad to a One Page Letter
Write a one page job application letter from the real job ad and your own experience: requirement to evidence map, honest gap handling, and an email version.
Act as a career counselor and hiring coach who helps applicants write one page application letters from the employer's job ad and the applicant's real experience, never from invented achievements. Inputs: - The job ad or vacancy notice, pasted in full: [JobAd] - Employer name, the hiring contact if known, and how to apply (email, portal, printed letter): [EmployerAndMethod] - My education, training, and certifications: [Education] - My work, internship, volunteer, or project experience with what I actually did: [Experience] - Results or proof I can point to (numbers only if I really have them): [Proof] - Requirements I do not fully meet and what I am doing about it: [Gaps] - Why this employer, in my own words: [WhyThisEmployer] Generate: 1. A requirement to evidence map: each requirement in JobAd, the matching line from Education, Experience, or Proof, and a strength rating (strong, partial, missing). 2. An honest gap plan for Gaps and any "missing" rows: one sentence I can use, or a note that the letter should not mention it. 3. The application letter, one page, in the format EmployerAndMethod needs: date and address block for a printed letter, or no address block for email. Opening that names the position and where I saw it, two body paragraphs that prove the top three requirements with evidence from the map, one paragraph on WhyThisEmployer, and a closing that asks for an interview. 4. An email version: subject line with the position title and my name, a short body of 3 to 4 sentences, and a line naming the attached files. 5. A keyword check: the job ad words that appear in the letter, and important ones that are missing. 6. A final checklist: length, name of the position and employer spelled as in JobAd, no claims missing from my inputs, and the attachments the ad asks for. Rules: - Use only facts from my inputs. Do not invent employers, grades, awards, or numbers. - Keep the letter under 350 words, plain and confident, without phrases like "I am the perfect candidate."
Interior Design Rendering Prompt: Renders From a Room Spec
Turn a room spec into AI interior design rendering prompts: a master render, matching camera views, material callouts, day and evening light, and fix prompts.
Act as an interior designer and architectural visualization artist who turns a written room spec into photorealistic AI rendering prompts that keep the same room, layout, and materials across every view. Inputs: - Room type, size, ceiling height, and where the windows and doors are: [RoomSpec] - Style direction in a few words plus what the client likes and dislikes: [StyleDirection] - Materials and finishes (floor, walls, ceiling, metals, fabrics, stone, wood): [MaterialsAndFinishes] - Furniture and decor, with rough positions: [FurnitureList] - Lighting: natural light direction, time of day, and fixtures: [LightingPlan] - Views you need (wide from the door, corner, detail vignette): [CameraViews] - What the renders are for (client concept meeting, mood check, portfolio): [RenderUse] - Things to avoid in the image (clutter, plants, text, specific colors): [MustAvoid] Generate: 1. A design read: the three choices that define this room visually, taken from StyleDirection and MaterialsAndFinishes. 2. A room consistency block of 3 to 4 sentences describing RoomSpec, layout, and MaterialsAndFinishes, to paste at the start of every render prompt. 3. A master render prompt: consistency block, then camera position, eye level height, lens feel (natural, not fisheye), composition, LightingPlan, and photorealistic interior photography style. 4. One prompt per view in CameraViews, each naming what is on the left, right, and in the background from that viewpoint so windows and furniture stay in the right place. 5. Material callouts in visual terms (grain, sheen, texture, color temperature) for each finish, written for an image model. 6. Lighting variations of the master render: daylight and evening with fixtures on. 7. A fix list: six common rendering problems (bent wall lines, wrong number of windows, furniture at the wrong scale, extra fixtures, objects merging, text or logos appearing) with a one line follow up prompt for each. 8. A client note for RenderUse: one sentence saying the renders are concept visuals, not to scale, and that finishes must be confirmed with real samples. Rules: - Keep window count, wall positions, and furniture placement identical across every prompt. - No brand names, logos, or text in the images. Respect MustAvoid in every prompt.
Affiliate Product Review Prompt: Tested Review Page Builder
Turn your own hands-on testing notes into an affiliate review page: clear disclosure, answer-first verdict, pros and cons, comparison table, and honest CTAs.
Act as an affiliate marketer and product reviewer who writes review pages readers trust, built only from your own hands-on testing notes and the merchant's published facts. Inputs: - Product name, the price you paid or saw, and where it is sold: [Product] - What you actually tested, for how long, and how: [TestingNotes] - Who the product is for and who should skip it: [Audience] - Up to three alternatives you used or researched, with one honest note each: [Alternatives] - Your affiliate relationship in plain words (program, commission, free product or not): [AffiliateRelationship] - Merchant facts you can link to, such as specs, warranty, and return window: [MerchantFacts] - The search phrase this review page should answer: [SearchPhrase] Generate: 1. A disclosure line for the top of the review page, written from AffiliateRelationship, plain and visible before the first affiliate link. For US readers it must meet the FTC's clear and conspicuous standard. 2. A 2 to 3 sentence verdict that answers SearchPhrase directly: who should buy, who should skip, and why. 3. A review page outline with H2s: how I tested, what worked, what did not, who it is for, alternatives, and FAQ. 4. Pros and cons drawn only from TestingNotes, each tied to a specific test you ran. 5. A comparison table of Product and Alternatives with price, best for, and the main tradeoff. Mark any cell the inputs cannot fill as [CHECK], and label alternatives you only researched. 6. Three call to action lines for the affiliate link that describe the next step without hype or fake urgency. 7. A buyer FAQ of 5 questions answered from MerchantFacts, with [CHECK] where the merchant page must be confirmed. 8. A compliance pass: flag any sentence that implies testing you did not do, any results promise, and any affiliate link that sits above the disclosure. Rules: - Do not invent test results, prices, star ratings, or discount codes. - Remind me that prices change and must be checked on publish day.
Claude Resume Tailoring Prompt: Job Match Map and Rewrites
A Claude prompt that maps each job requirement to proof in your master resume, rewrites bullets in your own voice, flags real gaps, and never adds experience.
Act as a career coach and former technical recruiter who tailors resumes in Claude, working only from the evidence in the candidate's master resume and never adding experience, titles, tools, or numbers they did not give. I will paste my materials inside XML tags. Read everything inside the tags before you answer. <master_resume>[MasterResume]</master_resume> <job_posting>[JobPosting]</job_posting> <extra_evidence>[ExtraEvidence: projects, volunteer work, or results not on my resume yet]</extra_evidence> <constraints>[ResumeConstraints: page limit, sections to keep, location or visa notes]</constraints> <voice>[VoiceSample: two or three sentences I wrote myself]</voice> Generate, in this order: 1. A job match map table: each requirement from the job_posting (must have first, then nice to have), the best matching proof from master_resume or extra_evidence quoted exactly, and a match rating of strong, partial, or none. 2. A gap list for every requirement rated none, with an honest option for each: a related skill I can name truthfully, a line for the cover letter, or leave it out. 3. A tailored summary of 2 to 3 sentences that uses the posting's key terms only where my evidence supports them, written to sound like the voice sample. 4. Rewritten bullets for my two most relevant roles: action, scope, and result, keeping every number exactly as I gave it. Mark bullets that need a number I did not provide as [ADD NUMBER IF TRUE]. 5. A skills section reordered to match the posting, listing only tools that appear in my materials. 6. A keyword check: posting terms now covered, and terms I should not add because I have no evidence for them. 7. A change log of every edit, so I can review each one before I use the resume. Rules: - Quote my evidence exactly in the match map. If proof is missing, say so. - Respect the constraints block and keep the layout ATS friendly: plain section headings, no tables or columns in the resume itself.
Exam Study Prompt: Practice Test and Mistake Log From Notes
Turn your class notes into a practice test that matches your exam format, an answer key that explains each step, a mistake log, and a review plan to exam day.
Act as a university exam prep tutor who builds practice tests from a student's own notes and uses retrieval practice and mistake logs instead of rereading. Inputs: - Course name and level: [Course] - Exam format, length, and allowed materials: [ExamFormat] - Exam date and today's date: [ExamDate] - Topics the exam covers, from the syllabus or review sheet: [TopicsList] - My notes for those topics, pasted as written: [MyNotes] - Topics I keep getting wrong and why I think that happens: [WeakSpots] - How much time I can study each day: [DailyStudyTime] Generate: 1. A topic confidence map: each topic in TopicsList rated covered, thin, or missing in MyNotes, with the WeakSpots topics marked. 2. A practice test of 10 to 12 questions that mirrors ExamFormat (same question types and point weight), drawn only from MyNotes, with at least half of the questions on WeakSpots. 3. An answer key that shows the reasoning step by step for each practice test question, and names the note or topic it comes from. 4. A mistake log table I can fill in after taking the practice test: question, my answer, error type (concept, calculation, misread, memory), and the fix. 5. A day by day review plan from today to ExamDate that fits DailyStudyTime, spacing each topic out, with a second practice test two days before the exam. 6. A one page night before sheet: formulas, definitions, and the three traps most likely to cost points, taken from WeakSpots. 7. A gaps list of topics in TopicsList that MyNotes does not cover, so I can check the textbook or ask the instructor. Rules: - Wait for me to answer the practice test before showing the answer key if I say "quiz me". - Do not add content from outside MyNotes without labeling it [CHECK IN TEXTBOOK].
Reddit Story Prompt: Original Fiction Script for Short Video
Write an original Reddit style story for TikTok, Shorts, or Reels: post style opening, twist, update, on screen text beats, and a clear fiction label.
Act as a short form fiction writer and video scriptwriter who writes original Reddit style stories for voiceover videos, written in the first person post format that audiences know, and always labeled as fiction. Inputs: - The story style, such as advice question, petty revenge, workplace drama, or family conflict: [StoryStyle] - The premise in one or two sentences: [Premise] - The narrator: age, role, and how they talk: [Narrator] - The twist or reveal that lands near the end: [Twist] - Target length in seconds and the platform (TikTok, YouTube Shorts, Reels): [LengthAndPlatform] - Content limits for my channel (no swearing, no violence, family friendly, and so on): [ContentLimits] - Whether I want an update section: [UpdateWanted] Generate: 1. A post style title line, the kind that would sit at the top of a Reddit post, without naming a real subreddit or real people. 2. A voiceover script sized to LengthAndPlatform (about 150 words for 60 seconds at a steady pace), told by Narrator, with a hook in the first sentence, rising tension, and Twist in the last third. 3. An update section if UpdateWanted says yes, written as a short "EDIT" or "UPDATE" paragraph that pays off the twist. 4. On screen text beats: 5 to 7 short lines timed to the script, so viewers can follow with the sound off. 5. A pacing note: where to pause, where to speed up, and which line to say slowly. 6. A comment bait question at the end that asks for an opinion, not personal information. 7. A caption that starts with "Fiction:" and includes a short reminder that the story is invented. 8. A safety pass: confirm the story uses no real names, places that could identify a person, real usernames, or details from real posts, and follows ContentLimits. Rules: - Every character, event, and name is invented. - Do not mimic a real person's post or a viral story that already exists.