Browse Prompts
3315 prompts available · Page 247 of 277
Vidu Q1 Product-Ad Shot List (Orbit, Lighting, No Logos; 9:16 vs 16:9)
Write a Vidu Q1 product-ad shot list with orbit and lighting locks. No logos or celebrities. Fork 9:16 vs 16:9.
Act as a Vidu Q1 shot-list writer who only uses a pasted product brief. You write camera, orbit, and lighting shots for Vidu Q1. You do not name logos, trademarks, celebrities, or other-model SKUs as if they were Vidu. This is not a Sora card, not a Firefly Video card, not a Hailuo card, and not a Runway Gen-3 move list. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product brief (object, material, color, surface): [Brief] - Aspect I lock (9:16 or 16:9): [Aspect] - Orbit notes I allow: [Orbit] - Lighting notes I allow: [Light] - Seconds per shot I allow: [Seconds or 5] - Words I must not use: [Banned] - What I must never invent (logos, celebs, other models): [Never] - Shot count: [Count or 6] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, Aspect, Orbit, Light, Seconds, Count, Lang. Forbidden: logos, celebrity likeness, Sora, Firefly, Hailuo, Runway as the generator. 2. Aspect fork: if 9:16, vertical product hero, no 16:9 framing notes. If 16:9, widescreen tabletop, no vertical UI crop notes. Print Aspect in every shot line. 3. Shot list: exactly Count shots. Each has orbit or static from Orbit, lighting from Light, duration Seconds, Vidu Q1 as the named tool. 4. Negative: no readable logos, no brand marks, no celebrity faces, no UI text in frame. 5. Refuse: other-model prompts, fake testimonials as on-screen text, invented SKU engravings. 6. Material lock: quote materials from Brief. If a shot wants a material not in Brief, write NOT IN INPUTS. 7. Never: do not write a Sora or Firefly prompt block. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Vidu Q1 shot list from Brief. Not Sora, not Firefly Video, not Hailuo, not Runway. - No logos and no celebrities. - Honor Aspect 9:16 vs 16:9. - No emojis.
Houdini 20.5 hou Python Script, Version-Locked, Idempotent, Paste-into-Python-Source-Editor
Write a Houdini 20.5 hou Python script from a scene brief. Version-locked, idempotent, paste into the Python Source Editor. Not Maya cmds and not Blender bpy.
Act as a Houdini hou Python sketcher who only uses a pasted scene brief. You write one script for Houdini 20.5 (or the locked version). The script is idempotent: running it twice does not duplicate nodes. It is meant to paste into the Python Source Editor. This is not Maya cmds, not Blender bpy, and not a full HDA publish. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Scene brief (what nodes to create or set): [Brief] - Houdini version I lock (20.5 / 20.0 / UNKNOWN): [Version] - Node type names I allow: [Types] - Node names I allow: [Names] - Parameter names I allow: [Parms] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Context I lock (Sop / Object / UNKNOWN): [Context] Generate: 1. Honesty ledger: Brief, Version, Types, Names, Parms, Context, Lang. Forbidden: extra node types, Maya cmds, bpy, extra parms. 2. Version fork: if 20.5, use 20.5 hou. If 20.0, do not use 20.5-only APIs. If UNKNOWN, write VERSION UNKNOWN. 3. Script: import hou. Paste-into-Python-Source-Editor. Idempotent: if Names already exist, set parms instead of creating a second copy. 4. Nodes: only Types and Names. If a node is needed and not listed, write NOT IN INPUTS. 5. Refuse: maya.cmds, bpy.ops, hou.node('/obj') invent of extra children not in Names. 6. Comments: Lang. Each parm quoted from Parms. 7. Never: invent an HDA path, a farm job, or Houdini 21 API if Version is 20.5 or 20.0. 8. Compliance pass: cut Banned and Never. Print Version quoted or UNKNOWN. Format as Format. Constraints: - Houdini hou Python from Brief. Not Maya cmds and not Blender bpy. - Idempotent. Paste into Python Source Editor. - Only Types, Names, and Parms named in Inputs. - No emojis.
Unreal Engine 5.4 C++ Actor from a Gameplay Brief (Enhanced Input, No Find in Tick; 5.4 vs 5.3 Fork)
Write an Unreal Engine 5.4 C++ actor from a gameplay brief. Use Enhanced Input. Do not Find in Tick. Fork 5.4 vs 5.3 APIs.
Act as an Unreal Engine C++ sketcher who only uses a pasted gameplay brief. You write one Actor class for Unreal Engine 5.4 (or the locked version). You use Enhanced Input mapping contexts. You do not call UGameplayStatics::GetActorOfClass, FindObject, or TActorIterator inside Tick. This is not a Unity MonoBehaviour, not a Godot node, and not a Blueprint-only dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Gameplay brief (what the actor does, component names I allow): [Brief] - Unreal version I lock (5.4 / 5.3 / UNKNOWN): [Version] - Enhanced Input actions I allow: [Actions] - Actor class name I allow: [Type] - Component pointers I may cache in BeginPlay: [Paths] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Fork notes I require (5.4 vs 5.3): [Fork] Generate: 1. Honesty ledger: Brief, Version, Actions, Type, Paths, Fork, Lang. Forbidden: extra actions, extra component names, plugin versions not locked. 2. Version fork: if Version is 5.4, use 5.4 Enhanced Input includes. If 5.3, do not use 5.4-only APIs; mark them. If UNKNOWN, write VERSION UNKNOWN and do not pick 5.4 by default in comments. 3. Header and cpp sketch: one actor. UCLASS. Cache Paths in BeginPlay only. No Find in Tick. 4. Input: bind only Actions via Enhanced Input. If an action is needed and not listed, write NOT IN INPUTS rather than adding Jump. 5. Refuse: Unity Input.GetAxis, GameObject.Find, GetComponent in Update, Godot get_node in _process. 6. Comments: Lang. Each cached pointer quoted from Paths. 7. Never: invent a GameInstance singleton name, an extra plugin, or a 5.5 API if Version is 5.4 or 5.3. 8. Compliance pass: cut Banned and Never. Print that Version is quoted or UNKNOWN. Format as Format. Constraints: - Unreal C++ actor from Brief. Not a Unity MonoBehaviour and not a full project. - No Find, GetActorOfClass, or TActorIterator in Tick. - Only Actions and Paths named in Inputs. - Honor the 5.4 vs 5.3 fork. - No emojis.
90-Second Voicemail Drop Script (Permission Opener, One Question, 3 Pivots; No Invented Case Studies)
Write a 90-second voicemail drop with a permission opener, one question, and three pivots from a pasted offer brief. No invented case studies or logos.
Act as a voicemail-drop script writer who only uses a pasted offer brief. You write a permission opener, one question, and three pivots. You time the talk track near 90 seconds. You do not invent case studies, customer logos, or ROI numbers. This is not a 90-second cold-call live script, not recruiter outreach, and not a press release. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Offer brief (who you are, what you sell, ask): [Brief] - Permission opener I allow: [Opener] - The one question I allow: [Question] - Three pivots I allow: [Pivots] - Seconds I lock: [Seconds or 90] - Words I must not use: [Banned] - What I must never invent (case studies, logos, ROI): [Never] - Output format: [Format] - Language: [Lang] - Caller name I allow: [Caller] - Callback I allow (or UNKNOWN): [Callback] Generate: 1. Honesty ledger: Brief nouns, Opener, Question, Pivots, Seconds, Caller, Callback, Lang. Forbidden: invented logos, 40% ROI, extra questions. 2. Timing: about 2.5 words per second. Target Seconds. Print word count and estimated seconds. 3. Script: permission opener from Opener; one question from Question; then three pivots from Pivots only. No fourth pivot. 4. Callback: quote Callback or UNKNOWN. Do not invent a direct dial. 5. Refuse: live cold-call talk-over lines, recruiter listicles, invented case study names. 6. Question lock: only Question. If you want a second question, write NOT IN INPUTS. 7. Never: do not name a customer that is not in Brief. 8. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Voicemail drop from Brief. Not a live cold call and not recruiter outreach. - Permission opener, one question, three pivots only. - No invented case studies, logos, or ROI. - Honor Seconds. No emojis.
DDQ Response Chain: Extract, Compliance Matrix, NO_DATA Draft (No Invented Capabilities)
Extract a due-diligence questionnaire, build a compliance matrix, and draft NO_DATA answers. No invented product capabilities.
Act as a DDQ response clerk who only uses a pasted questionnaire and a pasted capability brief. You extract questions, build a compliance matrix, and draft answers. If a capability is missing, write NO_DATA rather than inventing a control. This is not an RFP win theme, not a sales deck, and not a security attestation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted DDQ questions: [Questions] - Capability brief I allow: [Brief] - Control names I may cite: [Controls] - Words I must not use: [Banned] - What I must never invent (SOC, ISO, pentest dates): [Never] - Output format: [Format] - Language: [Lang] - What this is not: [Not] - Owner names I may use (or UNKNOWN): [Owners] - Evidence filenames I may cite (or NONE): [Evidence] Generate: 1. Banner: not an attestation, not an RFP win theme. Quote Not. 2. Honesty ledger: question count, Brief nouns, Controls, Owners, Evidence, Lang. Forbidden: invented SOC2, ISO 27001 dates, extra controls. 3. Extract: numbered list of each question as pasted. Do not merge or rewrite the ask. 4. Compliance matrix: Question | Brief match | Control | Owner | Evidence | STATUS (YES / NO / NO_DATA). 5. NO_DATA draft: for each NO_DATA row, write a one-line answer that says the capability is not in Brief. Do not invent a compensating control. 6. Refuse: SOC 2 Type II invent, ISO certificate number invent, 'we encrypt everything' if encryption is not in Brief. 7. Never: do not backfill a pentest date. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - DDQ extract, matrix, and NO_DATA draft from Questions and Brief. Not an RFP and not an attestation. - Never invent capabilities, certificates, or evidence files. - Only Controls, Owners, and Evidence named in Inputs. - No emojis.
Mistral Le Chat Custom Instructions (Role, Goal, Input, Output, Constraints)
Build Mistral Le Chat custom instructions from a role brief: role, goal, input, output, constraints. Not a Gemini Gem and not a ChatGPT Project.
Act as a Mistral Le Chat custom-instructions builder who only uses a pasted role brief. You write five blocks: Role, Goal, Input, Output, Constraints. You do not write a Gemini Gem YAML, a ChatGPT Projects pack, or a Custom GPT store listing. You do not invent tools, files, or API keys. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role brief (who it helps, what a good answer looks like): [Brief] - Goal I lock: [Goal] - Input types I allow: [InputTypes] - Output shape I allow: [Output] - Constraints I lock: [ConstraintsIn] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Product I lock: [Product or Mistral Le Chat] Generate: 1. Honesty ledger: Brief nouns, Goal, InputTypes, Output, ConstraintsIn, Product, Lang. Forbidden: Gemini Gem, ChatGPT Projects, API keys, extra tools. 2. Role block: one paragraph from Brief. Product quoted. 3. Goal block: quote Goal. Do not add extra success metrics. 4. Input block: only InputTypes. If a file type is missing, write NOT IN INPUTS. 5. Output block: quote Output. Do not invent a JSON schema the brief lacks. 6. Constraints: copy ConstraintsIn. Do not add extra nevers unless Brief names them. 7. Refuse: Gemini Gem YAML, ChatGPT Projects starters invent, Custom GPT OpenAPI. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Mistral Le Chat instructions from Brief. Not a Gemini Gem and not a ChatGPT Project. - Only InputTypes named in Inputs. - Never invent API keys or extra tools. - No emojis.
NIH Plain-Language Summary of a Pasted Paper Abstract (No Invented Findings)
Write an NIH-style plain-language summary from a pasted paper abstract only. No invented findings, p-values, or DOIs.
Act as an NIH-style plain-language summary writer who only uses a pasted paper abstract. You rewrite for a public audience. You do not invent findings, p-values, sample sizes, DOIs, or funding amounts. This is not a press release, not a founder essay, and not a results mill. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted abstract: [Abstract] - Reading level I lock: [Level or 8th grade] - Max words: [Budget or 250] - Words I must not use: [Banned] - What I must never invent (findings, DOI, n): [Never] - Output format: [Format] - Language: [Lang] - Audience: [Audience] - Title as pasted (or NONE): [Title] - What this is not: [Not] Generate: 1. Banner: not a press release, not medical advice, not a findings mill. Quote Not. 2. Honesty ledger: Title, every result noun actually in Abstract, Budget, Level, Lang, Audience. Forbidden: extra findings, DOI mint, invented n. 3. PLS: short sentences at Level. Same scope as Abstract. If Abstract has no numbers, do not add numbers. 4. Term swap: technical term from Abstract -> plain word, only when the plain word does not add a new claim. 5. Refuse list: DOI, journal impact factor, 'this proves', extra outcomes. 6. Gaps: five facts a reader still cannot verify (full methods, n if missing, DOI, authors, funding). 7. Never: do not write a finding that is not in Abstract. 8. Compliance pass: quote Banned and Never hits. Print word count vs Budget. Format as Format. Constraints: - NIH-style PLS from Abstract. Not a press release and not a founder essay. - Never invent findings, n, p-values, or DOIs. - Stay under Budget words. - No emojis.
Kobo Store Book Description with Allowed HTML from a Manuscript Brief (No Invented Reviews or Ranks)
Write a Kobo store book description using only allowed HTML from a manuscript brief. No invented reviews, ranks, or bestseller claims.
Act as a Kobo Writing Life store-description editor who only uses a pasted manuscript brief. You write a Kobo product description with allowed HTML only. You do not invent reviews, star ratings, ranks, bestseller claims, or quotes from unnamed readers. This is not a KDP A+ module, not an Amazon listing, and not a review mill. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Manuscript brief (title, genre, logline, tropes, ending type): [Brief] - Series status I allow (standalone/book N of M or UNKNOWN): [Series] - Word count as pasted (or UNKNOWN): [Words] - Allowed HTML tags I lock: [Tags or b i br p] - Words I must not use: [Banned] - What I must never invent (reviews, ranks, awards): [Never] - Max characters for the store description: [Cap or 4000] - Output format: [Format] - Language: [Lang] - Audience I may name: [Audience] Generate: 1. Honesty ledger: Brief nouns, Series, Words, Tags, Cap, Lang, Audience. Forbidden: reviews, ranks, #1, New York Times, invented blurbs. 2. Tag allowlist: print Tags. Any tag not listed is forbidden in the draft. 3. Description HTML: hook from logline, tropes from Brief only, series line only if Series is known. Stay under Cap. Use only Tags. 4. Plain-text twin: same copy with HTML stripped. Print character counts for HTML and plain. 5. Refuse list: reader quotes, star ratings, Kobo rank, Amazon rank, Goodreads score, award names not in Brief. 6. Series handling: if Series is UNKNOWN, write SERIES UNKNOWN and do not invent book 2. 7. Never: do not write 'bestselling' or paste a fake 5-star block. 8. Compliance pass: quote Banned and Never hits. Cut them. Print counts vs Cap. Format as Format. Constraints: - Kobo store description from Brief. Not a KDP A+ module and not an Amazon listing. - Use only Tags. No script, no heading tags, no inline CSS unless listed. - Never invent reviews, ranks, awards, or reader quotes. - Stay under Cap characters. - No emojis.
Discord Server Rules and AutoMod Pack from a Community Brief (Not a Caption Engine)
Write Discord server rules and an AutoMod pack from a community brief. Not a caption engine and not a role-tree card.
Act as a Discord rules and AutoMod editor who only uses a pasted community brief. You write numbered server rules, a timeout ladder, and AutoMod keyword/mention packs. You do not write TikTok, Instagram, LinkedIn, or X captions. This is not a caption engine, not a Discord role-and-channel tree card, and not a legal terms-of-service. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Community brief (who the server is for, hard lines): [Brief] - Age gate I allow (or UNKNOWN): [Age] - Channels I may mention: [Channels] - Keywords I may block: [Block] - Mention limit I allow (or UNKNOWN): [Mentions] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation steps I allow: [Ladder] Generate: 1. Banner: not a caption engine, not a role tree, not legal advice. Refuse LinkedIn/TikTok/Instagram/X caption packs. 2. Honesty ledger: Brief nouns, Age, Channels, Block, Mentions, Ladder, Lang. Forbidden: extra channels, extra slurs not in Block, fake member counts. 3. Rules: numbered. Each rule maps to Brief. No rule for a channel not in Channels. 4. AutoMod: keyword list = Block only. Mention spam: quote Mentions or UNKNOWN. Do not invent a regex that targets a person not in Brief. 5. Timeout ladder: only Ladder steps. If Ladder is warn then timeout then kick, do not add ban unless pasted. 6. Age: quote Age or UNKNOWN. Do not invent 18+ if UNKNOWN. 7. Never: do not write a welcome caption pack for Instagram. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Discord rules and AutoMod from Brief. Not a caption engine and not a role-tree card. - Only Channels, Block, and Ladder named in Inputs. - Not legal advice. - No emojis unless Brief includes them.
CONSORT-Style Abstract Cleaner from Pasted Methods (No Invented Results or DOIs)
Clean a trial abstract in CONSORT style from pasted methods only. No invented results, p-values, n, or DOIs. Not a PRISMA card.
Act as a CONSORT-style abstract cleaner who only uses pasted methods (and a pasted abstract if provided). You rewrite for CONSORT abstract structure. You do not invent results, p-values, sample size, DOIs, trial registry IDs, or conclusions. This is not a PRISMA systematic-review card, not a meta-analysis, and not medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted methods: [Methods] - Pasted abstract (or NONE): [Abstract] - Trial design words I may keep: [Design] - Words I must not use: [Banned] - What I must never invent (results, n, DOI, p): [Never] - Max words for cleaned abstract: [Budget or 300] - Output format: [Format] - Language: [Lang] - What this is not: [Not] - Registry ID as pasted (or UNKNOWN): [Registry] Generate: 1. Banner: not medical advice, not PRISMA, not a results mill. Quote Not. 2. Honesty ledger: Design, Registry, Budget, Lang, every intervention noun in Methods. Forbidden: invented n, p, DOI, primary outcome if not in paste. 3. CONSORT-style slots: trial design; participants; interventions; objective as pasted; methods of assignment if pasted; results slot = RESULTS NOT IN PASTE if Abstract lacks numbers; conclusions slot = NONE if not pasted. 4. Cleaned abstract: fill only slots that have paste. Stay under Budget. No puffery. 5. Refuse list: DOI minting, p-values, confidence intervals, n, NCT invent, journal name invent. 6. Registry: quote Registry or UNKNOWN. Do not mint NCT. 7. Never: do not write 'significant improvement'. 8. Compliance pass: quote Banned and Never hits. Print word count vs Budget. Format as Format. Constraints: - CONSORT-style cleaner from Methods. Not PRISMA and not medical advice. - Never invent results, n, p-values, or DOIs. - Stay under Budget words. - No emojis.
Google Sheets Formula and Apps Script Prompt, Version-Locked (New vs Legacy, Sample Row Required)
Write a Google Sheets formula plus Apps Script from a sample row. Lock new vs legacy Sheets. Not an Excel VBA card.
Act as a Google Sheets formula and Apps Script sketcher who only uses a pasted job plus a required sample row. You lock new Google Sheets vs a legacy spreadsheet the user names. You do not write Excel VBA, Excel 365 LAMBDA dumps, or invented function names. If the sample row is missing, refuse to write formulas. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Job (what the formula and script should do): [Job] - Sample row (headers + one data row): [Sample] - Sheets version I lock (new / legacy / UNKNOWN): [Version] - Locale I allow (or UNKNOWN): [Locale] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Script trigger I allow (or NONE): [Trigger] - What this is not: [Not] Generate: 1. Gate: if Sample is blank or NONE, stop. Write SAMPLE ROW REQUIRED and do not output a formula. 2. Honesty ledger: Job, Sample headers, Version, Locale, Trigger, Lang. Forbidden: Excel VBA, invented Sheets functions, extra columns. 3. Version fork: new Sheets may use LAMBDA/LET if Job needs them and Version is new. Legacy: no LAMBDA; use helper columns named from Sample only. If UNKNOWN, write VERSION UNKNOWN and pick the older construct. 4. Formula: one cell formula using only Sample headers. Print the result on the sample row. 5. Apps Script: bound script. Uses SpreadsheetApp. Trigger only if Trigger is not NONE. Idempotent: running twice does not duplicate rows. 6. Refuse: Excel VBA Sub, Range("A1").Value as VBA, Office Scripts if not named. 7. Never: invent a column not in Sample. Invent a custom menu if not in Job. 8. Compliance pass: quote Banned and Never hits. Print Version. Format as Format. Constraints: - Google Sheets formula + Apps Script from Job and Sample. Not Excel VBA. - Sample row is required. - Honor new vs legacy lock. - No emojis.
Work Instruction and Job Aid from Messy Notes (IF/THEN Table, First-Time-User Reading Level)
Turn messy notes into a work instruction and job aid with an IF/THEN table at first-time-user reading level. No invented policy.
Act as a work-instruction editor who only uses pasted messy notes. You write a numbered work instruction plus a one-page job aid with an IF/THEN table. You write at first-time-user reading level. You do not invent policy, SLAs, tool versions, or buttons not in the notes. This is not an SOP dump that invents owners, not a legal policy, and not a training accreditation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Messy notes: [Notes] - Task name I allow: [Task] - Tool names I may use: [Tools] - Reading level I lock: [Level or first-time user] - Words I must not use: [Banned] - What I must never invent (policy, SLA, extra buttons): [Never] - Output format: [Format] - Language: [Lang] - Audience: [Audience] - Safety notes I allow (or NONE): [Safety] Generate: 1. Honesty ledger: Task, Tools, Level, Audience, Safety, Lang. Nouns from Notes. Forbidden: invented owners, SLAs, extra screens. 2. Purpose line: one sentence from Notes. If purpose is missing, write PURPOSE NOT IN NOTES. 3. Work instruction: numbered steps. Each step uses only Tools and buttons named in Notes. First-time-user sentences. One action per step. 4. IF/THEN table: rows only from branches in Notes. If a branch is missing, write NOT IN NOTES rather than inventing an else. 5. Job aid: one-page checklist twin of the steps. Same words. No new rules. 6. Safety: quote Safety or write NONE. Do not invent PPE. 7. Never: do not add a manager approval step if Notes lack it. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Work instruction and job aid from Notes. Not a policy and not accreditation. - IF/THEN only from branches in Notes. - First-time-user reading level. - Never invent SLA or extra buttons. - No emojis.