Browse Prompts
3315 prompts available · Page 20 of 277
ChatGPT Image Prompt Builder: Subject, Style, Light, Ratio
Describe a subject, style, lighting, and aspect ratio to get a clear ChatGPT Images prompt, two one-change variations, and precise edit follow-ups.
Act as an art director who writes prompts for ChatGPT Images: plain-language scene descriptions of three to five sentences, explicit constraints, a stated aspect ratio, and edit follow-ups that change one thing at a time. Inputs: - Main subject and what it is doing: [Subject] - Where the image will be used (wallpaper, blog header, card, poster): [UseCase] - Visual style or medium (photo, watercolor, 3D render, flat illustration): [Style] - Lighting and time of day: [Lighting] - Setting and 2 to 4 specific details that must appear (colors, counts, positions): [MustShow] - Aspect ratio: [AspectRatio] - Exact words to render in the image, in quotes, or "none": [ImageText] - Things to keep out (logos, extra people, text, specific colors): [KeepOut] Generate: 1. One-sentence creative read: what the image should make a viewer feel, tied to UseCase. 2. Main prompt in 3 to 5 sentences: subject and action, setting with every MustShow detail (counts and left or right positions stated), Style, Lighting, and camera or composition notes. 3. Constraint line: ImageText exactly as quoted (or "no text in the image"), every KeepOut item, and AspectRatio. 4. Two variations that each change exactly one element (for example only the lighting, or only the camera angle) and repeat everything else. 5. Three edit follow-ups in the form "Change only X. Keep everything else exactly the same." 6. Check list: the MustShow details to verify in the result before using it. Rules: - Use plain sentences, not keyword lists or weights. - Do not ask for real people's likenesses, celebrities, trademarks, or living artists' names. - If MustShow has more than 4 details, keep the 4 most important and list the rest as optional edits.
AI Video Prompts for YouTube Shorts from Topic and Hook
Give a topic, hook, Short length, and your video tool's clip length to get a beat map, vertical clip prompts, a continuity sheet, voiceover, and AI checks.
Act as a short-form video director who turns one idea into vertical text-to-video prompts for a YouTube Short, splitting the Short into clips your AI video tool can generate, and keeping the subject consistent from clip to clip. Inputs: - Topic of the Short: [Topic] - Opening hook line (what viewers see or hear in the first seconds): [Hook] - Target Short length in seconds (YouTube Shorts can be up to 3 minutes): [ShortLength] - Longest clip your video tool generates per prompt, in seconds: [ClipLength] - Video tool you will use (any text-to-video tool that accepts a written prompt): [VideoTool] - Main subject and setting (no real people, no brands): [SubjectAndSetting] - Visual style (handheld phone look, macro food film, cinematic, stop-motion): [VisualStyle] - Voiceover or music plan: [AudioPlan] Generate: 1. Beat map: number of clips = ShortLength divided by ClipLength (rounded up), with each clip's start and end second and its job (hook, build, payoff, loop back). 2. Clip prompts for VideoTool: one per clip in 3 to 4 sentences with subject, action, camera move, lighting, and "vertical 9:16" stated every time. 3. Continuity sheet: one fixed description of SubjectAndSetting repeated word for word in every clip prompt. 4. On-screen text plan: captions to add in the editor afterwards (not inside the AI clip), with the second they appear. 5. Voiceover script timed to the beat map, or music cues if AudioPlan has no voice. 6. Publish checks: no real people, logos, or copyrighted characters; mark the Short in YouTube Studio's AI disclosure setting if the footage looks realistic; trim to ShortLength. Rules: - Never ask the video tool for readable text; add text in the editor. - Do not claim a specific tool supports a length or feature; use ClipLength as given. - Keep the hook clip visually clear within its first second.
Sales Email Sequence from Your Offer and ICP Notes
Paste your offer, ICP notes, proof points, and CTA to get a 5-email sequence, subjects, and follow-ups with no invented ROI or fake customer quotes.
Act as a B2B sales copy chief who writes email sequences only from the seller's offer facts and ICP notes, and who never invents ROI percentages, customer logos, or quotes. Inputs: - Product or service and who it is for: [Offer] - Ideal customer profile notes (role, company size, triggers): [ICP] - Proof points you can actually document: [Proof] - Primary call to action and booking link or next step: [CTA] - Tone and length limits: [Tone] - Compliance or claims bans (no medical, no guaranteed results, etc.): [Bans] - Personalization fields you will merge (first name, company, trigger): [MergeFields] - Competitor or status-quo notes you are allowed to mention: [StatusQuo] Generate: 1. Five-email sequence outline with purpose per touch. 2. Full drafts for emails 1 to 5 within Tone limits, using MergeFields placeholders. 3. Three subject lines per email, no clickbait lies. 4. One-line personalization variants tied to ICP triggers. 5. Objection bump email you can send after silence. 6. Honesty pass: list any metric, logo, or quote not in Proof and remove it. Rules: - Do not invent case-study numbers or named customers. - Keep claims inside Proof and Offer. - Output is a draft sequence for the seller to edit and comply with email laws in their region.
Graphic Design Deliverable Pack from Your Client Brief
Paste client goals, sizes, brand colors, and approved copy to get layouts, type hierarchy, asset lists, and revision questions without invented logos.
Act as a senior graphic designer who turns a client brief into a deliverable pack, and who never invents logos, trademarked marks, stock photo licenses, or performance metrics the brief did not include. Inputs: - Client and project type (poster, social set, one-pager, packaging face, etc.): [ProjectType] - Goal of the piece in the client's words: [Goal] - Final sizes and formats required: [Sizes] - Brand colors, fonts, and existing assets the client provided: [BrandAssets] - Required copy and legal lines exactly as approved: [Copy] - Audience and where it will appear: [Audience] - Constraints (print bleed, accessibility, multilingual, deadline): [Constraints] - What is explicitly out of scope: [OutOfScope] Generate: 1. Deliverable list mapped to Sizes with file naming suggestions. 2. Layout wireframe in words: zones for logo, headline, body, CTA, and required legal lines. 3. Type hierarchy: font roles using only BrandAssets fonts or system fallbacks you label as fallbacks. 4. Color usage notes from BrandAssets only; flag missing contrast checks. 5. Asset request list: photos, icons, or logos still needed from the client. 6. Revision question list: 8 clarifying questions before you start pixels. 7. Honesty pass: remove any claim of conversion lift, award, or license not in Inputs. Rules: - Never invent a logo mark or claim you own stock licenses. - Keep Copy wording exact unless the client asked for edits. - Output is a design plan for the designer, not print-shop legal advice.
Contract Review Red-Flag Memo from Your Pasted Clauses
Paste clause text, your role, and deal facts to get a plain-English red-flag memo, question list, and counsel handoff notes. Not legal advice.
Act as a contracts analyst who drafts plain-English red-flag memos from pasted clause text for the reader's own follow-up with counsel, and who never invents statutes, case law, or advice tailored as a lawyer. Inputs: - Your role in the deal (buyer, seller, freelancer, vendor, etc.): [Role] - Agreement type and parties as named in the document: [Agreement] - Deal facts you already know (price, term, deliverables): [DealFacts] - Paste of the clauses to review (or key excerpts): [Clauses] - Issues you care about most (payment, IP, termination, liability, etc.): [Priorities] - Jurisdiction or governing law line if present in the text: [GoverningLaw] - Questions you already plan to ask counsel: [CounselQuestions] - What you want the memo for (internal note, email to counterparty, meeting agenda): [MemoUse] Generate: 1. Executive snapshot: 5 bullets of what the pasted clauses appear to say, labeled as reading notes not conclusions of law. 2. Red-flag table: clause snippet, why it may matter for Role, and a clarifying question. 3. Missing-clause checklist against Priorities (payment timing, IP ownership, termination, liability caps, etc.). 4. Negotiation question list for the counterparty (non-legal, business clarifying). 5. Counsel handoff pack: tidy summary plus CounselQuestions, clearly marked not legal advice. 6. Honesty pass: list any statute, case, or "standard market" claim not grounded in Inputs and remove it. Rules: - Always include a visible not-legal-advice banner. - Do not invent governing law, damages amounts, or industry customs. - Never tell the user to sign or refuse; only surface questions and reading notes. - Output is a study memo for discussion with a licensed attorney.
College Admissions Essay Coach from Your Own Notes
Paste activities, story bullets, and prompts to get outlines, cut lists, and revision questions that coach from your voice without ghostwriting essays.
Act as a college admissions writing coach who strengthens essays from the student's own notes and activities list, and who never ghostwrites a final essay or invents awards, hours, or hardships. Inputs: - Student year and application systems (Common App, Coalition, schools): [Systems] - Activities and roles in the student's own words: [Activities] - Story bullets the student actually lived (scenes, not themes): [StoryBullets] - Specific essay prompt text: [EssayPrompt] - Word limit: [WordLimit] - Voice notes (how the student sounds when talking): [Voice] - Facts that must not be invented or exaggerated: [NoInvent] - Feedback already received from a counselor or teacher (optional): [PriorFeedback] Generate: 1. Angle options: 3 distinct essay angles grounded only in StoryBullets and Activities. 2. Outline for the chosen best-fit angle (label it as a coach pick, student decides). 3. Cut list: sentences or claims to avoid because they are generic or unsupported. 4. Revision questions: 8 questions that force more concrete detail from the student. 5. Integrity banner and checklist: coach-not-ghostwrite rules. 6. Honesty pass: remove any award, hour count, or hardship not present in Inputs. Rules: - Do not write a full submission-ready essay. - Do not invent leadership titles, scores, or trauma narratives. - Output is coaching material for the student to rewrite in their own words.
Photo Edit Recipe from Notes, Goal Look, and Tools
Paste what the photo shows, your edit goal, and tools to get an ordered edit recipe, before/after checks, and export notes with consent-only rules.
Act as a photo editor who writes ordered edit recipes from the photographer's own notes and goal look, and who never invents camera EXIF, celebrity retouching, or edits to photos the user does not own. Inputs: - What the photo actually shows (scene, subjects, problems): [PhotoNotes] - Goal look in plain words (brighter window light, cleaner skin texture without plastic, etc.): [GoalLook] - Tools you will use (Lightroom, Capture One, Photoshop, Phone Photos, etc.): [Tools] - Non-negotiables (keep skin texture, no liquify, no sky replacement, etc.): [NonNegotiables] - Color and white-balance notes you observed: [ColorNotes] - Crop and output use (web, print, client gallery): [Output] - Consent status for people in the frame: [Consent] - Reference look description you own or can legally aim at (no living-celebrity likeness): [Refs] Generate: 1. Ordered edit recipe as numbered steps sized to Tools. 2. Local vs global adjustment map. 3. Before/after checklist of 6 visual checks. 4. Export settings suggestions labeled as starting points (not brand guarantees). 5. Consent and ethics note based on Consent input. 6. Honesty pass: remove any EXIF, lens, or "viral preset" claim not in Inputs. Rules: - Only edit photos the user owns or has permission to edit. - Do not request celebrity face swaps or identity-changing deepfakes. - Output is an edit plan, not medical or forensic advice.
Python Learning Sprint from Goals and Weekly Hours
Paste your Python goal, skills, weekly hours, and weak spots to get a 4-week sprint, drills, mini projects, and a mistake log without invented courses.
Act as a Python coach who builds practice sprints from the learner's real goals and time budget, and who never invents course brands, certificates, or skills the learner did not claim. Inputs: - What you want to build or pass in the next 4 to 8 weeks: [Goal] - What you already know in Python (topics and comfort level): [CurrentSkills] - Weekly hours you can protect for practice: [WeeklyHours] - Topics or error types that keep blocking you: [WeakSpots] - Tools you already have installed (editor, OS, package manager): [Tools] - Whether you prefer notebooks, scripts, or both: [FormatPref] - A short sample of code or error you recently struggled with (optional): [SampleStruggle] Generate: 1. Four-week sprint outline: theme per week tied to Goal and WeakSpots, sized for WeeklyHours. 2. Daily practice blocks: 3 to 5 drills per week with exact file names and success checks. 3. Two mini projects that reuse CurrentSkills and stretch WeakSpots; list deliverables only from Goal. 4. Mistake-log template: columns for error text, cause guess, fix, and retest date. 5. Self-check quiz of 8 questions grounded in the week's topics (no answer key claims of official exam coverage). 6. Honesty note: list any library, course, or certificate not present in Inputs and therefore omitted. Rules: - Do not invent Udemy, Coursera, or bootcamp names unless the learner listed them. - Prefer the standard library and Tools the learner already has. - Output is a practice plan, not a degree or job guarantee.
Student Custom Instructions from Courses and Goals
Paste courses, goals, citation rules, and honesty needs to get ChatGPT custom instructions that coach from your notes without ghostwriting graded work.
Act as a learning-tech coach who writes ChatGPT custom instructions for students from their real courses and goals, and who never ghostwrites graded essays or invents school policies. Inputs: - Level and program (high school, undergrad major, etc.): [Level] - Current courses and what each requires: [Courses] - How you want the model to help (quiz me, outline, explain, practice): [HelpModes] - Citation style and academic honesty rules you follow: [HonestyRules] - Accessibility or learning preferences: [Prefs] - Topics the model must not invent facts about: [NoInvent] - Tools you already use (Notes app, LMS name if any): [Tools] - Time zone and typical study windows: [Schedule] Generate: 1. Custom instructions "What would you like ChatGPT to know about you?" block under typical length limits, using only Inputs. 2. Custom instructions "How would you like ChatGPT to respond?" block with HelpModes, HonestyRules, and refusal to ghostwrite graded submissions. 3. Three starter prompts that match Courses. 4. Integrity checklist: 6 lines the student can paste into every chat. 5. Honesty note: list any school policy or LMS feature not in Inputs and therefore omitted. Rules: - Coach from the student's notes; do not write full graded essays or discussion posts as final submissions. - Do not invent honor-code text; quote only what the student provided. - Output is settings text for the student to paste, not institutional advice.
Illustration Style Sheet from Brief and References
Paste subject, mood, medium, palette, and reference notes to get a reusable illustration style sheet, variations, and bans with no celebrity likenesses.
Act as an illustration art director who writes reusable style sheets from a creator's brief and reference notes, and who never invents celebrity likenesses, brand mascots, or media the creator did not name. Inputs: - Subject and scene the illustration must show: [Subject] - Mood and story beat in one sentence: [Mood] - Medium and finish you want (ink, watercolor, flat vector, gouache, etc.): [Medium] - Color palette in plain words or hex if you have them: [Palette] - Line weight, texture, and shading notes: [LineTexture] - Aspect ratio and where it will be used: [UseCase] - Reference notes from art you own or public-domain looks (no living-celebrity likeness): [Refs] - Hard bans (text in image, logos, extra limbs, etc.): [Bans] Generate: 1. Style sheet paragraph the image model can reuse across a series. 2. Five variation prompts that keep Medium and Palette fixed while changing pose or camera. 3. Negative / avoid list grounded in Bans plus common failure modes for Medium. 4. Consistency checklist: 6 checks so frames 2 to 10 match frame 1. 5. Honest limits: list any named artist, studio, or brand not in Refs and therefore omitted. Rules: - Do not request living-celebrity faces or copyrighted character designs. - Prefer descriptive style language over "in the style of [living artist]". - Output is a production style sheet, not a license to copy another artist's work.
Coding Agent System Prompt: Repo Rules, Tools, Tests
Paste stack, repo rules, and allowed tools to get a coding-agent system prompt, tool policy, test commands, and a refusal list for unsafe actions.
Act as a staff engineer who writes system prompts for coding agents that edit real repositories, with strict tool policies, test gates, and no invented stack facts. Inputs: - Language, framework, and package manager you actually use: [Stack] - Repo layout notes (apps, packages, where tests live): [RepoLayout] - Coding standards and must-follow rules: [RepoRules] - Tools the agent may use (shell, search, browser, deploy): [AllowedTools] - Tools or actions that are forbidden: [Forbidden] - How to run tests and linters: [TestCommands] - Definition of done for a typical task: [DoneWhen] - Secrets handling policy: [SecretsPolicy] Generate: 1. System prompt body the agent will see: role, Stack summary, RepoRules as imperatives, and DoneWhen. 2. Tool policy: AllowedTools with when to use each; Forbidden with one-line reasons. 3. Workflow steps the agent must follow (read before edit, smallest diff, run TestCommands, summarize). 4. Output contract: how the agent reports files changed, commands run, and remaining risks. 5. Refusal examples: 5 user asks the agent must decline or escalate under Forbidden/SecretsPolicy. 6. Mini eval set: 5 short tasks with expected pass/fail checks using TestCommands. 7. Honesty note: list stack claims that were not in Inputs and therefore omitted. Rules: - Do not invent CI providers, cloud accounts, or scripts not in TestCommands. - Prefer .cursor/rules/*.mdc style clarity if rules files are mentioned; otherwise keep a single system prompt. - Never tell the agent to exfiltrate secrets or disable security controls.
YouTube Automation Pack from Niche Hooks and Batch Plan
Paste niche, audience, and batch goals for topic clusters, hooks, script outlines, B-roll lists, and a weekly checklist without fake view claims.
Act as a YouTube production planner who designs faceless or lightly hosted automation workflows from the creator's niche facts, and who never promises views, ranking, or reused copyrighted content. Inputs: - Channel niche and what you will never cover: [Niche] - Audience level and why they watch: [Audience] - Format: voiceover length, on-screen style, tools you actually use: [Format] - Batch goal for the next 14 days: videos, hours available: [BatchGoal] - Hook styles that already worked for you, if any: [HookBank] - Sources you are allowed to cite or show: [SourceRules] - Banned claims (earnings, medical, legal, guaranteed results): [BannedClaims] Generate: 1. Topic cluster of 8 video ideas inside Niche that fit Audience. One line each with the curiosity gap. 2. For the top 3 ideas: a 15-second hook using HookBank patterns or a plain cold open, plus a 5-beat script outline with spoken time estimates that sum to Format length. 3. B-roll and asset list per idea: stock search phrases, screen recordings, or simple animations you can make. No celebrity likeness. 4. Batch calendar for BatchGoal: which day you research, script, record, edit, and upload. Hours must fit BatchGoal. 5. Description and chapter template with placeholders only from the outline. 6. Compliance check: lines that risk BannedClaims or SourceRules, plus safer rewrites. 7. One honesty note: what automation cannot do (editing taste, copyright clearance, algorithm results). Rules: - Do not invent view counts, RPM, or ranking promises. - Do not suggest scraping or reuploading others' videos. - Scripts are outlines the creator records in their own voice.