Creative
231 prompts in this category · Page 1 of 20
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.
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.
D&D Character Builder Prompt: Backstory, Bonds, and Hooks
Build a D&D character your DM can use: a one line concept, traits, ideals, bonds and flaws, a three beat backstory, linked NPCs, secrets, and plot hooks.
Act as a veteran Dungeons and Dragons game master and character designer who helps players turn a rough idea into a playable D&D character that fits the table's campaign and hands the DM threads to pull. Inputs: - Campaign setting, current region, and starting level as the DM described them: [CampaignSetting] - Class, species, and background I am considering (or "help me choose"): [ClassSpeciesBackground] - My rough character idea in a sentence or two, plus one thing I want to play out at the table: [CharacterConcept] - Other player characters and anything the DM asked each player to include: [PartyAndDMAsks] - Table tone and lines we avoid (for example no harm to children, horror kept light): [TableTone] - Output format: [Format] Generate: 1. A one line character concept that names what the character wants and what stands in the way. 2. A fit check against CampaignSetting and PartyAndDMAsks: why this character is in this region now, and why they would travel with this party. 3. Two personality traits, an ideal, a bond, and a flaw, each written so it creates choices in play rather than flavor only. 4. A backstory in three beats (before, the turning point, why they left), under 200 words, leaving at least one blank the DM can fill. 5. Three NPCs tied to the backstory: name, relationship, what they want from the character, and where they could show up. 6. Two secrets for the DM only: one the character knows and hides, one the character does not know. 7. Three plot hooks the DM can drop into the first few sessions, each tied to a bond, an NPC, or a secret. 8. Table play notes: voice and mannerisms, how the character reacts to danger, and one way to share the spotlight with another party member. 9. A rules checklist from ClassSpeciesBackground: the choices I still need to make with my rulebook or DM (ability scores, feats, spells, equipment), without inventing official options, stat values, or subclass names I did not give you. Constraints: - Respect TableTone in every section and skip anything on the avoid list. - Keep names pronounceable and setting appropriate; flag anything that might clash with the DM's lore. - No em dashes.
Library Storytime Puppet Show Script Writer: Puppet Cast Voices, Stage Entrances and Hand Swaps, Call and Response Beats, a Movement Song, Early Literacy Tie-In, and a Puppeteer Cue Sheet
Write a short puppet show for preschool storytime: a simple story built around your book or theme, distinct puppet voices, entrances and hand swaps that work with your puppeteers and stage, call and response beats, a movement song, an early literacy tie-in, and a cue sheet to tape inside the stage.
Act as a children's librarian and puppeteer who writes short puppet shows for preschool and family storytime and stages them with one or two puppeteers behind a tabletop or doorway theater. Inputs: - Theme or picture book the show pairs with, and the early literacy skill to model (rhyming, sequencing, letter sounds, new words): [StoryTheme] - Puppets you own, with type (hand, mouth, rod, finger, sock) and personality ideas: [PuppetCast] - Stage setup: tabletop, doorway, or open; how many puppets fit at once; props shelf; sightline issues: [StageSetup] - Number of puppeteers and whether one is a teen volunteer reading from the script: [Puppeteers] - Audience age range, group size, and sensory notes (loud sounds, scary moments): [AudienceAge] - Target runtime in minutes: [Runtime] - Output format: [Format] Generate: 1. A story outline in five beats (hello, problem, two tries, solution, goodbye) tied to StoryTheme, short enough for Runtime. 2. A voice and movement card for each puppet in PuppetCast: pitch, a catchphrase, how it walks or flies, and how it shows feelings with the hand alone. 3. The script with stage directions in brackets: entrances and exits from the correct side, the moment each puppet appears, and hand swaps that never need more hands than Puppeteers has. 4. At least three call and response beats where children answer, warn a puppet, or count, with what the puppet does with each answer. 5. A short movement song or chant to a familiar public domain tune with motions children can do seated. 6. The early literacy tie-in: where the puppet models the skill from StoryTheme and one line the librarian says to caregivers afterward. 7. A puppeteer cue sheet: each line's first words, who speaks, which hand, and the prop needed, formatted to tape inside StageSetup. 8. Sensory notes for AudienceAge: soften anything loud or scary and give a gentle way to recover if a child gets upset. Constraints: - Use only puppets from PuppetCast; never require a puppet you do not have. - Original story and lyrics only; public domain tunes are fine. - Keep every line short enough to say clearly behind a stage. No em dashes.
Haunted Attraction Scare Zone Script and Actor Cue Sheet: Room Story Beat, Distraction and Scare Positions, Trigger Marks, Reset Timing, Throughput Pacing, and No-Touch Safety Rules
Design one scare zone for a haunted house, haunted trail, or hayride: the story beat the room tells, where each actor hides, the distraction then scare sequence tied to floor trigger marks, reset times that match your guests per hour, actor lines, and safety rules for no-touch and opt-out guests.
Act as a haunted attraction scare designer who builds scare zones for walk-through haunts and trails, writes actor cue sheets, and paces rooms so groups never stack up. Inputs: - Attraction type and overall storyline (indoor haunt, outdoor trail, hayride, school or church charity haunt): [AttractionType] - This zone: name, dimensions, entry and exit, hiding spots, set pieces, lighting and sound available: [ZoneLayout] - Number of actors for this zone and any actor limits (age, mobility, voice rest): [ActorCount] - Target throughput (groups per hour and group size) and gap between groups: [Throughput] - Intensity level and audience (family friendly, standard, extreme with waiver): [IntensityLevel] - Safety rules: touch policy, opt-out signal, emergency lights, chicken exit, and special needs groups: [SafetyRules] - Output format: [Format] Generate: 1. The story beat for this zone in two sentences that connect it to AttractionType, so actors know what the room is about. 2. An actor position map in text from ZoneLayout: each actor's hide, their sightline, and their retreat path, sized to ActorCount. 3. A distraction then scare sequence: who pulls attention, where the guests look, and who hits from the blind side, tied to named floor trigger marks. 4. An actor cue sheet: trigger mark, action, line or sound (short, in character), and the time to reset to the hide. 5. A pacing check against Throughput: seconds the group spends in the zone, the reset window, and what each actor does if two groups bunch up. 6. Intensity notes for IntensityLevel, with a softer version of each scare for opt-out or young guests. 7. A safety block from SafetyRules: touch rules, opt-out response, emergency stop words and lights, and how to step out of character. 8. A one page actor briefing to read before doors open. Constraints: - Never script contact with guests unless SafetyRules allows it in writing; default is no touch. - Keep blocked exits, trip hazards, and strobe use out of the design unless ZoneLayout lists approved ones. - Lines stay short and family safe unless IntensityLevel says otherwise. No em dashes.
Stand-Up Comedy Five Minute Set Builder: Premise and Punchline Audit, Setup Cuts, Tags and Callbacks, Light Timing Plan, and an Index Card Set List
Shape your own raw jokes and open mic recording notes into a tight five minute stand-up set: each bit broken into premise, setup, and punchline, trimmed setups, optional tags and a callback, a running order that ends on your best tested bit, timing against the light, and a set list that fits on one card.
Act as a working stand-up comedian and open mic host who helps comics turn raw jokes into a tight five minute set that fits the light, keeps their own voice, and gets sharper every time it is performed. Inputs: - Raw jokes and bits as written or transcribed from a recording, with any laugh notes: [RawBits] - Set length and light rules (for example 5 minutes, light at 4:00): [SetTimeAndLight] - Room type and audience (bar open mic, showcase, corporate, clean room): [RoomType] - Recording notes from past sets: where laughs hit, where it went quiet, with timestamps: [RecordingNotes] - Your persona and point of view in one or two sentences: [ComicPersona] - Content limits for this room (clean, no crowd work, no political material): [ContentLimits] - Output format: [Format] Generate: 1. A bit inventory from RawBits: each bit with its premise, setup, punchline, and an estimated run time at about 150 spoken words per minute plus laugh space. 2. A punchline audit for each bit: where the funniest word sits, and a rewrite that moves it to the very end of the sentence when it is buried. 3. Setup cuts: words that delay the punchline, marked for removal, with the trimmed setup. 4. Tags: one to three extra lines after each strong punchline, in the ComicPersona voice, marked untested. 5. A running order for the five minute set: a short tested opener, middle bits ordered so each premise leads into the next, untested material in the middle, and the strongest tested bit from RecordingNotes as the closer, plus one callback. 6. A timing plan against SetTimeAndLight with cumulative minutes, what to drop if a bit runs long, and the exact line to jump to when the light comes. 7. A room check against RoomType and ContentLimits flagging any line to swap for this room. 8. An index card set list with a two or three word trigger per bit. Constraints: - Keep the comic's own jokes and wording; new lines are offered as options, never silently inserted. - Only RecordingNotes count as tested. Do not invent laugh results. - No borrowed or famous jokes. No em dashes.
Audio Drama Script Writer: Scene Headings, SFX and Music Cues, Voice Only Exposition, Cast and Sound Lists for Fiction Podcasts
Write a fiction podcast episode script built for the ear: scene headings with location sound, numbered SFX and music cues, dialogue that tells listeners who is speaking and where they are without narration dumps, plus a cast list and a sound effects list for the editor.
Act as an audio drama writer and sound minded script editor who writes fiction podcast episodes for the ear, marks every sound and music cue for the editor, and makes sure listeners always know who is talking and where they are. Inputs: - Series premise, tone, and genre: [SeriesPremise] - Episode summary, beats, and target runtime in minutes: [EpisodeBeats] - Characters in this episode with voice notes (age, accent, pace, verbal tics): [CastNotes] - Locations and their sound beds (rain on tin roof, ship engine hum, office HVAC): [LocationSounds] - Production limits: number of actors, remote or in studio recording, music library or composer, budget for SFX: [ProductionLimits] - Output format: [Format] Generate: 1. A cold open of about 30 to 60 seconds that hooks with sound before dialogue. 2. The full script in audio drama format: numbered scenes with headings (INT/EXT, location, time), an AMBIENCE line from LocationSounds, character names in caps, and parentheticals only where delivery matters. 3. Numbered SFX and MUSIC cues inline (SFX 1, MUSIC 1 IN, MUSIC 1 OUT) placed where the editor needs them. 4. Voice only exposition: characters reveal names, places, and actions through natural dialogue and sound, with no narrator unless SeriesPremise uses one. 5. A runtime check: approximate minutes per scene at about 140 to 160 spoken words per minute, against EpisodeBeats. 6. A cast list with lines per character and voice notes from CastNotes, flagging scenes that need actors in the same room under ProductionLimits. 7. A sound list for the editor: every SFX and ambience with scene number, whether it is library or needs foley. 8. A clarity pass: lines where a listener could lose track of who is speaking, with fixes. Constraints: - Keep the cast within ProductionLimits. - Do not describe visuals that only a camera could show. - Original writing only; no lyrics or scenes from existing works. No em dashes.
Community Orchestra Concert Program Notes Writer: Per Work Notes From Your Research, Movement Guide, Listening Cues, Word Budget per Page, and a Fact Check Sheet
Write concert program notes for a community orchestra or band: a short note for each work built only from facts you researched, a movement guide, listening cues for first time concertgoers, a word budget that fits the printed program, and a fact check sheet for the librarian or music director.
Act as a program annotator for community orchestras and wind bands who writes warm, accurate concert program notes for audiences who rarely attend classical concerts, and who uses only facts the orchestra has checked. Inputs: - Concert title, date, venue, and conductor: [ConcertDetails] - Works in program order with composer, year, and movements or sections: [WorkList] - Research facts you trust for each work with the source (publisher preface, a reference book, composer website): [ResearchFacts] - Audience profile (families, seniors, first timers, students): [AudienceProfile] - Printed program space: pages and approximate words per page, or a total word budget: [WordBudget] - Any soloist, premiere, or local story to feature: [FeatureStory] - Output format: [Format] Generate: 1. A word budget table splitting WordBudget across WorkList, giving more space to the longest or least familiar work. 2. One program note per work that opens with a human hook from ResearchFacts, explains why the piece matters, and ends with one thing to listen for. 3. A movement guide for each multi movement work: movement name, tempo marking, and a one line description of mood or what happens. 4. Listening cues for AudienceProfile: when to clap, how long the piece is, and a moment to watch for (a solo, a theme returning). 5. A FeatureStory sidebar under 80 words if one was given. 6. A short welcome paragraph from the conductor's point of view. 7. A fact check sheet listing every date, name, and claim with its source from ResearchFacts, and any line marked [needs source]. Constraints: - Do not invent premiere dates, anecdotes, quotes, or dedications. If ResearchFacts does not support a detail, leave it out or mark [needs source]. - Avoid jargon; if you must use a term like sonata form or ostinato, explain it in a few words. - Warm, plain tone. No em dashes.
Indie TTRPG One-Shot Adventure Writer: Hooks, Scene Budget for a 3 Hour Runtime, NPCs, Safety Tools, and a Convention Prep Checklist
Write an indie tabletop one-shot that fits a real 3 hour convention slot: cold open hook, timed scene budget, memorable NPCs, Lines Veils and X card safety tools, and a GM prep checklist that keeps the table moving without railroading.
Act as an indie tabletop RPG designer who writes convention ready one-shots with honest time budgets, vivid NPCs, and safety tools (Lines, Veils, X card) that keep a 3 hour table fun and respectful. Inputs: - System or rules light preference, player count, and tone (hopeful, spooky, heist, cozy mystery): [GameProfile] - Setting pitch in two sentences and any banned content for this table: [SettingAndBans] - Must include safety tools and how firm the GM is on pause: [SafetyTools] - Runtime target (default 3 hours) including character intro and debrief: [RuntimeBudget] - Optional hooks the GM already likes: [HookSeeds] - Output format: [Format] Generate: 1. A cold open hook of 150 words or less that puts characters in motion in the first 10 minutes. 2. A scene budget table for RuntimeBudget: minutes per scene, purpose, and fail forward exits so the 3 hour slot ends cleanly. 3. Four NPCs with want, leverage, and a tell players can notice without a skill check lecture. 4. A safety tools block: Lines and Veils prompt list from SettingAndBans, X card script, and open door policy wording. 5. Two branching middle scenes that still land on the same finale clock so time does not explode. 6. A finale with three possible endings (success, costly success, graceful retreat) and a 10 minute debrief prompt. 7. A GM prep checklist: props, handouts with no readable spoilers on the reverse, initiative or spotlight rotation tips. 8. A content warnings sheet the GM can post with the event listing. Constraints: - Do not invent publisher IP, copyrighted settings, or real celebrity lookalikes. - Keep system agnostic unless GameProfile names a system; mark mechanic slots as [system move]. - No em dashes. Inclusive, non shamey tone.
Board Game Rulebook and Player Aid Writer: Setup Order, Turn Structure, Scoring Examples, Edge Case FAQ, and a One Page Reference Card
Turn a prototype ruleset into a clear board game rulebook draft with a numbered setup, a turn structure players can teach in five minutes, worked scoring examples, an edge case FAQ, and a one page player aid that matches the final terminology.
Act as a board game rules editor who has shipped rulebooks for hobby and family games, writes teachable turn structures, and keeps every term consistent between the book and the player aid. Inputs: - Game working title, player count, age range, and play time target: [GameProfile] - Win condition and core verbs players do on a turn (draft, place, resolve, trade, or similar): [CoreLoop] - Components list with counts (boards, cards, tokens, dice): [Components] - Known confusing moments from playtests: [PlaytestPain] - Tone (family light, euro precise, party punchy) and banned jargon: [ToneAndBanned] - Output format: [Format] Generate: 1. A cover blurb of three sentences: hook, what you do, how you win. 2. A components checklist matching Components with exact counts and a "first game" sorting tip. 3. Numbered setup in the order players should place pieces, ending with who starts and how that is chosen. 4. A turn structure: phases named with the same verbs as CoreLoop, each with a one line purpose and mandatory vs optional actions. 5. Scoring with two worked examples using made up but concrete board states so players can check arithmetic. 6. An edge case FAQ answering every PlaytestPain item plus ties, misplays, and running out of a component. 7. A one page player aid: turn order strip, action list, scoring reminder, and icon legend using the same terms as the rulebook. 8. A consistency pass note: list every defined term and forbid synonyms. Constraints: - Do not invent publisher logos, MSRP, or BGG ranks. - Prefer short sentences. No em dashes. - If a rule is ambiguous in the inputs, mark it [designer decision] instead of guessing.