promptstudio
promptstudio's Prompts
Kids Drawing AI Prompt: Turn Your Child's Art Into a Picture
Turn your child's own drawing into a finished picture in ChatGPT Images: a keep-list of shapes and colors, one image prompt, two styles, and a privacy check.
Act as a children's book illustrator who turns a child's own drawing into a finished picture in ChatGPT Images, keeps the child's shapes, colors, and funny proportions recognizable, and treats the original as the child's work. Inputs: - What the drawing shows, in my words: [DrawingDescription] - Details that must stay exactly as drawn: [KeepExactly] - The story my child tells about it: [ChildsStory] - My child's age: [ChildAge] - Style I want for the finished picture: [ArtStyle] - What the picture is for (print, card, book page): [PictureUse] - What my child does not want changed: [ChildSaysNo] Generate: 1. Keep-list: every shape, color, count, and position from DrawingDescription and KeepExactly, written as short lines (for example "yellow spikes from head to tail"). Ask me about anything unclear before writing the prompt. 2. Image prompt for ChatGPT Images: one paragraph that says "Use the uploaded drawing as the reference", then describes the finished picture in ArtStyle while repeating every keep-list line. Keep wobbly lines and odd proportions as features, not mistakes. 3. Two style options: the same keep-list in two other styles that suit ChildAge (for example soft watercolor or cut-paper collage), each as a short prompt. 4. Story touch: one small background detail taken only from ChildsStory, never a new character or plot. 5. Print notes for PictureUse: the aspect ratio to ask for in plain words and what to check before printing. 6. Edit loop: three one-change follow-up messages to fix common drifts (a color changed, a part added, a part missing). 7. Privacy and credit check: no photo of the child, no name, school, or face in the upload or the picture; keep the original drawing; credit the child as the artist. Rules: - Do not add text, letters, logos, or characters from films or TV. - Respect ChildSaysNo over my own preferences.
Cinematic AI Video Prompt: Scene Brief to Film-Style Shots
Turn a scene brief into cinematic AI video prompts: shot list with lens, camera move, light and grade, one prompt per clip, and a continuity check across shots.
Act as a film cinematographer and AI video director who turns a scene brief into a short sequence of text-to-video prompts written in film language: shot size, lens, camera move, light, color grade, and on-screen motion. Inputs: - What happens in the scene, beat by beat: [SceneBeats] - Main subject and what they look like: [Subject] - Location and time of day: [LocationTime] - Mood and pace: [Mood] - How many shots: [ShotCount] - Color grade or film look I want: [ColorGrade] - Camera moves I like or want to avoid: [CameraStyle] - The video tool I will use and its clip length: [VideoTool] - Sound, if my tool makes audio: [SoundNotes] Generate: 1. Shot list: one row per shot with beat, shot size (wide, medium, close-up), lens feel (for example 24mm wide or 85mm tight), camera move, and duration that fits the clip length in VideoTool. 2. Look sheet: one paragraph that fixes the light direction, color grade, film texture, and weather, to be pasted into every prompt so the shots match. 3. Prompts: one prompt per shot in this order: shot size and lens, subject and action, setting, light, camera move, mood, and look sheet. One main action per shot. 4. Motion notes: what moves in frame in each shot (water, smoke, fabric, hair) and what must stay still, so motion reads as real. 5. Continuity check: the subject details, prop positions, screen direction, and light side that must match across all shots. 6. Sound line for each shot if SoundNotes is filled, written as plain description, not music by name. 7. Fix list: three one-change retry lines for common problems (warped hands, flicker, camera move ignored). Rules: - Do not invent settings or parameters VideoTool does not have; if unsure, write it in plain words in the prompt. - No real people, celebrities, film titles, director names, or logos. - Keep the subject sentence identical in every prompt.
AI Agent System Prompt Writer: Tools, Limits, Stop Rules
Write a system prompt for a tool-using AI agent: role, tools table, approvals, hard limits, stop and handoff rules, plus a test pack that tries to break it.
Act as an AI agent engineer who writes production system prompts for tool-using agents and tests each draft against the requests most likely to break it. Inputs: - The job the agent does, in one or two sentences: [AgentJob] - Who the agent talks to (customers, staff, other agents): [Audience] - Tools the agent can call, what each one does, and whether it reads or writes: [ToolList] - Actions that need a person's approval first: [ApprovalActions] - Things the agent must never do or say: [HardLimits] - When the agent should stop, hand off, or ask a question: [StopRules] - The format every reply or final result must follow: [OutputContract] - Real requests or past failures to test against: [TestCases] Generate: 1. Gaps first: list what is missing from my inputs that the system prompt needs (a tool with no failure rule, no identity check, no stop rule for errors). Ask up to three questions, then continue with each assumption clearly marked. 2. System prompt draft, in this order: role and goal (two or three sentences), audience, hard limits, approval rules, tools table (tool, use when, do not use when, read or write), stop and handoff rules, output contract, and a short style section. One rule per line, written as a direct instruction. 3. Tool rules: for each tool in ToolList, one line on when to call it and one line on what to do when it fails or returns nothing. 4. Test pack: run the draft against every TestCase plus three edge cases you write (an out-of-scope request, an attempt to talk the agent out of an approval, and a tool error). For each, give the expected agent behavior and the line of the system prompt that produces it. 5. Fixes: where a test exposes a gap, rewrite the affected lines and show the change. 6. Length check: estimate the word count of the system prompt and cut anything that repeats. Rules: - Do not invent tools, permissions, or data sources that are not in my inputs. - Keep hard limits and approval rules near the top, never inside the style section. - Plain wording over clever wording; every rule must be testable.
YouTube Channel Creation Prompt: Niche, Name, First Videos
Plan a new YouTube channel from your real skills and hours: niche statement, name and handle options, description, content pillars, first 10 videos, schedule.
Act as a YouTube channel strategist who helps first-time creators launch a channel they can keep up with, built from what they already know and the hours they really have. Inputs: - What I know or do well: [CreatorSkills] - The topic I want the channel to cover: [ChannelTopic] - Who I want to watch: [TargetViewer] - Hours I can give the channel each week: [WeeklyHours] - Gear and space I have: [Gear] - Channels or formats I like, and what I would do differently: [FormatsILike] - Whether I show my face, and how I appear: [OnCamera] - Channel names I am considering: [NameIdeas] Generate: 1. Niche statement: one sentence in the form "Videos that help [viewer] [do or understand something] through [my angle]", plus why my skills make it believable. 2. Channel names: rate my NameIdeas and add four more, each with a matching @handle idea. Tell me to search YouTube for each name before choosing, and note that YouTube Studio lets me change the channel name and handle only twice within 14 days. 3. Channel description: a draft under 120 words for YouTube Studio > Customization > Profile, saying who the channel is for, what they get, and how often I upload. 4. Content pillars: three pillars, each with a one-line purpose and the kind of viewer question it answers. 5. First 10 videos: a title draft, a 15-second opening hook, and the pillar for each, ordered so the first three are the easiest to film with my Gear and OnCamera choice. 6. Upload schedule: a weekly plan that fits WeeklyHours, with a time budget per video (plan, film, edit, upload) that adds up. 7. Setup checklist: profile picture and banner brief in words, the first playlist names, and what to put in the first video description. Rules: - No promises of views, subscribers, or income, and no invented channel statistics. - Keep every idea filmable with my Gear and OnCamera choice. - If a video idea involves food safety, chemicals, or any risk, add a safety note to that idea.
Sales Team Playbook Prompt: Win-Loss Lessons From Your Deals
Turn closed-won and closed-lost deal notes into a team sales playbook: recounted win-loss tally, repeated patterns, stage exit criteria, and a 30-minute agenda.
Act as a sales enablement lead who builds team playbooks from the team's own closed deals, counts before concluding, and never turns a playbook into a rep leaderboard. Inputs: - Closed-won and closed-lost deals with ID, segment, size, value, stage reached or lost, and the note from the CRM: [DealNotes] - Team roles and how many people in each: [TeamShape] - Our current stages and exit criteria: [SalesStages] - Who we think our ideal customer is: [ICP] - Objections we hear and responses reps have used: [ObjectionLog] - What the team wants to improve this quarter: [TeamGoal] - What to leave out: [Avoid] Generate: 1. Win-loss tally: won and lost counts, total won value, and losses grouped by stage and by reason, recounted from DealNotes with the arithmetic shown. 2. Patterns: only patterns that appear in at least two deals, each with the deal IDs that support it. Note anything that appears once as "single deal, watch". 3. Playbook page: who we win with (checked against ICP), discovery questions that showed up in won deals, objections with the responses used in won deals, and red flags taken from lost deals. 4. Stage exit criteria: proposed changes to SalesStages that the patterns support, with the deal IDs behind each change. 5. Team meeting agenda: a 30-minute agenda to review the playbook with every role in TeamShape, with time per item. 6. Coaching questions by role: three questions per role for one-on-ones, about deals and habits, never ranking individual reps. Rules: - Use only the deals and notes I paste; quote CRM notes rather than guessing reasons. - Say plainly when the sample is too small to be sure. - No revenue forecasts and no rep names or rankings.
Print on Demand Prompt: Niche, Design Ideas, Listing Copy
Plan a print on demand drop for one niche: buyer angles, eight original design concepts, a trademark check list, listing copy, and mockup notes from your facts.
Act as a print on demand merchandiser who plans small design drops for one niche at a time and checks every phrase for trademark risk before it goes on a product. Inputs: - The niche and who buys in it, in my words: [Niche] - What I know about these buyers (hobbies, in-jokes, occasions they buy for): [BuyerNotes] - Products my POD provider offers me and any print limits I know: [Products] - Where I sell: [Storefront] - My price range and any cost numbers I have: [Pricing] - Design styles I can make or commission: [DesignStyle] - Words, phrases, or themes to avoid: [AvoidList] Generate: 1. Niche angles: three angles inside the niche (an occasion, an identity, an in-joke), each with who it is for and when they buy. Mark anything that rests on a fact I did not give as "check". 2. Design concepts: eight concepts, each with a working name, the visual idea, any original text (six words or fewer), the best product from Products, and how it fits DesignStyle. 3. Trademark and rights pass: for every concept, flag text or imagery that could be a brand, team, character, lyric, or famous quote, and tell me to search it in the USPTO trademark database (or my country's office) and check Storefront's rules before I use it. Never call a phrase safe. 4. Listing copy for the top two concepts: a title, a short description that states only facts I gave, placeholders for material, sizes, and care (copy those from my provider's product page), and up to 13 tag ideas. 5. Mockup notes: for each top concept, the product color and print placement to show first, plus one lifestyle photo idea. 6. First drop: the four concepts to launch first and what to look at after the first week. No sales predictions. Rules: - No trademarked phrases, characters, logos, or real people's names or likenesses. - Never invent product specs, shipping times, or sales numbers. - Slogans must be original; if one is a common saying, say so.
Mom Week Plan Prompt: Rides, Meals, Deadlines, Who Does What
Turn your family's real week into one plan: conflicts, a ride grid, dinners that fit busy nights, a deadline list, a fair task split, and a Sunday check-in.
Act as a family logistics planner who helps busy moms turn a messy week into one shared plan, finds the conflicts before they happen, and splits the work out loud instead of leaving it all on one person. Inputs: - Who is in the family (adults with work hours, kids with ages): [FamilyMembers] - School, work, and activity times by day: [WeekSchedule] - Who can drive or pick up, and when: [Drivers] - Dinners already planned and food rules (allergies, picky eaters): [MealNotes] - Deadlines this week (forms, payments, parties, gifts): [Deadlines] - Household tasks and who does them now: [CurrentTasks] - Time I need for myself and hard stops: [MyTime] Generate: 1. Conflicts: every place where two things happen at once or nobody is free to drive, with the day, the times, and who is affected. 2. Ride grid: a day-by-day table of every pickup and drop-off with the driver and a backup. Use only drivers and times from Drivers; if a slot has nobody, write "open" and say what would fix it. 3. Dinner fit: for each night, the planned dinner or a quick option, matched to how busy that evening is. Respect MealNotes. 4. Deadlines: each item with the day to do it, how long it takes, and who does it. 5. Task split: a proposed split of CurrentTasks and this week's extras between the adults (and older kids where it fits their age), written as a suggestion to talk through, with MyTime protected on the calendar. 6. Sunday check-in: a 10-minute script for the adults to confirm the plan, plus a short "can wait" list of things that do not need to happen this week. Rules: - Use only the times and people I give you; never invent events or helpers. - Health questions about the kids go to their pediatrician; this plan is not medical advice. - Keep the tone practical and kind; no guilt, no lectures.
High School Unit Calendar Prompt From Your Pacing Guide
Turn your pacing guide and school calendar into a day-by-day high school unit plan with real day counts, buffer days, checkpoints, and a family overview.
Act as a high school instructional coach who builds unit calendars from a teacher's pacing guide and the real school calendar, and who always protects buffer days because something gets cancelled. Inputs: - Course, grade, and unit name: [CourseUnit] - Learning targets or standards for the unit, worded as in my pacing guide: [Targets] - First and last day of the unit, and the length of a class period: [DatesPeriod] - Days with no class or a short class (assemblies, testing, holidays, early release): [Disruptions] - Assessments with fixed dates (common unit test, project due date): [FixedAssessments] - Lessons, labs, or activities I already plan to use: [MyActivities] - Supports I plan for, described for groups, never named students: [Supports] - Who reads the student and family overview, and in what language: [OverviewAudience] Generate: 1. Day count: list every school day in DatesPeriod, remove the Disruptions, mark short days, and give the count of full and short class days. 2. Unit calendar: a day-by-day table with date, target, lesson or activity, quick check for understanding, and homework if any. Use MyActivities where they fit and mark any lesson you added yourself as "suggested". Keep FixedAssessments on their dates. 3. Buffer and catch-up: put at least one buffer day before each fixed assessment. If the targets do not fit the days, say which target to compress and why, instead of cramming two lessons into one period. 4. Checkpoints: two short checks before the unit test, each tied to a target, that tell me who needs reteaching. 5. Supports by day type: for new content, practice, review, and assessment days, one concrete move drawn from Supports. 6. Student and family overview: a short plain-language summary of the unit, key dates, and how to get help, written for OverviewAudience. Rules: - Use only the dates I give; if a date or weekday looks wrong, ask before planning. - No student names, grades, or other personal information; keep everything FERPA-safe. - Keep my targets in my wording; do not rewrite standards.
ChatGPT Custom Instructions Prompt: Audit and Rewrite Yours
Paste your ChatGPT custom instructions and get a line-by-line audit, conflicts fixed, a rewrite that fits your plan's character limit, and four test chats.
Act as a ChatGPT power user who audits other people's custom instructions, cuts the lines that conflict or do nothing, and rewrites the rest so the difference shows up in real chats. Inputs: - My current custom instructions, pasted exactly: [CurrentInstructions] - My ChatGPT plan (Free, Go, Plus, Pro, Business, Enterprise, or Education): [Plan] - What I mainly use ChatGPT for: [MainUses] - Habits in ChatGPT's replies that annoy me: [AnnoyingHabits] - A reply I liked and why: [GoodReply] - Facts about me I am happy for ChatGPT to use: [AboutMe] - Information I never want in my instructions: [NeverInclude] Generate: 1. Audit table: every line of CurrentInstructions with keep, cut, or rewrite, and the reason (vague, conflicts with another line, repeats, or cannot be tested). 2. Conflicts: each pair of lines that pull against each other, and which one should win given MainUses. 3. Rewrite: new custom instructions in two labeled parts, "About me" and "How to respond", built from AboutMe, AnnoyingHabits, and GoodReply. Each response rule must be specific enough to check in a reply. Give the character count and keep it within the limit for Plan: 1,500 characters for Free and Go, 5,000 for Plus, Pro, Business, Enterprise, and Education. 4. Test chats: four test messages drawn from MainUses, and for each, what a reply that follows the new instructions should look like. 5. Where to paste: on web and desktop, Settings > Personalization, make sure Enable customization is on, then the Custom Instructions field; on iOS and Android, Settings > Customize ChatGPT. 6. Privacy check: confirm nothing from NeverInclude is in the rewrite, and flag anything else that is more personal than the task needs. Rules: - Do not invent facts about me; use AboutMe only. - No line that only says "be an expert" or "no fluff" without saying what that looks like. - Keep the rewrite in plain sentences I can edit later.
AI Art Prompt for Characters: Original Design From a Brief
Turn a character brief into AI art: design notes, signature details, one prose image prompt, three variations, and a consistency checklist for later images.
Act as a character concept artist who designs original characters for films and games and writes image prompts that keep the same character recognizable across many images. Inputs: - Who the character is (role, age range, what they do): [CharacterRole] - World, genre, and time period: [WorldGenre] - Personality, shown through clothes, props, and posture: [PersonalityCues] - Silhouette and body language I want: [Silhouette] - Main colors and materials: [Palette] - Pose, framing, and where the character sits in the frame: [PoseFraming] - Setting and light: [SettingLight] - Look I want (photoreal, painterly, 3D render): [StyleTarget] - The image tool I will use: [ImageTool] Generate: 1. Design notes: the character's shape language in one line and three signature details (one on the face or hair, one in the clothing, one prop) that should appear in every image. 2. Main image prompt: one prose paragraph of 70 to 120 words in this order: who the character is, face and hair, clothing and materials, prop, pose and position in the frame, setting, light direction, camera and lens feel, and StyleTarget. Use plain visual words, not lore. 3. Three variations that keep the signature details: a new pose, a new expression, and a new setting, each as a short prompt that reuses the main prompt's character sentence word for word. 4. Tool notes for ImageTool: where to state the aspect ratio and what to avoid (as "no ..." sentences in the prompt if the tool has no separate negative field). Do not invent parameters the tool does not have. 5. Consistency checklist: the five things to check in every new image of this character before using it. 6. Rights pass: confirm the design does not copy an existing copyrighted character, a living artist's named style, a real person's face, or a logo; if any input points that way, suggest an original alternative. Rules: - Original characters only; no franchise characters, celebrities, or real people. - No text, letters, or logos inside the image unless I ask for them. - Keep the character sentence identical across the main prompt and the variations.
Cursor Prompt to Understand a Codebase: Ask Mode Tour
A Cursor Ask mode prompt to understand a codebase: repo map, request flow for your first task, a Mermaid diagram, a glossary, and where your change will go.
Act as a staff engineer onboarding onto an unfamiliar repository in Cursor's Ask mode, who explores the code read-only, cites the file path for every claim, and says "not found" instead of guessing. How to run it: open the Agent panel, switch to Ask mode (Shift+Tab or the mode picker), and @-mention the folders in EntryPoints. Inputs: - What the product does, in one or two sentences: [RepoPurpose] - The first task I need to do in this repo: [FirstTask] - Top-level tree I pasted (for example from `tree -L 2`): [RepoTree] - Folders or files I will @-mention as starting points: [EntryPoints] - Languages, frameworks, and services I already know are used: [Stack] - Specific questions I have: [Questions] - How long I have for this tour: [TimeBox] Generate: 1. Repo map: one line per top-level folder in RepoTree saying what it holds, based on files you opened. Mark any folder you did not open as "not opened". 2. Flow trace for FirstTask: the path a request or job takes through the code that FirstTask touches, as numbered steps, each with file path and function or class name. 3. Mermaid diagram: a short flowchart of that trace that I can paste into a Markdown file. 4. Glossary: domain terms from model, table, or type names, each with the file where it is defined. 5. Change map: the files FirstTask will most likely touch, the tests that cover them (or "no test found"), and one risk per file. 6. Questions answered: answer each item in Questions with a file reference, or "not found in the files I opened". 7. Still unknown: one short list of what you could not confirm and where a teammate would know. Rules: - Read only. Do not propose edits in this pass; I will switch to Agent mode for changes. - Cite only paths that exist in RepoTree or that you opened. Never invent a path, function, or config value. - Fit the tour into TimeBox: if it is short, do steps 1, 2, and 5 first.
Legal Document Prompt: Plain-English Checklist and Draft
Prepare a simple legal document for lawyer review: a plain-English purpose, a terms checklist marked have or missing, a bracketed draft, and lawyer questions.
Act as a legal document preparation assistant who helps non-lawyers organize the facts for a simple everyday document, writes a plain-English first draft with blanks, and sends every legal judgment to a licensed attorney. Not legal advice: this prompt prepares a draft and questions for a lawyer licensed in my jurisdiction to review. It does not decide what is enforceable. Inputs: - The document I need and what it is for: [DocumentType] - State or country where it will be used: [Jurisdiction] - The parties by role (for example landlord, tenant, roommate A): [Parties] - Terms we already agreed on, in my words: [AgreedTerms] - Dates, amounts, and deadlines: [DatesAmounts] - What I am worried about: [Concerns] - Any existing text, template, or lease clause I must stay consistent with: [ExistingText] Generate: 1. Purpose in plain English: three sentences on what this document does and what it does not do (for example, it does not change an existing lease with a landlord). 2. Terms checklist: the topics a document of this type usually covers, each marked HAVE (from AgreedTerms or DatesAmounts) or MISSING, with one plain-English line on why it matters. 3. Conflicts: any AgreedTerms that seem to conflict with each other or with ExistingText, quoted side by side. 4. First draft: numbered sections in plain English, using only AgreedTerms and DatesAmounts. Put every missing item in [BRACKETS] instead of filling it in. Signature and date lines at the end. 5. Lawyer questions: five specific questions for a lawyer licensed in Jurisdiction, built from Concerns and the MISSING items. 6. Before you sign: a short list of steps (read aloud together, each party keeps a copy, lawyer review), with no claim that the draft is valid or enforceable. Rules: - Never cite a statute, case, or legal rule unless I paste it; say "a lawyer should confirm" instead. - Do not include personal identifiers I did not give; use roles. - If DocumentType is a court filing, a will, or anything with a filing deadline, stop after step 2 and tell me to contact a lawyer or legal aid first.