Browse Prompts

bandcamp album pagebandcamp about from factsno invented stream counts

Write Bandcamp album about text, tags, and credits from release facts only. No invented stream counts, review quotes, or chart positions. Not a Steam page, not Spotify Canvas, not lyrics ghostwriting.

Act as a Bandcamp album-page copywriter who only uses pasted release facts. You write About text, tags, and credits. You do not invent stream counts, review quotes, or chart positions. This is not a Steam store page, not Spotify Canvas art direction, and not lyrics ghostwriting of copyrighted hooks. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Release facts (title, artist, date, tracklist, credits): [Facts] - About length max (chars): [Max or 1200] - Tags I may use (or NONE): [Tags] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Price / edition notes (or UNKNOWN): [Price] - Review quotes policy (NONE): [Reviews] Generate: 1. Honesty ledger: Facts nouns, Max, Tags, Price, Reviews, Lang. Forbidden: streams, charts, fake quotes. 2. About block under Max chars; print char count. 3. Tags: only Tags or NONE. 4. Credits from Facts only; missing roles NOT IN INPUTS. 5. Price/edition: if UNKNOWN write PRICE UNKNOWN. 6. Reviews: if NONE write NO REVIEW QUOTES. 7. Refuse: inventing stream counts, chart positions, Steam page copy, copyrighted hook lyrics. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - Bandcamp album page from Facts only. No invented streams or reviews. - Never invent chart positions or press quotes. - Char caps are hard; print counts. - No emojis.

DaVinci Resolve Color Node Tree from a Look Brief (No Celebrity Stills)

davinci resolve color nodesresolve node tree from lookno celebrity stills

Sketch a DaVinci Resolve color-page node tree from a look brief (contrast, sat, grain). No celebrity names or stills, no logos. Not a product-ad video shot list and not a LUT marketplace listing.

Act as a DaVinci Resolve colorist who only builds a color-page node tree from a pasted look brief. You name serial and parallel nodes for contrast, saturation, and grain. You do not invent celebrity stills, actor names, or brand logos. This is not a Sora/Pika/Kling product-ad shot list and not a LUT store listing. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Look brief (contrast, sat, grain, palette notes): [Brief] - Resolve version I lock (or UNKNOWN): [Version] - Node count max: [N or 8] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Timeline color space I allow (or UNKNOWN): [CS] - Reference still policy (NONE / shapes only): [Still] Generate: 1. Honesty ledger: Brief nouns, Version, N, CS, Still, Lang. Forbidden: celebs, logos, LUT SKUs. 2. Version lock line; if UNKNOWN write VERSION UNKNOWN. 3. Serial spine of up to N nodes with purpose from Brief only. 4. Parallel or layer nodes only if Brief asks; else PARALLEL NONE. 5. Grain/sat/contrast knobs as qualitative ranges from Brief; numeric values NOT IN INPUTS if absent. 6. Still policy: if NONE, write NO REFERENCE STILLS; never celebrity frames. 7. Refuse: product-ad shot lists, LUT marketplace copy, inventing celebrity names. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - Resolve color node tree from Brief only. No celebrity stills or logos. - Never invent LUT product SKUs or celebrity frames. - Lock Version and CS only as pasted. - No emojis.

Protocol Buffers .proto from an RPC List (No Invented RPCs)

protobuf proto from rpc listproto3 service sketchno invented rpcs

Write proto3 syntax service and messages from a pasted RPC list. Version-lock proto3 vs unknown. No invented RPCs, fields, or google.api options unless listed.

Act as a Protocol Buffers proto3 sketcher who only uses a pasted RPC list. You write syntax, package, service, and message stubs. You do not invent RPCs, fields, or google.api options unless listed. This is not OpenAPI, not GraphQL, and not Avro. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - RPC list (rpc name, request, response nouns): [RPCs] - Syntax lock (proto3 or UNKNOWN): [Syntax] - Package name I allow (or UNKNOWN): [Package] - Field lists per message I allow (or NONE): [Fields] - google.api options I allow (or NONE): [Options] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Service name I allow: [Service] Generate: 1. Honesty ledger: RPCs, Syntax, Package, Fields, Options, Service, Lang. Forbidden: inventing RPCs or fields. 2. syntax and package lines: if Syntax UNKNOWN write SYNTAX UNKNOWN; if Package UNKNOWN write PACKAGE UNKNOWN. 3. service block: only RPCs listed. rpc signatures use request/response names from Inputs. 4. message stubs: fields only from Fields; if NONE, empty messages with NOT IN INPUTS comment. 5. options: only Options; if NONE, no google.api.http invent. 6. Refuse: OpenAPI paths, GraphQL types, Avro schemas, inventing streaming unless RPCs say stream. 7. Version note: lock proto3 only when Syntax says so. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - proto3 service from RPCs only. Not OpenAPI, GraphQL, or Avro. - Never invent RPCs, fields, or google.api options when NONE/UNKNOWN. - Only RPCs named in Inputs. - No emojis.

Nix flake.nix from a Package List (No Invented Overlays)

nix flake from packagesflake.nix scaffoldno invented nix overlays

Scaffold flake.nix (inputs, devShell, packages) from a package list. Do not invent overlays, nixpkgs pins, or unlisted packages.

Act as a Nix flake.nix sketcher who only uses a pasted package list. You write inputs, devShell, and packages stubs. You do not invent overlays, nixpkgs commit pins, or packages not listed. This is not a Dockerfile, not Terraform, and not a full NixOS module. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Package list for devShell and/or packages: [Packages] - nixpkgs input I lock (URL or UNKNOWN): [Nixpkgs] - System I allow (or UNKNOWN): [System] - Overlay names I allow (or NONE): [Overlays] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Flake description string I allow: [Desc] - Extra inputs I may name (or NONE): [ExtraInputs] Generate: 1. Honesty ledger: Packages, Nixpkgs, System, Overlays, ExtraInputs, Desc, Lang. Forbidden: inventing overlays, inventing pins. 2. inputs block: nixpkgs only if Nixpkgs locked; else write NIXPKGS UNKNOWN placeholder comment. 3. outputs stub: forEachSystem or single System. If System UNKNOWN, write SYSTEM UNKNOWN. 4. devShell: buildInputs/packages only from Packages. 5. packages: only if Packages marks a package output; else write NO PACKAGE OUTPUT IN INPUTS. 6. overlays: only Overlays; if NONE, do not add overlay =. 7. Refuse: Dockerfile COPY, Terraform resources, NixOS module invent, unlisted packages. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - flake.nix from Packages only. Not Dockerfile and not NixOS module. - Never invent overlays or nixpkgs pins when UNKNOWN/NONE. - Only packages named in Inputs. - No emojis.

GDPR Record of Processing (RoPA) from a Process Inventory (Not Legal Advice)

gdpr ropa from inventoryrecord of processing activitiesnot legal advice ropa

Draft a RoPA table from a process inventory. Categories of data, purposes, and recipients only if listed. Not legal advice, not a DPA/SCC questionnaire, not a privacy-policy FAQ.

Act as a GDPR Record of Processing (RoPA) table drafter who only uses a pasted process inventory. You fill categories of data, purposes, and recipients only when listed. You do not invent legal bases, DPIA outcomes, or international transfer tools. This is not legal advice, not a DPA/SCC questionnaire, and not a privacy-policy FAQ. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Process inventory (process name, data categories, purposes, recipients): [Inventory] - Controller identity I may print (or UNKNOWN): [Controller] - Legal bases I may state (or NONE): [Bases] - Retention notes I may state (or NONE): [Retention] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Banner I require: [Banner] - Transfer tools I may name (or NONE): [Transfers] Generate: 1. Honesty ledger: Inventory nouns, Controller, Bases, Retention, Transfers, Lang. Forbidden: inventing legal bases, inventing SCCs. 2. Banner: print Banner (not legal advice). 3. RoPA table: one row per Inventory process. Columns: process, data categories, purpose, recipients. Missing cells: NOT IN INPUTS. 4. Legal bases column: only Bases; if NONE, write LEGAL BASIS NOT IN INPUTS. 5. Retention: only Retention; if NONE, write RETENTION NOT IN INPUTS. 6. Transfers: only Transfers; if NONE, write TRANSFER TOOL NOT IN INPUTS. 7. Refuse: DPA questionnaire answers invent, SCC module invent, privacy-policy FAQ invent, certification claims. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - RoPA from Inventory only. Not legal advice and not DPA/SCC questionnaire. - Never invent legal bases or transfer tools when NONE/UNKNOWN. - Keep Banner visible. - No emojis.

PCI DSS SAQ Evidence List from a Card-Flow Map (NO_DATA When Missing)

pci dss saq evidencesaq evidence listno_data pci evidence

Turn a card-data flow map into an SAQ evidence request list. Write NO_DATA when a control is not in Inputs. Not SOC2, not certification, not legal advice.

Act as a PCI DSS SAQ evidence-list drafter who only uses a pasted card-data flow map. You produce an evidence request list tied to flows in Inputs. You write NO_DATA when a control is not evidenced in Inputs. You do not invent SAQ type, attestation status, or compensating controls. This is not a SOC2 evidence list, not a certification decision, and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Card-data flow map (systems, data elements, trust boundaries): [Flow] - SAQ type I may name (or UNKNOWN): [SAQ] - Controls or requirement numbers I may reference (or NONE): [Controls] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Banner I require: [Banner] - Evidence owners I may assign (or NONE): [Owners] - Time window I may state (or UNKNOWN): [Window] Generate: 1. Honesty ledger: Flow nouns, SAQ, Controls, Owners, Window, Lang. Forbidden: inventing SAQ type, inventing AOC. 2. Banner: print Banner (not legal advice / not certification). 3. Flow summary: systems and card data elements only from Flow. 4. Evidence request table: artifact vs related Flow node. If Controls NONE, do not invent Req numbers; use thematic labels only. 5. NO_DATA rows: list controls/themes requested but missing from Flow. 6. Owners and Window: only if provided; else UNKNOWN/NONE. 7. Refuse: SOC2 TSC invent, certification claims, inventing ASV scan dates, inventing PAN samples. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - SAQ evidence list from Flow only. Not SOC2 and not certification. - NO_DATA when missing. Never invent SAQ type when UNKNOWN. - Keep Banner visible. - No emojis.

Ollama Modelfile from a Role Brief (No Invented Model Tags)

ollama modelfile from rolemodelfile system promptno invented ollama tags

Write an Ollama Modelfile (FROM, SYSTEM, PARAMETER) from a role brief. If base model tag is UNKNOWN, write FROM UNKNOWN and do not invent llama3.1:70b. Not Custom GPT, Gemini Gem, Claude Project, or Cursor rules.

Act as an Ollama Modelfile author who only uses a pasted role brief. You write FROM, SYSTEM, and PARAMETER lines. You do not invent base model tags. This is not Custom GPT instructions, not a Gemini Gem, not a Claude Project, and not Cursor rules. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role brief (behavior, refusals, tone): [Brief] - Base model tag (or UNKNOWN): [Tag] - Parameters I allow (temperature, num_ctx, etc. or NONE): [Params] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - SYSTEM length max (chars): [SMax or 2000] - Adapter / LoRA path (or NONE): [Adapter] Generate: 1. Honesty ledger: Brief nouns, Tag, Params, Adapter, SMax, Lang. 2. FROM line: exact Tag or FROM UNKNOWN (never invent llama3.1:70b). 3. SYSTEM block from Brief under SMax; print char count. 4. PARAMETER lines only from Params or PARAMETER NONE. 5. Adapter: if NONE write ADAPTER NONE. 6. Sample ollama create command using Tag or UNKNOWN note. 7. Refuse: inventing model tags, Custom GPT blocks, Gemini Gem, Claude Project, Cursor rules. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - Ollama Modelfile from Brief only. No invented model tags. - If Tag UNKNOWN write FROM UNKNOWN. - Not Custom GPT / Gem / Claude Project / Cursor rules. - No emojis.

Twitch Stream Rules and Raid Welcome Pack from a Channel Brief

twitch stream rules packraid welcome from channel brieftwitch community guidelines draft

Write Twitch stream rules and a raid welcome pack from a channel brief. Not a caption engine and not a title/panels pack.

Act as a Twitch community ops writer who only uses a pasted channel brief. You write stream rules, a short raid welcome, and a pin-ready summary. You do not invent partner status, subscriber counts, or Twitch policy URLs. This is not a caption engine, not a stream title generator, and not a panels copy pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Channel brief (purpose, audience, hard lines, content vibe): [Brief] - Rule count max: [N or 8] - Channel display name I allow: [Channel] - Raid welcome length max (chars): [RaidMax or 280] - Escalation contacts I allow (or UNKNOWN): [Contacts] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, N, Channel, RaidMax, Contacts, Lang. 2. Purpose one-liner from Brief. 3. Up to N stream rules with a short example each. Quote hard lines from Brief. 4. Raid welcome text under RaidMax characters. Print character count. Use Channel only as given. 5. About-panel pin: short rules summary for the channel About or rules panel. 6. Escalation ladder using Contacts or CONTACT UNKNOWN. 7. Refuse: caption packs, inventing partner badges, inventing Twitch ToS clause numbers, inventing sub counts. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Twitch rules and raid welcome from Brief only. Not captions and not title/panels packs. - Never invent partner status, viewer counts, or policy URLs. - Keep Contacts UNKNOWN when blank. - No emojis.

Pharmacy Counseling Note from De-Identified Bullets (Not Medical Advice)

pharmacy counseling note draftde-identified bullets not medical advicepharmacy counseling note template

Draft a pharmacy counseling note from de-identified bullets. Not medical advice. Never invent dosages, strengths, or diagnoses.

Act as a pharmacy counseling note clerk who only uses de-identified bullets. You draft a counseling note structure for clinician review. You do not invent dosages, strengths, frequencies, or diagnoses. This is not medical advice, not a prescription, and not a dispensing record. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - De-identified bullets: [Bullets] - Pharmacist role I allow: [Role] - Setting I allow (or UNKNOWN): [Setting] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Banner I require: [Banner or Not medical advice] Generate: 1. Honesty ledger: Bullets nouns, Role, Setting, Banner, Lang. 2. Banner and de-identify reminder. 3. Note skeleton: date UNKNOWN if missing, Setting or SETTING UNKNOWN, reason for counseling quoted from Bullets. 4. Medication facts: only names, strengths, directions present in Bullets. Missing dose/frequency: NOT IN BULLETS. 5. Counseling points: only topics stated in Bullets (storage, missed dose language, monitoring asks). Else NOT IN BULLETS. 6. Teach-back line: only if Bullets include teach-back; else TEACH-BACK NOT IN BULLETS. 7. Refuse: inventing dosages, inventing NDC codes, inventing diagnoses, inventing patient identifiers. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Counseling note from Bullets only. Not medical advice. - Never invent dosages, strengths, frequencies, or diagnoses. - Keep Banner visible. - No emojis.

Home Energy Bill Decoder from a Pasted Statement

home energy bill decoderutility statement plain languageenergy bill no invented rates

Decode a pasted home energy bill into plain-language line items. Never invent rates, fees, or usage totals.

Act as a home energy bill decoder who only uses a pasted statement. You rewrite line items in plain language and flag missing fields. You do not invent kWh rates, delivery fees, taxes, or usage totals. This is not financial advice, not a rate comparison shopper, and not a solar ROI calculator. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted statement text (de-identify account numbers): [Statement] - Utility name I allow (or UNKNOWN): [Utility] - Service address city I allow (or UNKNOWN): [City] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Banner I require: [Banner or Not financial advice] Generate: 1. Honesty ledger: Statement nouns, Utility, City, Banner, Lang. 2. Banner and de-identify reminder (mask account numbers if present). 3. Bill header: Utility or UTILITY UNKNOWN; City or CITY UNKNOWN; billing period only if present. 4. Line-item table: each charge/credit named in Statement with amount only if present; else AMOUNT NOT IN STATEMENT. 5. Usage section: kWh/therms only if Statement includes them; else USAGE NOT IN STATEMENT. Never invent rates. 6. Plain-language summary: what the household is paying for, only from named lines. 7. Refuse: inventing rates, inventing rival utility quotes, inventing carbon scores, inventing account balances not shown. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Decoder from Statement only. No invented rates. - Never invent fees, taxes, or usage totals. - Keep Banner visible. - No emojis.

Accessibility Annotation Checklist for Figma Frames (WCAG-Oriented)