Explore curated prompts

You are an AI platform architect. Design an explainable, testable, progressively deployable model-routing policy for the application below. Do not send every request to the largest model by default. Application and user scenarios: {application} Primary task classes and examples: {task examples} Candidate models and known capabilities: {model inventory} Context windows and tool support: {context and tools} Quality and safety thresholds: {quality thresholds} Latency objectives: {latency} Cost budget and billing units: {cost} Privacy, data-residency, and compliance requirements: {privacy and compliance} Availability, concurrency, and rate-limit information: {runtime constraints} Allowed telemetry and feedback signals: {telemetry} First audit every time-sensitive input. If model price, regional availability, rate limits, context size, or capability lacks a dated source, label it "verification required" rather than treating it as current fact. Then return: 1. A task-classification table defining complexity, context, tools, privacy, accuracy, latency, and cost needs for each class, with positive examples and confusing counterexamples. 2. A routing decision table that filters models by hard constraints before ranking eligible options by quality, latency, and cost. Explain every rule; do not substitute brand reputation or one benchmark for task evidence. 3. Escalation and degradation rules covering when to move up from a small model, when to fall back to a compatible model, and how to handle timeout, rate limit, empty response, tool failure, and low confidence. Never silently weaken safety or privacy to stay online. 4. Budget controls for request, session, and daily limits, including what the system returns when a limit is reached, which tasks may continue after user confirmation, and which must stop. 5. An evaluation set with representative cases, expected behavior, scoring rubric, maximum latency, and cost-recording fields for every task class. Include multilingual, long-context, and failure-injection cases. 6. A rollout plan covering offline replay, shadow routing, limited traffic, rollback thresholds, and monitoring. Do not change production configuration directly. Finish with machine-readable pseudoconfiguration and a short team-facing decision note. Distinguish conclusions supported by supplied data from assumptions that require measurement.

You are a context architecture auditor. Review the AI or agent context below and propose a reversible simplification without changing the product goal or its safety boundaries. Product and task: {product and task} Current system prompt: {system prompt} Project-level rules: {project rules} Tool and interface descriptions: {tool descriptions} Skills or knowledge modules: {skill modules} Memory and history summaries: {memory} Known failure cases: {failures} Compliance constraints that must remain: {compliance constraints} Available regression tests: {tests} Work in this order: 1. Build an inventory. Classify every instruction as identity and goal, permanent safety boundary, task rule, tool contract, project knowledge, example, historical memory, or temporary state. Record where it currently lives. 2. Find conflicts and waste. Identify duplication, contradictions, excessive specificity, facts directly discoverable from code, stale guidance, and material that should not load by default. Never delete something merely because it is long. 3. Design layers. Keep only identity, goals, permissions, and non-negotiable boundaries in the core. Put tool behavior in the relevant interface description, project knowledge in project rules, long procedures in on-demand skills, and examples, files, or rubrics behind explicit references. Store short-lived facts as dated, sourced memory. 4. Rewrite interfaces. For every on-demand module define its trigger, inputs, outputs, stop condition, fallback, and human escalation point. Preserve provenance when referencing real files or data, and do not copy secrets, personal data, or unrelated private material. 5. Assess removal risk. Give every proposed change an expected benefit, possible loss, evidence strength, and recovery method. Mark assumptions as unverified when failure evidence or tests are missing. 6. Plan regression tests. Cover correctness, tool selection, constraint adherence, conflicts, long tasks, unknown inputs, and high-risk actions. Define the baseline, comparison version, pass threshold, and rollback condition. Return a current-state map, issue table, target layered architecture, itemized migration list, revised core-prompt draft, module interface drafts, regression matrix, and phased rollout plan. Do not delete or overwrite the current configuration. Present a diff and backup approach first, and keep human gates around production, permissions, or external actions.

You are a multimodal video director. Turn the following idea into structured production instructions for an AI video tool: Creative concept and goal: {concept} Duration: {duration} Available image, video, and audio assets: {assets} Aspect ratio and publishing platform: {format and platform} Brand, copy, and other constraints: {constraints} First assign one explicit job to every asset, such as subject consistency, opening frame, camera movement, pacing, palette, or audio mood. Do not leave the model to guess what an asset is for. Then create a time-coded shot plan. For each segment specify what happens, composition, shot size, camera movement, subject action, transition, sound or beat behavior, and on-screen text. Finish with: 1. Consistency rules for people, products, scenes, and brand details; 2. Visual errors and irrelevant elements to avoid; 3. Checks for spelling, logos, safe areas, and accessibility; 4. One final prompt that can be copied directly. When using references, extract specific technical attributes instead of reproducing protected characters, logos, or the distinctive style of a living creator without permission. If critical details are missing, ask no more than three questions while still providing the best draft possible from the available information.

Act as an animation pre-production director. Plan {an original or authorized story concept} as an animated short lasting {duration}, using {aspect ratio}, for {audience and platform}. Use only fictional, public-domain, or explicitly authorized characters and references. Do not replicate a real person's identity or imitate the recognizable style of a living creator. Additional inputs: {lead character and goal}, {world setting}, {central conflict}, {emotional arc}, {visual attributes}, {permitted references}, and {video-model capabilities and limits}. Work in this order: 1. Build a character continuity sheet. For every character, define silhouette, wardrobe, palette, key props, movement habits, starting emotion, and features that must not change. Mark missing information as Needs confirmation instead of filling it with a famous character or real person. 2. Establish story rules. State the theme in one sentence, then define location, time, spatial relationships, key-light direction, prop counts, and three rules the world must not break. 3. Design six to ten key beats. For each beat, provide its purpose, visible action, emotional change, shot size, camera movement, transition, and continuity risk. The durations must add up to the target runtime. 4. Choose three to five keyframes. Specify composition, character position, eyelines, light, foreground/midground/background, and the elements preserved from the previous frame. Do not generate images; return review-ready keyframe specifications. 5. Write one complete prompt ready for the video model, including timecodes, visible action, camera language, sound cues, transitions, and global continuity anchors. If the model cannot handle multiple shots, rewrite it as a single-shot version and explain the tradeoff. 6. Finish with a continuity checklist covering identity, wardrobe, props, space, light, action causality, shot duration, and final state. Avoid real-person face replacement, unauthorized character replication, sexualization of minors, glamorized dangerous behavior, sudden wardrobe changes, face drift, extra limbs, changing prop counts, spatial jumps, impossible camera moves, gibberish, logos, and watermarks. Return: assumptions and gaps, character continuity sheet, story rules, beat table, keyframe specifications, complete video prompt, and continuity checklist.

Act as my head of content. Design a 30-day content operating plan for [brand or product], optimized for [business objective] on [primary platforms] and aimed at [target audience]. Do not generate the calendar immediately. First ask no more than eight questions about product differentiation, audience pain, existing trust assets, conversion path, production resources, available time, brand voice, and compliance boundaries. If I cannot answer, state conservative assumptions and label them. After diagnosis, deliver: 1. Strategic spine: one positioning statement and three content pillars, each tied to an audience problem and business goal. 2. Audience journey: content needs and next actions across discover, understand, trust, and act stages. 3. Thirty-day calendar: topic, platform, format, opening hook, core point, evidence or example, call to action, and repurposing route for each day. 4. Production system: roles, inputs, definition of done, and deadlines for ideation, research, drafting, review, publishing, and retrospective. 5. Measurement plan: weekly leading and outcome indicators plus stop, continue, or scale rules without false precision. 6. Retrospective template: winning content, failed assumptions, audience signals, and next-week experiments. Constraints: avoid generic motivation and unverified promises; rewrite ideas for each platform instead of copying them mechanically; schedule at least one weekly user-question or real-case validation.

Act as a video creative director and technical producer. Plan a [duration] video about [topic] for [audience] on [platform], optimized for [desired viewer action or feeling]. First confirm available footage, brand rules, aspect ratio, narration language, caption requirements, production tools, and deadline. Then deliver: 1. Creative concept: one core proposition, emotional arc, visual motif, and clichés to avoid. 2. Timeline: time-coded purpose, visuals, narration or on-screen text, sound, and transition for every segment. 3. Shot list: framing, camera position, movement, subject action, lighting, duration, and continuity logic. 4. Production routing: identify shots best handled by code-driven motion, existing-footage editing, generative video, or animated stills, with reasons. 5. Asset list: required images, footage, fonts, icons, music, sound effects, and license checks. 6. Implementation plan: component or scene names, render order, review milestones, and fallback paths. 7. Quality checklist: pacing, caption readability, loudness, brand consistency, visual continuity, copyright, and platform safe areas. Finish with a minimum viable version and an enhanced version, clearly comparing cost and quality. Never invent available assets, licenses, or tool capabilities.

You are a brand visual production lead. Plan a complete workflow from strategy to deliverable assets using the brief below. Tool names are replaceable options; define the problem and acceptance criteria for each stage first. Brand and product: {brand and product} Audience and use situations: {audience situations} Project goal: {goal} Required assets and placements: {assets and placements} Existing brand guidelines: {brand guidelines} Available copy, images, data, and rights: {materials and rights} Team and tools: {team and tools} Time, budget, and technical limits: {limits} Release channels and date: {release information} Return these stages: 1. Brief validation. Confirm the core message, audience, tone, required and prohibited elements, dimensions, languages, accessibility needs, and success criteria. List missing information instead of inventing positioning or product facts. 2. Research and direction. Gather authorized competitive, cultural, and visual references. Extract observable attributes such as composition, palette, typography, texture, and information hierarchy. Do not copy trademarks, packaging, characters, or a living creator's distinctive style. 3. Concept system. Propose two or three directions with a narrative, mood-board attributes, palette, type categories, grid, image strategy, suitable placements, risks, and rejection criteria. Obtain direction approval before batch production. 4. Asset production. Define inputs, output formats, resolution, color space, naming, version, and owner for images, vectors, icons, typography, product mockups, presentations, and social layouts. For generated assets, retain the model, date, prompt summary, source-material rights, and human-edit record. 5. Editing and adaptation. Plan cropping, background removal, retouching, extension, copy review, multilingual layout, and size variants. Never alter a real person's identity, product appearance, or legally required copy without authorization. 6. Quality gates. Check brand consistency, readability, contrast, keyboard or screen-reader needs, alt text, copyright and trademarks, factual claims, file size, bleed, and export settings. Route every failure back to a named production stage. 7. Release and archive. Define approvers, final files, source files, font and asset licenses, change log, rollback version, channel upload checks, and a post-release review date. Never claim a file was generated, uploaded, or published unless that action was verified. Return a stage flow, responsibility matrix, asset register, concept directions, file and metadata specification, tool-handoff contracts, quality checklist, and approval and rollback plan. If the environment can create files, still present verifiable outputs at each required approval gate.

You are a cautious content-market researcher. Evaluate whether the niche below deserves a small test without promising success or revenue. Platform: {platform} Target language and region: {market} Niche: {niche} Available data sources: {sources} Production cost and capabilities: {cost and capabilities} Test window: {window} Use only public or authorized data in ways allowed by platform terms. Do not bypass authentication, rate limits, or access controls. Attach a source, observation time, and definition to every number. Mark unavailable data as unknown instead of presenting an estimate as fact. Apply four gates in order: 1. New entrants: find recently created channels with verifiable views or engagement and assess whether new accounts still receive distribution. 2. Consistency: compare the latest five items with the five strongest historical items for each candidate. Calculate medians, maxima, and outlier concentration so one viral result does not represent the whole niche. 3. Economics: gather reliable sources and ranges for advertising, sponsorship, or product yield. Model scenarios alongside production cost and never treat third-party estimates as actual revenue. 4. Recent momentum: compare the latest 48 hours, or the shortest consistently available window, to determine whether momentum is current. Label seasonality and sample-size limits. Return a candidate table, evidence links, calculation method, pass or reject reasons, unknowns, risks, and one seven-day minimum test. Recommend only one direction to test first, with success signals, kill criteria, and the next review date.