8,214 AI prompts, ready to copy

Create a checklist for checking whether a collection I generated with AI might look too similar to existing collections or recognisable works: search steps (reverse image search, marketplace searches, art databases), what to record, how to compare styles, and what to do if something looks too close. Include a reminder that this is not legal advice.

Draft a plain-language outline (not legal advice) of topics I should address in the licence and description for a digital collectible series: what the buyer can and cannot do with the artwork, commercial use limits, my tools used (including AI image generation), AI disclosure, marketplace policy links, and a statement that no return or value is promised. Flag items I should ask a lawyer to review.

Write a 120-word collection description for a series of 500 stylised market-trader portraits. State facts only: the style, the inspiration, how images were made (hand-drawn base plus AI-assisted exploration, if that is true), the licence summary and a link placeholder to the full terms. No investment language, no promises about future value, no "limited chance", no urgency pressure. Tone: calm, warm, honest.

Provide a balanced pro and con outline for the debate motion "Should animal testing be completely banned?". Include at least four points for each side, with a brief explanation for each.

Here are my notes after listening to the generated night loop: [YOUR NOTES: e.g. 'the celesta is too bright', 'the drone covers footsteps', 'loop seam at 2:28']. Convert them into specific revision settings or brief changes I can apply (instrument, register, tempo, dynamics, length). Order the changes by impact, and tell me which problems are better fixed in an editor than by regenerating.

Creative brief: background loop for a cosy farming game, daytime orchard. Mood: warm, unhurried, gently playful. Tempo 80 to 90 BPM, major key (G major or D major). Lead: solo acoustic guitar or soft piano, support with light pizzicato strings and a soft woodwind. No drums or only a very quiet brushed shaker. Structure: 8-bar A section, 8-bar B section, return to A, loop point at the end with a quiet ending that can fade into the start. Length 2 minutes. Dynamics: low, never above mezzo-piano, so footsteps and UI sounds stay clear. Avoid: big brass, epic crescendos, heavy bass, dramatic stingers, dense reverb tail that ruins looping.

Creative brief: night-time loop for a haunted orchard in a cosy game; unsettling but not horror. Tempo 60 to 70 BPM, minor mode (D minor), sparse. Instruments: low sustained strings, soft celesta or music-box, distant solo cello, subtle low drone. No percussion hits or jump-scare stingers. Structure: slow build over 16 bars then return to a quiet bed, 2 minutes 30 seconds, loop-safe. Leave the midrange free for ambient SFX. Avoid: distorted guitars, loud brass, rapid ostinatos, and melodies that sound like nursery rhymes.

Creative brief: main menu theme, 1 minute 30 seconds. Mood: nostalgic, inviting, a hint of mystery. Tempo about 95 BPM, A minor shifting to C major in the second half. Feature a memorable 4-bar melody on piano, answered by clarinet or flute, with warm strings underneath. Gentle build to a satisfying ending, then a clean finish (not a loop). Avoid: electronic synths, trap beats, epic cinematic hits.

Creative brief: a 4-second victory sting for a farming game quest completion. Bright, warm, satisfying. Key C major, 110 to 120 BPM feel, instruments: harp glissando, glockenspiel, soft strings. Single rising phrase ending on a clear tonic chord, quick decay. No percussion, no choir, no fanfare brass. It must not clash with the day loop in G major.

Creative brief: a 3-second gentle fail sting (not punishing) for when the player's crops wilt. Mood: soft disappointment. Instruments: single cello or low piano, descending minor third. No dissonant clusters, no loud hit. Quiet, ends on a sustained note that fades naturally.

I want to build adaptive music for the orchard day loop using layers. Suggest a plan for generating 3 compatible versions of the same piece: (1) base: piano and guitar only, (2) mid: base plus light strings and woodwind, (3) full: mid plus soft percussion. They must share tempo (85 BPM), key (G major) and length (2 minutes) so they can be cross-faded in the game engine. Tell me which settings to keep identical, what could cause drift between generations, and how to check alignment in a DAW. Do not promise stem export; tell me to check the tool's current export options.

Creative brief: a 2-minute town theme for a fictional rural village in a cosy game. Feeling: friendly market-day bustle. Tempo 100 to 110 BPM in 6/8 or 3/4 for a gentle lilt, major key. Instruments: accordion or hurdy-gurdy-like tone, fiddle, light hand percussion. Keep the idiom generic (invented village), not tied to a specific real culture or a named existing tune. Avoid: imitation of real folk songs, caricature, or anything that quotes known melodies.

Create a music spec table for a 2D cosy game with 6 tracks: menu, day, night, town, win sting, fail sting. Columns: filename, role, mood, tempo, key, length, loop yes/no, instruments, priority (1-3), where it plays. Use these constraints: all tracks must sit well with the day loop in G major; total budget of 12 minutes of music. Add notes on fade lengths in the engine ([ENGINE NAME]). Do not invent file formats; I will confirm the formats my tool exports.

Write a checklist of questions I must answer by reading the current licence and terms of an AI music generator before using its tracks in a commercial indie game on Steam and in a YouTube trailer. Cover: who owns the output, commercial use allowed on my plan, credit requirements, restrictions on stores or platforms, content ID or claim risks, use after cancelling my subscription, whether tracks can be registered with collecting societies, and changes in terms over time. Do not state what any specific tool allows; I will check each point myself and save a dated copy of the terms.

Context: I am working with a legacy Python codebase using a monolithic structure.
Task: Refactor the following function into a modular service class. 
Requirements: 
1. Implement Type Hinting. 
2. Ensure PEP 8 compliance. 
3. Add a decorator for logging execution time. 
4. Include unit tests using the Pytest framework.
Code: [Insert Code Block]

Role: Senior Research Analyst
Context: Reviewing recent literature surrounding transformer model optimization, quantization, and edge deployment performance.
Task: Synthesize the key findings, methodologies, performance trade-offs, and research gaps from the provided abstracts/text.
Constraints: Maintain strict academic rigor. Clearly distinguish between empirical evidence and authors' hypotheses.
Output Format: Structured research brief containing: Executive Summary, Key Methodologies, Performance Comparative Analysis, and Open Questions.

Role: Technical SEO Director
Context: We are targeting the seed keyword domain "ChatGPT prompts" to build an authoritative content hub.
Task: Generate a comprehensive semantic keyword cluster table based on search volume intent patterns (Informational, Commercial, Transactional).
Constraints: Group long-tail variations, identify content gaps, propose primary target titles, and specify internal linking structures.
Output Format: Markdown table with the following columns: [Target Keyword | Search Intent | Recommended Article Title | Target H2 Headers | Internal Link Target].

Act as an experienced debate judge. After hearing the following brief summary of an affirmative case for "Resolved: Universal healthcare is a human right," provide constructive feedback on its clarity, persuasiveness, and potential areas for the negative to attack.

Summary: "Our case rests on the moral imperative that healthcare access should not be dictated by socioeconomic status. We will demonstrate how universal healthcare improves public health outcomes, reduces financial burdens on individuals, and fosters a more equitable society. Our evidence will highlight models from countries like Canada and the UK."

Role: Executive Brand Strategist
Context: Convert a dense 20-page industry whitepaper on corporate sustainability metrics into viral social media assets.
Task: Repurpose the core data points into 3 LinkedIn text posts, 1 Twitter/X thread (7 tweets), and 1 short-form video script.
Constraints: Avoid generic platitudes. Use data-driven hooks, short paragraphs, bold statements, and open-ended questions to drive comments.
Output Format: Group output clearly by platform with instructions for visual elements where appropriate.

Act as a debate coach. I need three current, controversial debate topics suitable for high school students, covering social, economic, and environmental issues.

Those are good, but I need topics with more nuance and potential for deep argumentation. Make sure they have clear affirmative and negative sides.

Act as a Senior Strategic Consultant with 20 years of experience in SaaS scaling. Analyze the provided quarterly report for [Company X]. Identify three potential market risks and five growth opportunities in the APAC region. Format the output as a SWOT analysis followed by an executive summary. Use a professional, data-driven tone. [Insert Data Here]

Role: Management Consultant (Ex-McKinsey)
Context: A mid-market fintech firm expanding operations into the Latin American cross-border payments sector.
Task: Conduct a rigorous PESTLE (Political, Economic, Social, Technological, Legal, Environmental) analysis, followed by an actionable SWOT matrix.
Constraints: Focus heavily on regional regulatory frameworks, currency volatility risks, local mobile penetration metrics, and compliance hurdles. Avoid high-level generalities.
Output Format: Executive Report format with bulleted strategic recommendations prioritizing risk mitigation.

ROLE: [Define expert identity and core function]
CONTEXT: [Provide situational awareness and active memory boundaries]
TOOLS: [List accessible API functions and tool specs]
OPERATIONAL PROTOCOL:
  1. ANALYZE: Evaluate input against memory.
  2. PLAN: Formulate multi-step action sequence.
  3. EXECUTE: Issue structured tool call.
  4. VERIFY: Parse observation; retry if failed.
  5. RESPOND: Return final output schema.
CONSTRAINTS: [List strict negative constraints and security rules]
OUTPUT FORMAT: [Specify JSON, XML, or Markdown schema]