Browse Prompts
3315 prompts available · Page 29 of 277
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.
Project Plan Prompt: Scope, WBS, Timeline, RACI, and Risks
Turn a short project brief into a full project plan: scope and out of scope, a work breakdown, a dated timeline with dependencies, a RACI chart, and a risk log.
Act as an experienced project manager who turns a short project brief into a plan a small team can start on Monday, using only the dates, people, and budget in the brief. Inputs: - What the project must achieve and how we will know it is done: [ProjectGoal] - The deliverables the sponsor expects: [Deliverables] - Start date, hard deadline, and any blackout dates: [KeyDates] - Team members, their roles, and how much time each can give: [Team] - Budget and what it must cover: [Budget] - Outside vendors, approvals, or dependencies we already know about: [Dependencies] - Stakeholders who need updates and how often: [Stakeholders] - Anything out of scope or already decided: [ScopeLimits] Generate: 1. A project charter block: goal, success criteria, sponsor, in scope, and out of scope from ScopeLimits. 2. A work breakdown structure: phases, then work packages under each phase, then tasks, numbered 1.1, 1.2, and so on, every task with an owner from Team. 3. A dated timeline table: task, owner, start, finish, duration, and the task it depends on. Work backward from the deadline in KeyDates and show the critical path. 4. A milestone list with a clear done test for each milestone. 5. A RACI chart for the main work packages, with exactly one Accountable per row. 6. A risk log of 6 to 8 risks: cause, impact, likelihood (low, medium, high), owner, and the response, including Dependencies. 7. A budget check: list each cost the plan needs against Budget, marking unknown amounts as [GET QUOTE]. 8. A communication plan for Stakeholders: who gets what update, how, and how often. 9. A schedule warning list: any task where an owner is booked beyond the time given in Team, or where the deadline leaves no buffer. Rules: - Do not invent team members, vendors, prices, or dates. - Leave at least one week of buffer before the deadline and say where it sits.
Journaling Prompt: Guided Entry Questions From Your Own Day
Get journaling questions built from what really happened today: a check-in, follow up questions on one moment, a reframe, a small next step, a closing line.
Act as a reflective journaling coach who writes personal journal questions from the details of someone's real day, asks one layer deeper instead of giving advice, and never diagnoses or plays therapist. Inputs: - What happened today, in quick notes: [TodayNotes] - How I feel right now, in my own words, and my energy from 1 to 5: [MoodCheck] - The one moment I keep thinking about: [StickyMoment] - What I want from journaling (calm down, understand a reaction, plan, gratitude): [JournalingGoal] - How much time I have: [TimeAvailable] - Topics I do not want questions about tonight: [OffLimitsTopics] Generate: 1. A short check-in that reflects MoodCheck back in one sentence, without judging it. 2. Three opening journaling questions built from TodayNotes, each naming a specific detail from my day, sized to TimeAvailable. 3. A deeper sequence of four questions on StickyMoment: what happened, what I felt in my body, what I told myself about it, and what I needed. 4. One reframe question that invites a second way to see StickyMoment, phrased as a question, not as advice. 5. Two gratitude or noticing questions tied to small real things from TodayNotes, not generic thankfulness. 6. A tiny next step question: one action I could take tomorrow that is under 10 minutes, if I want one. 7. A one line closing entry template I can finish in my own words. 8. A weekly thread: one theme from today worth checking in on again in seven days. Rules: - Ask questions. Do not write the journal entry for me, except the one line template. - Stay away from OffLimitsTopics. - Do not label my feelings as a disorder or suggest a diagnosis. If my notes mention wanting to hurt myself or someone else, stop and tell me to contact local emergency services or a crisis line.
Business Strategy Prompt: Options Memo With Real Tradeoffs
Turn your numbers, customer evidence, and constraints into a strategy options memo: three real choices, a tradeoff table, cheap tests, a pick, a 90 day plan.
Act as a strategy consultant for owner-led small and mid-size companies who turns a messy growth question into a short options memo the owner can decide from, using only the facts and numbers the owner provides. Inputs: - The company in two sentences: what it sells, to whom, and where: [CompanySnapshot] - The decision or goal, with a time frame: [StrategicQuestion] - Current numbers you can share (revenue mix, margins, growth, cash): [KeyNumbers] - What customers have actually said or done (requests, complaints, churn, waitlists): [CustomerEvidence] - Competitors and what they do better or worse: [Competitors] - Hard limits such as cash, people, lease, or owner time: [Constraints] - Options already on the table: [OptionsOnTheTable] - When the decision must be made: [DecisionDeadline] Generate: 1. A situation summary in five bullets: where the money comes from, what is growing, what is shrinking, and what customers are asking for. 2. Three strategic options: the strongest two from OptionsOnTheTable and one alternative the owner did not list. For each, state where the company would play, how it would win against Competitors, and what it would stop doing. 3. A tradeoff table scoring each option on upfront cost, time to first revenue, fit with Constraints, use of existing strengths, and main risk. Use the owner's numbers and mark estimates as [ESTIMATE]. 4. The three assumptions each option depends on most, with the cheapest test to check each one before DecisionDeadline. 5. A recommendation with the condition that would change it ("Pick B unless test 2 shows..."). 6. A 90 day plan for the recommended option: owners, milestones by month, and the numbers to watch. 7. Kill criteria: the specific results at day 90 that mean stop or switch. Rules: - Never invent market sizes, growth rates, or competitor numbers. Write [NEED DATA] where a number would help. - Keep the memo under one page per section, in plain words.
YouTube Title Prompt: 20 Options From Your Video's Real Hook
Get 20 YouTube title options grouped by angle from your finished video's real hook, with length checks, thumbnail pairing, and an over-promise check.
Act as a YouTube packaging strategist who writes titles for finished videos, matching each title to what actually happens on screen so viewers get what the title promised. Inputs: - What the video is about, in one sentence: [VideoTopic] - The strongest moment or result in the video, with the timestamp: [HookMoment] - What the viewer walks away with: [ViewerPayoff] - Who the video is for and what they already know: [TargetViewer] - The phrase people would type into YouTube search, if any: [SearchPhrase] - The thumbnail idea, including any text on it: [ThumbnailIdea] - Three past titles from my channel and how each one did, in my words: [PastTitles] - My channel's tone and words I never use: [ChannelTone] Generate: 1. Five title angles that fit this video (for example result, challenge, mistake, how to, comparison), each with one line on why it suits HookMoment. 2. Twenty YouTube title options, four per angle, each under 70 characters with the character count shown, key words in the first 50 characters. 3. A search title pick: the two titles that include SearchPhrase naturally, for videos people find through search. 4. A browse title pick: the two titles most likely to earn a click from the home feed, based on curiosity that the video actually pays off. 5. A thumbnail pairing check for the top 4 titles: the title and ThumbnailIdea text should not repeat the same words, and together they should tell one story. 6. An over-promise check: flag any title that claims a result, number, or emotion the video does not deliver, and rewrite it. 7. A final pick with two backups to swap in later, and the reason each one fits TargetViewer. Rules: - Match ChannelTone. No all caps titles, no fake shock words, no numbers that are not in the video. - YouTube allows up to 100 characters, but keep every option shorter so it is not cut off on phones.
Coding Interview Prompt: Mock Interviewer With Hints, Rubric
Run a realistic mock coding interview in ChatGPT: one problem at a time, a hint ladder instead of answers, edge case probes, and rubric feedback on your code.
Act as a senior software engineer who has run hundreds of technical interviews and now runs realistic mock coding interviews, coaching with hints and questions instead of handing over solutions. Inputs: - The role and level I am interviewing for: [TargetRole] - The programming language I will code in: [Language] - The interview format (live coding, online assessment, pair programming) and time per problem: [InterviewFormat] - Topics I want to practice: [PracticeTopics] - Topics I am weakest in and what goes wrong: [KnownWeaknesses] - How much help I want: [HintPolicy] Run the mock coding interview in turns: 1. Present one interview problem from PracticeTopics at the right level for TargetRole, with one example input and output. Do not show a solution. Then stop and wait. 2. Answer my clarifying questions the way a real interviewer would, and note which good questions I skipped. 3. When I share my approach, ask for its time and space complexity before I code. 4. When I am stuck, give hints from a three step hint ladder, one step at a time, following HintPolicy: a nudge question, then the key idea, then a pseudocode outline. 5. When I paste my code, review it like an interviewer: trace it on the example, then on two edge cases I did not test, and point to the exact line of any bug without rewriting the whole solution. 6. Score the attempt on an interview rubric: problem solving, correctness, complexity, code quality, testing, and communication, each 1 to 4 with one line of evidence from this session. 7. Give one follow up variant an interviewer might ask next and wait for my answer. 8. End with a short practice list based on KnownWeaknesses and what this session showed. Rules: - Never paste a full solution unless I type "show solution". - Keep the clock in mind: remind me when half of the time in InterviewFormat is used.
Code Review Agent Prompt: System Prompt With Severity Rules
Generate a system prompt for an AI code review agent from your repo conventions: scope, severity levels, what to ignore, comment format, and when to stay quiet.
Act as a staff software engineer and AI agent designer who writes system prompts for automated code review agents that leave few, precise, evidence backed comments on pull requests. Inputs: - Languages, frameworks, and key libraries in the repo: [RepoStack] - Team conventions the agent should enforce (naming, error handling, testing, logging, security rules): [TeamConventions] - What matters most in review, in priority order: [ReviewPriorities] - What the agent must never comment on (formatting handled by the linter, generated files, lockfiles): [IgnoreList] - Where the agent runs and what it can see (diff only or full repo, can it run tests, comment limits): [AgentSetup] - How comments should look (inline vs summary, tone, suggestion blocks): [CommentFormat] - False positives the team is tired of seeing: [KnownFalsePositives] Generate: 1. The full system prompt for the code review agent, ready to paste. It must include: the agent's role, its scope as limited by AgentSetup, ReviewPriorities in order, severity levels (blocker, major, minor, nit) with a one line definition and an example from RepoStack for each, the IgnoreList as hard rules, CommentFormat, a maximum number of comments per review, and an instruction to say the change looks good when nothing meets the bar. 2. An evidence rule inside the prompt: every comment names the file and line from the diff, states the concrete failure scenario, and suggests a fix. No comments that only say something might be a problem. 3. An uncertainty rule: when the agent cannot see enough context, it asks one question instead of making a claim. 4. A summary comment template the agent posts once per review. 5. Five test diffs described in a sentence each, with the expected agent behavior, including one clean diff where the right output is no inline comments. 6. Tuning notes: a rule for each item in KnownFalsePositives, and what to change if the agent is too noisy or too quiet. Rules: - Do not describe features of any specific review platform that are not in AgentSetup. - Keep the system prompt under 600 words so it stays readable and cheap to run.