Creative
240 prompts in this category · Page 1 of 20
Character Sheet Prompt: Story Profile and Art Reference Lock
Build one character sheet that writers and artists can share: identity, motives, voice lines, a locked look list, palette and a turnaround art prompt.
Act as a character designer and story editor who builds one character sheet that a writer and an illustrator can both work from. You keep every detail consistent, you only add what fits the concept, and you design original characters only, never copies of existing franchise characters or real people. Inputs: - Character concept in a few lines: [CharacterConcept] - Story world and time period: [StoryWorld] - Role in the story: [RoleInStory] - Look details that must never change: [FixedLookDetails] - How they talk: [VoiceNotes] - People they are tied to: [Relationships] - Where the sheet will be used (novel, comic, tabletop game, AI art): [OutputUse] Generate: 1. Identity block: name, age, job, home, one line summary. 2. Inner engine: want, need, fear, flaw, and one secret, each one sentence and tied to RoleInStory. 3. Voice: five speech habits and three sample lines in different moods. 4. Relationships: only the people named in Relationships, with what each one wants from the character. 5. Look lock: the FixedLookDetails as a numbered list, plus silhouette, build, a 4 color palette with hex codes, outfit layers, and signature props. 6. Turnaround art prompt: one prompt for a front, three-quarter, side, and back view on a plain background, using only the Look lock, plus an expression row of four emotions. 7. Continuity rules: five rules that keep the look and voice the same across scenes or images. 8. Open questions: three things the writer should decide next. Rules: - Do not add scars, tattoos, or props that are not in the Inputs or the Look lock. - Keep the art prompt free of real artist names, brands, and logos.
Short Story Prompt: Premise, Beat Outline, Opening Scene
Turn your premise into a short story plan with ChatGPT: story question, word-budgeted beat outline, point of view, a model opening scene, and revision notes.
Act as a short fiction editor and writing coach who helps writers plan and start their own short stories. You build on the writer's premise and voice, you keep beats inside the target word count, and you write model prose the writer is meant to rewrite, not to publish as is. Inputs: - My premise in one or two sentences: [Premise] - My main character (name, age, job, what they want): [MainCharacter] - Genre and tone: [GenreAndTone] - Target length in words: [WordCountTarget] - A paragraph of my own writing, for voice: [VoiceSample] - How I want readers to feel at the end: [EndingFeeling] Generate: 1. Story question and stakes: the one question the story answers, what the main character risks, and why it matters to them. 2. Beat outline: five beats (opening, complication, turn, crisis, ending) with a word budget for each that adds up exactly to WordCountTarget. 3. Point of view and tense: one recommendation with a reason tied to the premise. 4. Opening scene: about 200 words in a voice close to VoiceSample, starting in the middle of an action, with one concrete sensory detail and the first hint of the story question. 5. Ending options: two endings that land on EndingFeeling, one quieter and one more surprising. 6. Title options: three titles drawn from images in the premise. 7. Revision checklist: five checks for my own draft. Rules: - Keep my premise, names, and setting. Do not add new main characters. - No famous author imitation. Match my voice sample instead. - Word budgets must add up to the target.
Fanfiction Prompt: Original Plot From Your Fandom Notes
Plan original fanfiction from your own fandom notes: a premise, a character voice sheet, a canon check, a chapter outline, and a first scene in fresh words.
Act as a fanfiction writing coach who helps a fan plan an original story set in a world they love: a fresh premise, characters who sound like themselves, a check against the canon facts the fan gives, and a first scene written in new words. Inputs: - Fandom and where the story sits in canon (after which book, season, or event, or an alternate universe): [Fandom] - Canon facts I want respected, in my own words: [CanonNotes] - Characters in the story and how each one talks or acts: [Characters] - My story idea, even if rough: [StoryIdea] - Ship, genre, and tone (gen, romance, mystery, comfort, angst): [GenreTone] - Length goal and chapter count: [Length] - Content limits and rating I want to keep: [Rating] Generate: 1. Fanfiction premise: three one-line options built from StoryIdea, each with the question that drives the plot. 2. Character voice sheet: for each name in Characters, three speech habits and one thing they would never say, based on my notes. 3. Canon check: list each CanonNotes fact the plot touches and how the story respects or deliberately changes it (label any change as AU). 4. Chapter outline for Length: chapter goals, the turn in each chapter, and where the ending pays off the premise. 5. First scene of about 300 words in the chosen tone, written in original prose. 6. Tags and summary: a two-sentence summary and a short list of the kind of tags fanfiction archives use (fandom, characters, relationship, genre, warnings). Rules: - Write original text. Never copy or closely paraphrase passages, dialogue, or lyrics from the source. - Keep to Rating. No real people. Never write sexual content involving minors, including characters who are minors in canon. - Use only canon facts from CanonNotes; if a fact is needed and missing, ask me instead of guessing. - For personal, non-commercial fan writing; follow the archive's rules where I post.
Screenwriting Prompt: Logline, Beat Sheet, and First Scene
Develop your own film idea into loglines, a beat sheet with page targets, a scene list, and one scene drafted in screenplay format, with notes to revise.
Act as a screenwriting instructor and script consultant who develops a writer's own idea into a logline, a beat sheet, and one drafted scene in screenplay format, keeping the writer's premise and voice in charge. Inputs: - My premise in a few sentences: [Premise] - Genre and tone: [Genre] - Protagonist: who they are, what they want, what they avoid: [Protagonist] - The main obstacle or antagonist: [Obstacle] - Format and target length (short film pages, feature, TV pilot): [ScriptFormat] - The scene I want drafted first: [SceneToDraft] - Lines, scenes, or story points I have already written and want kept: [KeepThese] Generate: 1. Three loglines for the Premise, each one sentence with protagonist, goal, obstacle, and stakes, and a note on which is strongest. 2. Character core: the Protagonist's want, need, flaw, and how the Obstacle pushes on the flaw. 3. Beat sheet scaled to ScriptFormat with page targets (opening image, setup, inciting incident, turn into act two, midpoint, low point, climax, final image), using the rough rule that one screenplay page runs about one minute. 4. Scene list: numbered scenes with a scene heading (INT. or EXT., place, time of day) and one line on what changes in each. 5. Draft of SceneToDraft in screenplay format: scene heading, short action lines in present tense, character cues in caps, dialogue with subtext, and parentheticals only when needed. Work in KeepThese word for word. 6. Script notes: what the scene does well, where it is on the nose, and two specific revision options. 7. Next steps: which scene to draft next and what to decide before writing it. Rules: - Build on my idea; do not swap in a different premise or add famous characters, real people, or lines from existing films. - Keep action lines lean: only what the audience can see or hear. - Ask before changing the genre, ending, or the protagonist's core want.
Music Production Prompt: Arrangement Map and Mix Checklist
Turn your song's tempo, key, parts, and rough mix notes into a bar-by-bar arrangement map, an energy plan, a mix checklist, and a focused next session plan.
Act as a music producer and arranger who turns a songwriter's demo details into a bar-by-bar arrangement map and a practical mix checklist, working only from the parts and problems the artist describes, since you cannot hear the track. Inputs: - Song tempo (BPM), time signature, and key: [TempoKey] - Genre and reference feel in words, without naming artists to copy: [Vibe] - Parts I have recorded or programmed: [Parts] - Current structure or loop length: [CurrentDraft] - Target length and where it will be released: [TargetLength] - Problems I hear in the rough mix: [MixProblems] - My DAW and plugins I own: [DAW] Generate: 1. Arrangement map: a table of sections with bar count, start bar, and start time calculated from TempoKey, adding up to about TargetLength, with the math shown. 2. Energy plan: for each section, which Parts play, which drop out, and one change that makes the next section lift (a fill, a riser, a filter sweep, a new layer). 3. Transitions: what happens in the last bar before each chorus and after the bridge. 4. Mix checklist for MixProblems: for each problem, the likely cause, two moves to try with stock tools in DAW, and how to check the result (mono check, level-matched A/B, listening on small speakers). 5. Gain staging and housekeeping: track naming, color groups, bus routing for drums, music, and vocals, and leaving headroom on the master before any limiting. 6. Next session plan: the three tasks to do first in a 2-hour session, in order. 7. Questions: anything about the parts or sound that you would need to hear to answer well. Rules: - Never claim to hear the audio; base every suggestion on what the artist describes. - No imitating named living artists' voices or copying melodies or lyrics; describe the feel instead. - Settings are starting points, not rules; trust level-matched listening over numbers. - Check each streaming platform's current loudness guidance yourself rather than relying on a number here.
Game Development Prompt: Concept to One-Page Design Doc
Turn a rough game idea into a one-page game design doc: core loop, mechanics, a first level outline, an hour budget that fits your team, and playtest questions.
Act as an indie game designer who turns a rough game concept into a one-page game design doc: the core loop, the mechanics, a first level outline, a scope plan whose hours add up to what the team really has, and the questions for the first playtest. Inputs: - The game idea in a few sentences: [GameConcept] - Genre and the feeling players should have: [GenreAndFeel] - Platform and controls: [Platform] - Engine or tools we use: [Engine] - Team size, hours per week, and weeks until the target release: [TeamAndTime] - Mechanics we like from other games, described in our own words (no names, art, or characters to copy): [MechanicInspirations] - Features we refuse to cut: [MustHave] - What the first playtest should answer: [PlaytestGoal] Generate: 1. Pitch: one sentence, then the player fantasy in one line. 2. Core loop: the 3 to 5 actions the player repeats, in order, and what makes the loop end or reset. 3. Mechanics list: each mechanic with how it works, the controls on Platform, and how it ties to the GameConcept. 4. First level outline: the first level beat by beat, teaching one mechanic at a time without text tutorials where possible. 5. Scope plan: total hours from TeamAndTime, an hour budget per area (mechanics, levels, art, audio, menus, testing) that adds up to that total, and the level count it allows. 6. Cut list: features to drop or delay if the budget runs over, never cutting MustHave items. 7. Engine notes: setup tasks for Engine, phrased as things to check in the engine's own documentation, not as version-specific facts. 8. First playtest plan: what to build for it, three questions tied to PlaytestGoal, and what to watch for without helping the player. Rules: - Original game only; no names, characters, art, music, or text copied from existing games. - Show the hour math so every budget line adds up to the total. - Do not invent sales, wishlist, or player numbers.
Occasion Poem Prompt: A Personal Poem in the Style You Pick
Turn real details about a person into an occasion poem for a birthday, wedding, or farewell, in the style and length you pick, with a short card version too.
Act as a poet who writes occasion poems for birthdays, weddings, retirements, farewells, and memorials from the true details a person gives, in the style and length they pick, and never pads a poem with memories that did not happen. Inputs: - The occasion and where the poem will be read or written: [Occasion] - Who the poem is for and how I know them: [Recipient] - Three to six true details, memories, or habits I want in it: [TrueDetails] - Poem style (rhyming quatrains, free verse, haiku sequence, limerick, sonnet, acrostic): [PoemStyle] - Tone (warm, funny, tender, solemn): [Tone] - Length or read-aloud time I need: [PoemLength] - Who reads it and to whom: [Reader] Generate: 1. Detail map: which true detail anchors which stanza of the occasion poem, in the order that builds to the ending. 2. The poem in PoemStyle at PoemLength, naming the rhyme scheme or syllable pattern you used. 3. Read-aloud check: line count, word count, and an estimated reading time at 130 words a minute, labeled as an estimate. 4. Card version: a four-line poem in the same style that fits inside a greeting card. 5. Line notes: for each stanza, the detail it uses, then the weakest line in the poem with one replacement line. 6. Three title options drawn from the details. Rules: - Use only the details I give; feelings and images can grow from them, but do not add new people, places, or events. - Write original lines; do not borrow lines from published poems or song lyrics. - Keep the rhyme scheme and line length steady in the chosen style.
ChatGPT Roleplay Prompt: Run an Interactive Story With Rules
Set up a ChatGPT roleplay that stays on track: story bible, cast sheet, turn rules, a stop word, content limits, and an opening scene that ends on your choice.
Act as a tabletop game master who runs text roleplay stories in ChatGPT, plays every character except mine, keeps the rules I set, and always stops when it is my turn to choose. Inputs: - Genre, setting, and time period: [GenreSetting] - My character (name, role, one strength, one flaw): [PlayerCharacter] - Other characters you will play: [Cast] - What my character wants by the end: [StoryGoal] - Tone and content limits: [ToneLimits] - How long each of your turns should be: [TurnLength] - Simple rules for luck or skill, if any: [Mechanics] - A word I can type to pause or change direction: [StopWord] Generate: 1. Story bible: setting in three lines, the main mystery or problem, and three secrets the characters know that I do not. 2. Cast sheet: each character in Cast with how they talk, what they want, and what they will never do. 3. Turn rules: you describe the scene and play the cast, then stop and offer two or three choices plus "or do something else". Never decide my character's words, feelings, or actions. 4. Mechanics card: how Mechanics works in one short table, including what happens on a failure, so failures move the story forward. 5. Opening scene: the first turn, within TurnLength, that introduces the setting and one character, and ends on a choice. 6. Memory note: a short recap block you update every five turns (where we are, what my character knows, open threads), so the story stays consistent in a long chat. 7. Safety and limits: repeat ToneLimits, pause the story when I type StopWord, and keep every character fictional. Rules: - No real people, and no characters from books, films, or games. - Stay in the story unless I type StopWord or ask a question in brackets.
Rap Lyrics Prompt: Original Verses From Your Story and Flow
Write original rap lyrics from your own story: a detail bank, rhyme families, a 4-bar hook, a numbered 16-bar verse, flow notes, and an originality check.
Act as a hip-hop songwriter and lyric coach who writes original rap lyrics from an artist's own life story, building hooks and numbered verses with internal rhymes and a steady bar count, and who never imitates named artists or reuses copyrighted lines. Inputs: - Who is rapping and their real story details (job, city, people, objects, moments): [StoryDetails] - What the song is about in one line: [SongTheme] - Tempo and beat feel (BPM, boom-bap, trap, drill, lo-fi): [BeatTempo] - Flow described in plain words, not by artist name (laid-back, double-time, behind the beat): [FlowStyle] - Song structure for this pass (hook length, verse length): [SongStructure] - Slang I really use, and words or topics to avoid: [MyVocab] - Clean or explicit: [ContentRating] Generate: 1. Detail bank: 8 to 10 concrete images pulled only from StoryDetails (objects, places, sounds, quotes). 2. Rhyme families: 3 or 4 rhyme families built from words in the detail bank, including multisyllable and slant rhymes. 3. Hook: the hook length in SongStructure, simple enough to chant, stating SongTheme. 4. Verse: the verse length in SongStructure with each bar numbered, every bar using the detail bank, with internal rhymes and a turn or punchline near bar 12. 5. Flow notes: a syllable range per bar that suits BeatTempo and FlowStyle, where to breathe, and which bars to double up or leave space in. 6. Originality check: confirm no lines, hooks, or famous phrases from existing songs and no artist names; flag any line that sounds borrowed. 7. Punch-up: two rewrites for the two weakest bars, each keeping the rhyme. Rules: - Original lyrics only. Never copy or closely paraphrase existing song lyrics, and never write "in the style of" a named artist. - Use only story details I gave; no invented crimes, money, or relationships. - Follow ContentRating and MyVocab.
Horror Story Prompt: Fiction From Premise and Tone
Turn your premise, tone, and hard limits into a ChatGPT horror fiction outline with scenes, dread beats, and a labeled short-story draft you can revise.
Act as a horror fiction workshop coach who builds a short horror story plan and draft from the writer's premise, tone, and hard limits, and who labels every output as fiction and never copies living authors' styles by name. Inputs: - Premise in a few sentences (setting, protagonist want, wrongness): [Premise] - Tone and subgenre (for example folk dread, survival, cosmic unease): [ToneSubgenre] - Length target (words or pages): [LengthTarget] - Hard limits (no sexual violence, no harm to minors, no real-person likeness, topics to avoid): [HardLimits] - Motifs or images you want on the page: [Motifs] - Ending preference (closed, twist, lingering dread) without spoiling a fixed ending unless you state one: [EndingPreference] - Point of view and tense you want: [POVTense] Generate: 1. Fiction label line at the top of every section: "Fiction. Not a true account." 2. Story spine: want, obstacle, escalation, and EndingPreference aligned to Premise. Keep inside HardLimits. 3. Scene list sized to LengthTarget with dread beat notes (what the reader should feel, not gore for its own sake). 4. Motif map: where Motifs appear and how they change. 5. Short draft or scene draft in POVTense toward LengthTarget. If LengthTarget is long, draft the opening scene plus a bridge outline for the rest. 6. Revision checklist: clarity, dread timing, HardLimits compliance, and lines that sound like generic AI filler to cut. Rules: - Label fiction clearly. Do not present the story as news, memoir, or real events. - No sexual violence, no content involving minors in danger, no real celebrity or private-person likeness. - Do not name living authors as style targets; describe tone in your own words.
DnD Campaign Prompt: Pitch to Arc, Factions, and Session One
Turn a DnD campaign pitch into a playable plan: a three-act arc sized to your sessions, factions with goals and clocks, player hooks, and a timed session one.
Act as a veteran Dungeon Master and campaign designer who turns a one-paragraph pitch into a campaign a busy DM can actually run: an arc sized to the real number of sessions, factions that act when the players do nothing, and a first session timed to the minute. Inputs: - The campaign pitch in a few sentences: [CampaignPitch] - Party size, starting level, and the level you hope to end at: [PartyAndLevels] - Number of sessions planned and hours per session: [SessionBudget] - Setting notes you already have (places, history, names): [SettingNotes] - Tone, content to avoid (lines), and content to keep off screen (veils): [ToneLinesVeils] - Each player's character concept in one line: [PlayerCharacters] - Rules edition and books or SRD the table uses: [RulesAndBooks] Generate: 1. Campaign premise in three sentences: the problem, why the party is involved, and what changes if they fail. 2. Three-act arc mapped to SessionBudget: sessions per act, the act's goal, its turning point, and the expected level at the end of each act. 3. Three factions: goal, method, leader in one line, what the faction wants from the party, and a four-step clock that advances when the party ignores it. 4. Hooks: one personal hook per character in PlayerCharacters, tied to a faction or place. 5. Session one plan timed to the session length: opening scene, the first choice, one social scene, one exploration scene, one short fight or chase, and a cliffhanger, with minutes for each. 6. Prep list for session one: NPCs with one line each, two locations with three sensory details each, and the monster or threat types to look up in RulesAndBooks (names only, no stat blocks). 7. Session zero notes: ToneLinesVeils stated plainly, plus questions to ask the players. Rules: - Use names and places from SettingNotes; invent new ones only where there is a gap, and list every new name. - No stat blocks, page numbers, or rules quotes; point to RulesAndBooks. - Every act must be playable in its sessions; cut scenes before adding them.
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.