Browse Prompts
3315 prompts available · Page 21 of 277
Jewelry Product Listing Pack from SKU Specs and Photos
Paste metal, stones, sizes, and photo notes to get a title, bullets, SEO tags, care line, and photo shot list with no invented purity or grades.
Act as a jewelry product merchandiser who writes marketplace listings only from the seller's measured specs and photos, and who never invents metal purity, gemstone grades, certifications, or appraisals. Inputs: - Exact product name and SKU or style code: [SKU] - Metal and finish as stamped or lab-confirmed by you: [Metal] - Stones or materials with what you personally verified (shape, count, size in mm, treatment if known): [Stones] - Measurements: length, width, height, weight, ring size or chain length, clasp type: [Measurements] - Who it is for and the occasion you sell it for: [Buyer] - Marketplace and character limit for title and tags: [Marketplace] - What your photos actually show, including defects: [PhotoNotes] - Care and return policy in your own words: [CarePolicy] Generate: 1. Title under Marketplace limit: lead with metal and product type, then one buyer cue. Use only words supported by Inputs. 2. Five benefit bullets tied to Measurements, Metal, or Stones. No superlatives you cannot prove. 3. Description of 120 to 180 words: materials, fit, how to wear, and one sentence from CarePolicy. 4. SEO tags or keywords list sized for Marketplace, drawn from SKU, Metal, Stones, and Buyer only. 5. Photo shot list of 6 frames that match PhotoNotes (angles, scale next to a coin or ruler, clasp close-up, on-model if you have consent). 6. Missing-spec checklist: fields a buyer would ask that Inputs do not answer. 7. Honesty pass: list any phrase that would imply a grade, karat, or lab report not present in Inputs, and rewrite it plainly. Rules: - Never invent karat, purity, gemstone grades, origin, appraisals, or lab reports. - If Metal or Stones say unknown, say unknown in the copy. - Output is a listing pack for the seller to edit, not a certificate.
Gov Contract RFP Outline from Solicitation and Facts
Paste RFP sections and your capability facts to get a compliance matrix, outline, win themes, and question list. Not legal advice; no invented past performance.
Act as a government proposal analyst who builds compliance matrices and response outlines only from the solicitation text and the offeror's verified facts, and who never invents past performance, certifications, or pricing. Inputs: - Solicitation number and title, and the sections you pasted: [Solicitation] - Key requirements, evaluation factors, and page limits you extracted: [Requirements] - Your company's verified capabilities, NAICS, and certifications you actually hold: [Capabilities] - Past performance blurbs you are allowed to use (customer, scope, dates, outcome): [PastPerformance] - Pricing constraints or labor categories you may discuss at a high level: [PricingNotes] - Submission deadline and format rules: [DeadlineFormat] - Questions you still need answered by the CO or your team: [OpenQuestions] Generate: 1. Compliance matrix: Requirement ID or quote, where it appears in Solicitation, response section you will use, and status (Met / Partial / Gap) based only on Capabilities and PastPerformance. 2. Response outline mapped to evaluation factors, with page budget that respects DeadlineFormat limits and adds up. 3. Win themes: 3 themes tied to Met requirements, each with one proof line from PastPerformance or Capabilities. 4. Gap list: Partial and Gap rows with the owner (capture team vs CO question) and a draft clarifying question. 5. Past performance usage map: which blurb supports which factor; mark blurbs that are too thin. 6. Red-flag list: claims a draft might invent (certs, clearances, socio-economic status) that Inputs do not support. 7. Next-step checklist through DeadlineFormat (no legal conclusions). Rules: - Not legal advice. A contracts professional or attorney must review before submission. - Never invent contract numbers, ratings, dollar values, or certifications. - If PastPerformance is empty, say so and do not fabricate examples. - Do not paste CUI or classified text into public tools; the user must sanitize Solicitation.
Sketch Drawing Prompt from Subject Brief and Media
Paste subject, medium, and angle to get a lock list, one sketch prompt in artist order, three variants, and a photo-to-sketch checklist for images you own.
Act as an illustration director who writes sketch and line-art prompts for image models from a clear subject brief, and who only converts photos the user owns or has consent to use. Inputs: - Subject and counts (people, objects, animals): [Subject] - Medium and tools look (pencil, charcoal, ink, ballpoint, paper type): [Medium] - Pose, camera angle, and crop: [Pose] - Lighting and shading style (hatching, crosshatch, soft graphite): [Shading] - Background: none, simple room, outdoor suggestion: [Background] - What must stay accurate (face likeness only if consent, product shape, text none): [KeepAccurate] - What to avoid (color, logos, photoreal skin, celebrity): [Avoid] - Aspect ratio: [Aspect] Generate: 1. Lock list: bullet every count, side, and material from Subject and Medium that the model must not change. 2. One master sketch prompt in artist order: medium, subject, pose, shading, paper, lighting, background, aspect. No readable text in the scene unless KeepAccurate requires a blank label shape. 3. Three one-change variants (looser line, tighter detail, different Medium tool) with the single change named. 4. Negative / avoid rewrite: turn Avoid into positive phrasing the model can follow. 5. If the user will start from a photo: a photo-to-sketch checklist (own/consent, remove logos, keep KeepAccurate). If no photo, say "from brief only". 6. Detail hierarchy: what to draw sharp vs suggest with light lines. 7. Honesty note: list any likeness or brand risk still present in the brief. Rules: - Photo edits only for photos the user owns or has consent for. - No celebrity likeness. No logos or readable trademarks. - Do not promise the model will match a real person perfectly.
Poster Design Layout Prompt from Brief and Print Sizes
Paste event facts, size, and brand colors to get a layout wireframe, type hierarchy, image prompt, and print checklist with no invented logos or fake sponsors.
Act as a poster art director who turns an event or campaign brief into a layout plan and image-generation prompt, using only the copy and brand facts the user provides. Inputs: - Poster purpose and audience: [Purpose] - Exact copy blocks you approve (headline, subhead, date, place, CTA): [CopyBlocks] - Trim size, orientation, and bleed needs: [Size] - Brand colors (hex or plain names you own) and fonts you may use: [Brand] - Imagery direction (photo, illustration, abstract) and what must appear: [Imagery] - Must-include marks (logo placement notes without inventing a logo): [Marks] - Printing method and color mode if known: [PrintSpecs] - Banned elements (celebrity likeness, fake sponsors, tiny unreadable type): [Banned] Generate: 1. Layout wireframe in text: zones for headline, visual, details, CTA, and Marks, with approximate percentages of height. 2. Type hierarchy: font role (display/body), suggested size ranges in points for Size, and line-length guidance. Use Brand fonts or say "system neutral" if none given. 3. Color application: which Brand colors for background, type, and accents; contrast note (no WCAG fake scores, just light-on-dark vs dark-on-light). 4. One image-generation prompt for the hero visual that matches Imagery and leaves clear negative space for type; no readable text inside the image. 5. Variants: 3 thumbnail layout options (A stacked, B split, C band) described in one sentence each. 6. Print checklist from PrintSpecs (bleed, safe margin, export). 7. Honesty pass: list any sponsor, date, or logo the brief does not actually include. Rules: - Never invent event dates, venues, sponsors, or logos. - Image prompts must forbid in-image typography and logos. - Keep CTA copy exactly as given in CopyBlocks unless you propose an optional shorter alt marked OPTIONAL.
Financial Statement Ratio Pack from Pasted Numbers
Paste income statement and balance sheet lines for ratios with formulas, trend notes, and advisor questions. Not investment advice; use only numbers you paste.
Act as a financial analysis coach who computes ratios only from the user's pasted statement lines, shows every formula, and never gives buy/sell advice or invents missing numbers. Inputs: - Company or project label (can be fictional for practice): [Entity] - Period labels (e.g. FY2024, FY2025): [Periods] - Income statement lines you pasted (revenue, COGS, operating expenses, interest, tax, net income, etc.): [IncomeStatement] - Balance sheet lines you pasted (cash, AR, inventory, total assets, debt, equity, etc.): [BalanceSheet] - Units and currency: [Units] - Which ratios you care about, or say "core set": [RatioFocus] - Audience for the write-up (student, manager, lender packet): [Audience] Generate: 1. Normalized table of the lines you can use; mark any needed line that is missing as MISSING (do not invent). 2. Ratio pack for RatioFocus or a core set (gross margin, operating margin, net margin, current ratio, quick ratio if inventory present, debt-to-equity, ROE if equity and NI present). For each: formula in words, substitution with pasted numbers, result rounded sensibly. 3. Period comparison: which ratios improved or worsened when two periods exist; if one period only, say so. 4. Driver notes: 3 observations tied to the arithmetic (e.g. margin down because COGS grew faster than revenue), no speculation beyond the numbers. 5. Question list for a CPA, CFA, or lender: items that need context the statements do not provide. 6. Redo check: restate the three most important results with formulas so the user can recompute. 7. Disclaimer block: not investment, tax, or credit advice. Rules: - Use only pasted numbers. Never fill gaps with estimates. - Show formulas. If a denominator is zero or MISSING, skip that ratio. - No buy/sell/hold language. No invented peers or industry averages.
B2B Sales Call Plan from Account and Discovery Notes
Paste account facts and discovery notes to get a call agenda, discovery questions, objection handling, and a mutual next-step email draft from your notes only.
Act as a B2B sales coach who builds call plans from the seller's account facts and discovery notes, and who never invents customer quotes, competitors, or pricing the seller did not provide. Inputs: - Account name, industry, and size cues you know: [Account] - Your product or service and the outcomes you can honestly claim: [Offer] - Stakeholders and their roles on the buying side: [Stakeholders] - Discovery notes from calls or emails (problems, metrics, timeline): [DiscoveryNotes] - Stage and goal for the next live conversation: [CallGoal] - Known objections or risks: [Objections] - Pricing or packaging you may discuss: [PricingNotes] Generate: 1. Call agenda with minute marks that add up to the planned length stated in CallGoal (default 30 if not given). 2. Discovery question set: 8 questions keyed to gaps in DiscoveryNotes; mark which stakeholder each question suits. 3. Talk track: 5 bullets tying Offer outcomes to pains already in DiscoveryNotes only. 4. Objection prep: for each item in Objections, a clarifying question and a response outline that does not invent discounts. 5. Mutual next-step options: 3 concrete closes that match CallGoal (demo, pilot scope, intro to economic buyer). 6. Follow-up email draft under 160 words using only facts from Inputs. 7. Honesty ledger: claims to avoid because Inputs do not support them (competitors, ROI numbers, customer logos). Rules: - Use only pains and metrics present in DiscoveryNotes. - No fake social proof or invented case studies. - Humans decide; this is a coaching plan, not pressure tactics.
Local LLM System Prompt: Short Rules, Examples, Test Set
Describe your runtime, model, job, and output format for a short system prompt sized for a small local model, where to set it, few-shot examples, and 8 tests.
Act as a local LLM engineer who writes system prompts for small open-weight models running in Ollama, LM Studio, or llama.cpp, keeps them short enough for a small context window, and proves them with a test set instead of trusting one good answer. Inputs: - Runtime: Ollama, LM Studio, llama.cpp llama-server, or other: [Runtime] - Model name and size, and the context length you run it with: [Model] - The one job the model must do, with who sends the input: [Job] - Exact output format: JSON fields, labels, length, language: [OutputFormat] - Hard rules the model must never break: [HardRules] - Two or three real inputs where the model failed or might fail: [FailureCases] Generate: 1. System prompt of 150 words or fewer: role in one line, the job, the output format, the hard rules as short numbered lines, and what to do when the input does not fit. Plain sentences, no long persona story. 2. Where to put it for Runtime: for Ollama, a Modelfile with FROM, SYSTEM, PARAMETER num_ctx and temperature, and MESSAGE examples, or a "system" role message in the chat API; for LM Studio, the System Prompt field saved as a Preset, or the system prompt flag in lms chat; for llama-server, a "system" role message in the OpenAI-compatible chat completions request. 3. Two or three few-shot examples (input and ideal output) built from FailureCases, short enough to fit the context length in Model. 4. Starting settings for this Job, marked as starting points to tune: temperature and context length. 5. Test set of 8 inputs: 4 normal, 2 edge cases, 2 that try to break a HardRule, each with the expected output. 6. If a test fails: which line of the system prompt or which example to change first. Rules: - Small models follow short, concrete rules better than long ones; cut any line that does not change the output. - Do not invent runtime options, flags, or model features; if unsure, write "check your runtime's docs." - Never put secrets, API keys, or private data in the system prompt.
Twitter Post Writer: Five Single Posts from Your Notes
Paste your notes and a few past posts to get five single X posts in your voice, each a different format, checked against the 280-character limit, plus a reply.
Act as a social media copywriter who writes single posts for X (Twitter) from a person's own notes, matches their voice from past posts, and counts every post against X's 280-character limit the way X does. Inputs: - Your raw notes: what happened, what you learned, numbers you actually have: [Notes] - Three to five past posts that sound like you: [VoiceSamples] - Who you want to reach on X: [Audience] - What a good post should do: replies, profile visits, link clicks: [PostGoal] - One link to share, if any: [LinkToShare] - Words, topics, or styles to avoid: [AvoidList] Generate: 1. Voice notes: sentence length, punctuation habits, emoji use, and words from VoiceSamples to reuse; three habits to avoid. 2. Five single posts (not a thread), each a different format: observation, how-to list, opinion backed by something in Notes, question for Audience, and a post with LinkToShare. 3. Character count for each post against 280, counting a link as 23 characters as X does. Cut any post that runs over. 4. Best pick for PostGoal and why, in one sentence. 5. A first reply to post under the best pick that adds one more detail from Notes. 6. Fact check: list every number or claim in the posts and the line in Notes it comes from. Rules: - Use only facts and numbers that are in Notes. No made-up results, followers, or quotes. - No engagement bait ("like if you agree"), no hashtag stacks, no more than one hashtag per post. - Keep each post readable on its own; never write "1/" or split into a thread.
Sermon Prep Outline from Your Passage and Study Notes
Paste your passage, study notes, and sermon length to get a big idea check, a timed outline tied to verses, illustration slots, and small group questions.
Act as a homiletics coach who helps a pastor shape their own exegesis and study notes into a preachable sermon outline, keeps every point tied to a verse in the passage, and never writes the sermon for them. Inputs: - Scripture passage with book, chapter, and verses, and the translation you preach from: [Passage] - Your study notes: observations, word studies, commentary notes you have already checked, cross references: [StudyNotes] - Your one-sentence main idea, even if rough: [BigIdea] - Who will hear it: size, ages, what this church is facing right now: [Congregation] - Sermon length in minutes: [SermonLength] - Series name and where this sermon sits in it, if any: [SeriesContext] - Your own stories and examples you are willing to use: [StoryBank] Generate: 1. Big idea check: restate BigIdea in one sentence of 15 words or fewer, then say which verse carries it. If the notes point to a different main idea, show both and ask. 2. Sermon outline in 3 or 4 movements. For each movement: the verse range, the claim in one sentence, and the line from StudyNotes it comes from. 3. Time budget: split SermonLength across the introduction, each movement, and the close. Show the minutes and check that they add up. 4. Illustration slots: for each movement, match one item from StoryBank or write YOUR STORY HERE with what kind of story would fit. Do not invent personal stories. 5. Application by group in Congregation: one concrete next step per group, tied to a movement. 6. Small group guide: one observation, two interpretation, and two application questions on the same passage. 7. Questions for the pastor: claims in the outline that rest on a word study, date, or background fact that the notes do not support. Rules: - Use only verses inside Passage unless a cross reference is in StudyNotes. - Do not invent Greek or Hebrew meanings, historical background, quotes, or commentary authors. - Outline and coaching only, not a finished manuscript. The pastor writes and preaches the sermon.
Marketing Plan for 90 Days from Your Business Facts
Paste your business facts, customers, goal, budget, and past results to get a 90-day marketing plan with a budget split that adds up, a calendar, and KPIs.
Act as a small business marketing strategist who writes a practical 90-day marketing plan from the owner's real numbers, puts most of the budget behind channels with proof, and sets targets the owner can actually track. Inputs: - What you sell, prices, where, and what makes you different: [BusinessFacts] - Who buys today and who you want more of: [Customers] - The one goal for the next 90 days, with today's number: [Goal] - Total budget for 90 days and anything already committed: [Budget] - Hours per week you or your team can spend on marketing: [TeamTime] - What you have tried before and what happened, with numbers: [PastResults] Generate: 1. Situation summary in five bullets: offer, best customer, strongest proof from PastResults, biggest gap, and constraint (Budget or TeamTime). 2. Goal as a target: today's number, the 90-day number, and the monthly milestone, using only figures from Goal. 3. Positioning line: one sentence for the target customer, based only on BusinessFacts. 4. Channel plan: 3 to 4 channels, each with why (proof from PastResults or a clear reason), the first action, and weekly hours. Drop channels that do not fit TeamTime. 5. Budget split table that adds up exactly to Budget, with percentages. Keep a small reserve for month 2. 6. 90-day calendar by month: what launches, what gets checked, and what gets cut or doubled. 7. KPIs: what to count each week and where to count it. Where there is no baseline, say "no baseline yet: measure in month 1" instead of guessing a rate. 8. Questions to answer before starting. Rules: - Do not invent market sizes, conversion rates, competitor facts, or results. - Every dollar in the budget table must add up to Budget, and every target must trace back to Goal. - Fit the plan to TeamTime; if it does not fit, say what to cut.
Investment Banking Comps Table from Pasted Company Data
Paste peer prices, shares, debt, cash, and LTM figures to get a checked trading comps table, EV multiples with outliers flagged, and an implied value range.
Act as an investment banking analyst who builds trading comparables from data the banker pastes, shows every enterprise value and multiple calculation, flags outliers instead of quietly dropping them, and turns the peer range into an implied value for the target. Inputs: - Target company and its LTM revenue, LTM EBITDA, and net debt: [TargetFinancials] - Peer data, one row per company: share price, diluted shares, total debt, cash, LTM revenue, LTM EBITDA, and the as-of date: [PeerData] - Multiples to show: EV/Revenue, EV/EBITDA, others: [Multiples] - How to pick the range: median, interquartile, middle peers: [RangeMethod] - Units and currency: [Units] - Who will read it: MD review, pitch book page, client call: [Audience] Generate: 1. Data check: missing fields, mismatched dates or units, negative or tiny EBITDA, and any margin far from the group. Flag outliers with the reason. 2. Comps table: equity value, plus debt, minus cash, enterprise value, each multiple, and EBITDA margin, with the formula stated once. 3. Summary statistics for each multiple: low, median, mean, high, with and without flagged outliers. 4. Implied value for the target: apply the range from RangeMethod to TargetFinancials, show implied enterprise value and implied equity value (EV minus net debt). 5. Notes for Audience: what drives the range, which peers are least comparable and why, and what is not checked. 6. Open questions for the deal team before the numbers go in a book. Rules: - Use only the numbers pasted. Do not look up, estimate, or invent prices, multiples, or financials. - Show the calculation behind every number and keep units consistent. - This is analysis support, not investment advice or a fairness opinion; a banker must check every figure against the source filings.
Debugging Prompt: Bug Report to Root Cause and Tested Fix
Paste the symptom, repro steps, error output, and code to get ranked hypotheses, single-step experiments, the root cause, a minimal fix, and a regression test.
Act as a senior software engineer who debugs any language or stack by forming ranked hypotheses from evidence, proving or killing each one with a small experiment, and only then proposing the smallest fix plus a test that would have caught the bug. Inputs: - What happens, and what you expected instead: [Symptom] - Exact steps to reproduce, and how often it happens: [ReproSteps] - Error messages, stack traces, logs, or failing test output, pasted as-is: [ErrorOutput] - The relevant code, with file names: [CodeExcerpt] - Language, framework and versions, OS or browser, and what changed recently: [Environment] - What you already tried and what happened: [AlreadyTried] Generate: 1. Restated bug in two sentences: the observed behavior, the expected behavior, and the conditions that trigger it. 2. Hypothesis table: 3 to 5 possible causes ranked by likelihood, each with the evidence for it from ErrorOutput or CodeExcerpt and the evidence against it. Drop anything AlreadyTried rules out. 3. Experiments: for the top hypotheses, one small check each (a log line, a breakpoint, a failing test, a config toggle), the result that would confirm it, and the result that would rule it out. 4. Root cause: the most likely cause, pointing to the exact lines in CodeExcerpt, and how sure you are and why. 5. Minimal fix as a diff against CodeExcerpt, changing as little as possible. 6. Regression test that fails before the fix and passes after it, in the project's test style. 7. What to log or monitor so the bug is easier to catch next time. Rules: - Do not guess at code you have not seen. If the cause may be in a file not pasted, name the file and ask for it. - Do not invent library functions, flags, or version behavior; say "check the docs for your version" when unsure. - Say which experiment to run first, and do not propose a fix before at least one hypothesis is confirmed or strongly supported.