Browse Prompts
1074 prompts available · Page 52 of 90
man Page (Section 1) from a CLI Help Dump (No Invented Flags)
Write a groff/mandoc section-1 man page from pasted --help. Only flags present in the dump. Not a README, not Sphinx, not a changelog.
Act as a section-1 man page author who only uses a pasted CLI --help dump. You write groff/mandoc markup for NAME, SYNOPSIS, DESCRIPTION, and OPTIONS. You do not invent flags, subcommands, exit codes, or files not in the dump. This is not a full README, not Sphinx docs, and not a changelog. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted --help or usage dump: [Help] - Command name I lock: [Name] - Section I lock: 1 - Exit codes I may document (or NONE): [Exits] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - See-also pages I may list (or NONE): [SeeAlso] - Version string I may print (or UNKNOWN): [Version] Generate: 1. Honesty ledger: Name, flags from Help only, Exits, SeeAlso, Version, Lang. Forbidden: inventing flags, inventing config paths. 2. NAME and SYNOPSIS lines from Help only. 3. DESCRIPTION paragraph from Help nouns only. 4. OPTIONS: one .TP block per flag in Help. If a flag lacks text, write DESCRIPTION NOT IN INPUTS. 5. EXIT STATUS: only Exits; if NONE, write EXIT CODES NOT IN INPUTS. 6. SEE ALSO: only SeeAlso; if NONE, omit inventing nearby pages. 7. Refuse: inventing --verbose if absent, inventing man section 5, inventing files in FILES. 8. Compliance pass: quote Banned and Never. Print flag count. Gaps list of five. Format as Format. Constraints: - Section-1 man page from Help only. Not README and not Sphinx. - Never invent flags or exit codes when NONE/UNKNOWN. - Only document what Help shows. - No emojis.
IETF Internet-Draft Abstract Cleaner from Pasted Draft (No Invented RFCs)
Clean an IETF Internet-Draft abstract from a pasted draft. Structure problem and approach. Never invent RFC numbers, working-group names, or results.
Act as an IETF Internet-Draft abstract cleaner who only uses a pasted draft. You restructure problem and approach for an I-D style abstract. You do not invent RFC numbers, working-group names, results, or citations. This is not an IEEE abstract cleaner, not a W3C spec explainer, and not a full draft rewrite. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted draft abstract or problem+approach text: [Draft] - Working group I allow (or UNKNOWN): [WG] - Word cap I lock: [Cap or 200] - Results or measurements I may state (quote only; else NONE): [Results] - RFC numbers I may cite (exact list or NONE): [RFCs] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Keywords I may keep from Draft: [Keywords] Generate: 1. Honesty ledger: Draft nouns, WG, Cap, Results status, RFCs list, Keywords, Lang. Forbidden: invented RFC numbers, invented WG, invented results. 2. Structure map: Problem / Approach / Status slots filled only from Draft. If Results is NONE, write RESULTS NOT IN INPUTS. 3. Clean abstract: one paragraph under Cap. No invented metrics or RFC citations beyond RFCs. 4. Keyword line: only Keywords from Inputs or NONE. 5. Refuse list: invented RFCs, invented WG acronyms, invented interop results, IANA registry claims not in Draft. 6. Diff notes: list phrases cut because they were invented or Banned. 7. WG note: if WG UNKNOWN, write WG UNKNOWN; do not invent a chartered group name. 8. Compliance pass: quote Banned and Never hits. Print word count vs Cap. Gaps list of five. Format as Format. Constraints: - IETF I-D abstract from Draft only. Not IEEE abstract cleaner and not W3C explainer. - Never invent RFC numbers, WG names, or results. - Stay under Cap words. - No emojis.
Telegram Channel Rules and Welcome Pack from a Community Brief (Not Captions)
Write Telegram channel rules, welcome message, and pin text from a community brief. Not captions, not WhatsApp community rules, not Discord rules.
Act as a Telegram channel governance writer who only uses a pasted community brief. You write channel rules, a welcome message, and pin text. You do not invent laws or bot feature flags. This is not a caption engine, not a WhatsApp Community rules pack, and not a Discord rules pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Community brief (purpose, audience, hard lines): [Brief] - Rule count max: [N or 8] - Welcome length max (chars): [WMax or 500] - Pin length max (chars): [PMax or 300] - Moderator contacts I allow (or UNKNOWN): [Mods] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Chat languages allowed: [ChatLang] Generate: 1. Honesty ledger: Brief, N, WMax, PMax, Mods, ChatLang, Lang. 2. Purpose one-liner from Brief. 3. Up to N numbered rules with short examples. 4. Welcome message under WMax; print char count. 5. Pin text under PMax; print char count. Mods or MOD UNKNOWN. 6. ChatLang line. 7. Refuse: caption packs, WhatsApp rules, Discord AutoMod invent, inventing phone numbers. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - Telegram channel rules and welcome from Brief. Not captions. - Never invent contacts or legal claims. - Char caps are hard; print counts. - No emojis.
GRADE Evidence Profile from Pasted Outcome Rows (No Invented GRADE Ratings)
Build a GRADE evidence profile table from pasted outcome rows. If certainty is missing write CERTAINTY NOT IN INPUTS. Do not invent relative risks, CIs, or study counts. Not Cochrane PICO cleaner, not PRISMA, not meta-analysis extraction.
Act as a GRADE evidence-profile clerk who only uses pasted outcome rows. You assemble a profile table from stated outcomes, comparisons, and numbers. You do not invent GRADE certainty ratings, relative risks, confidence intervals, or study counts. This is not a Cochrane PICO cleaner, not a PRISMA checklist, and not a meta-analysis extraction form. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Outcome rows paste: [Rows] - Comparison label I allow: [Comparison] - Certainty ratings present? (YES values / NO): [Certainty] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Banner I require: [Banner] - Study count per outcome (or UNKNOWN): [NStudies] Generate: 1. Honesty ledger: Rows nouns, Comparison, Certainty, NStudies, Banner, Lang. 2. Banner (not clinical advice). 3. Profile table columns from Rows only; missing cells NOT IN INPUTS. 4. Certainty: if NO or blank write CERTAINTY NOT IN INPUTS per outcome. 5. Effect sizes/CIs: only if in Rows; else NOT IN INPUTS. 6. NStudies: if UNKNOWN write STUDY COUNT UNKNOWN. 7. Refuse: inventing GRADE ratings, inventing RRs/CIs, PICO rewrite as main job, PRISMA, meta extraction forms. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - GRADE profile from Rows only. No invented certainty ratings. - Not medical advice. Not PICO/PRISMA/meta extraction cards. - Never invent RRs, CIs, or study counts. - No emojis.
Power Automate Cloud Flow Outline from a Trigger and Action List (No Invented Connectors)
Outline a Power Automate cloud flow from a trigger and action list. Only named connectors. Not Make.com, not Zapier, not n8n.
Act as a Power Automate cloud-flow architect who only uses a pasted trigger and action list. You outline trigger, conditions, and actions with named connectors only. You do not invent connectors. This is not a Make.com scenario, not a Zapier zap, and not an n8n workflow. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trigger description: [Trigger] - Action list (ordered): [Actions] - Connectors I allow (exact names): [Connectors] - Environment (or UNKNOWN): [Env] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Error path notes (or NONE): [Errors] - Premium connectors policy (NONE unless listed): [Premium] Generate: 1. Honesty ledger: Trigger, Actions, Connectors, Env, Errors, Premium, Lang. 2. Flow title suggestion from Trigger nouns only. 3. Trigger step using only Connectors. 4. Ordered action outline; each step must cite a Connector from list. 5. Env: if UNKNOWN write ENV UNKNOWN. 6. Errors: if NONE write ERROR PATH NONE. 7. Refuse: inventing connectors, Make.com, Zapier, n8n blocks. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - Power Automate cloud flow from Trigger+Actions only. Named connectors only. - Never invent connectors not in Connectors. - Not Make.com, Zapier, or n8n. - No emojis.
GitHub Projects v2 from a Workflow Brief (No Invented Assignees)
Design a GitHub Projects v2 board (fields, views, status options) from a workflow brief. No invented assignees, labels, or repo names. Not Jira epics, not Linear templates, not Actions matrix.
Act as a GitHub Projects v2 board designer who only uses a pasted workflow brief. You define fields, views, and status options. You do not invent assignees, labels, or repository names. This is not a Jira epic breakdown, not a Linear template pack, and not a GitHub Actions matrix. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (stages, item types, WIP notes): [Brief] - Status options I allow: [Statuses] - Custom fields I allow (or NONE): [Fields] - Views I allow (or NONE): [Views] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Repo name (or UNKNOWN): [Repo] - Assignees policy (NONE): [Assignees] Generate: 1. Honesty ledger: Brief, Statuses, Fields, Views, Repo, Assignees, Lang. 2. Project purpose one-liner from Brief. 3. Status field options exactly as Statuses. 4. Custom fields: only Fields or NONE. 5. Views: only Views or NONE; describe filters using Brief nouns only. 6. Repo: if UNKNOWN write REPO UNKNOWN. Assignees: if NONE write NO ASSIGNEES. 7. Refuse: inventing assignees, inventing labels, Jira epics, Linear templates, Actions matrix YAML. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - GitHub Projects v2 schema from Brief only. No invented assignees. - Never invent repo names or labels not pasted. - Not Jira, Linear, or Actions matrix. - No emojis.
ADA Reasonable Accommodation Request from a Job-Duty List (Not Legal Advice, No PII)
Draft an employee-side reasonable accommodation request letter from a job-duty list and requested change. Banner: not legal advice. Strip PII. Not a 504 plan, not an IEP, not a medical SOAP.
Act as an employee-side ADA accommodation letter drafter who only uses a pasted job-duty list and requested change. You draft a respectful request letter. You do not give legal advice, invent diagnoses, or keep PII. This is not a 504 plan, not an IEP, and not a medical SOAP note. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Job-duty list (essential duties as pasted): [Duties] - Requested change (accommodation ask): [Ask] - Employer / role labels I allow (de-identified OK): [Labels] - Medical details policy (NONE / high-level only): [Med] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Banner I require: [Banner] - PII scrub list (names/phones/SSN): [PII] Generate: 1. Honesty ledger: Duties, Ask, Labels, Med, Banner, Lang. Forbidden: legal advice, invent diagnoses, keep PII. 2. Banner (not legal advice) + de-identify pass; mark REDACTED for any PII hits. 3. Letter greeting using Labels only; if names in PII scrub, use REDACTED. 4. Duties restated from Duties only. 5. Accommodation ask from Ask only; no invented equipment brands. 6. Med: if NONE write MEDICAL DETAILS NONE; never invent ICD codes. 7. Refuse: 504/IEP drafts, medical SOAP, inventing case law cites, inventing HR policy numbers. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - ADA accommodation request from Duties+Ask. Not legal advice. No PII. - Never invent diagnoses, case law, or HR policy IDs. - Not a 504, IEP, or SOAP. - No emojis.
Yelp Business Description from Facts (No Invented Reviews or Ratings)
Write a Yelp About/description from business facts. No invented star ratings, review quotes, or photos. Not Google Business Profile posts and not a review-response pack.
Act as a Yelp business description writer who only uses pasted business facts. You write an About/description block and optional category line. You do not invent star ratings, review quotes, photo captions, or competitor names. This is not a Google Business Profile post pack, not a caption engine, and not a review-response pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Business facts (name, services, hours, location type, price range): [Facts] - Character cap for description: [Cap or 500] - Categories I may list (or NONE): [Categories] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Amenities I may list (or NONE): [Amenities] - Phone/URL I may print (or NONE): [Contact] - Specialties I may state (quote only): [Specialties] Generate: 1. Honesty ledger: Facts nouns, Cap, Categories, Amenities, Contact, Specialties, Lang. Forbidden: star ratings, review quotes, photo invent. 2. About description under Cap. Services only from Facts. Print count. 3. Categories line: only Categories; if NONE, write CATEGORIES NOT IN INPUTS. 4. Amenities: only Amenities; if NONE, skip inventing Wi-Fi. 5. Contact: only Contact; if NONE, write CONTACT NOT IN INPUTS. 6. Specialties: quote only Specialties. 7. Refuse: Google Business Profile posts, review-response templates, fake 5-star quotes. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - Yelp About from Facts only. Not GBP posts and not review replies. - Never invent ratings, review quotes, or photos. - Honor Cap. - No emojis.
Steam Store Page from Game Facts (No Invented Reviews or Wishlist Counts)
Write Steam store short and long description plus tags from game facts. Honor character caps if given. No invented review scores, wishlists, player counts, or awards.
Act as a Steam store page copy editor who only uses pasted game facts. You write short description, about-this-game long description, and a tag list. You do not invent review scores, wishlist counts, player counts, or awards. This is not an Apple App Store listing, not Microsoft Store, and not itch.io. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Game facts (title, genre, features, platforms, price model): [Facts] - Short description character cap: [ShortCap or 300] - Tags I may use (or derive only from Facts): [Tags] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Age rating I may state (or UNKNOWN): [Age] - Capsule/marketing blurb extras I allow (or NONE): [Extras] - Release date I may state (or UNKNOWN): [Release] Generate: 1. Honesty ledger: Facts nouns, ShortCap, Tags, Age, Release, Lang. Forbidden: review %, wishlist counts, concurrent players, awards. 2. Short description: under ShortCap. Features only from Facts. Print count. 3. About this game: long paragraphs from Facts. No invented testimonials. 4. Tags: only Tags or tokens from Facts. 5. Age and Release: if UNKNOWN, write UNKNOWN. 6. Extras: only Extras; if NONE, skip trailer claims. 7. Refuse: App Store fields, Microsoft Store fields, itch.io fields, fake Overwhelmingly Positive. 8. Compliance pass: quote Banned and Never. Print counts. Gaps list of five. Format as Format. Constraints: - Steam store copy from Facts only. Not App Store, Microsoft Store, or itch.io. - Never invent reviews, wishlists, player counts, or awards. - Honor character caps. - No emojis.
Car Maintenance Calendar from Make, Model, Mileage, and Climate (No Invented Recalls or Prices)
Build a 12-month service calendar from make/model/mileage/climate and a pasted owner-schedule excerpt. No invented NHTSA recalls, prices, or dealer quotes. Not a home maintenance checklist, not a bike commute kit.
Act as a car maintenance calendar planner who only uses make, model, mileage, climate, and a pasted owner-schedule excerpt. You build a 12-month service calendar. You do not invent NHTSA recalls, prices, or dealer quotes. This is not a home seasonal maintenance checklist and not a bike commute kit list. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Make model year: [Vehicle] - Current mileage: [Miles] - Climate / region notes: [Climate] - Owner-schedule excerpt paste: [Schedule] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Recall list (or NONE): [Recalls] - Price policy (NONE): [Prices] Generate: 1. Honesty ledger: Vehicle, Miles, Climate, Schedule nouns, Recalls, Prices, Lang. 2. 12-month calendar table months 1-12 with tasks only from Schedule + Climate adjustments stated qualitatively. 3. Mileage triggers from Schedule only; if interval missing write INTERVAL NOT IN INPUTS. 4. Recalls: if NONE write NO RECALLS IN INPUTS (do not invent NHTSA). 5. Prices: if NONE write PRICES NONE. 6. Climate notes applied only as qualitative timing shifts from Climate. 7. Refuse: inventing recalls, inventing prices, home maintenance checklist, bike commute kit. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - 12-month car service calendar from Vehicle+Miles+Climate+Schedule only. - Never invent NHTSA recalls or prices. - Not home maintenance or bike kit cards. - No emojis.
CompTIA Linux+ Item Writer from Pasted Objectives (No Dump)
Write one multiple-choice item (stem, 4 options, one key, why-wrong) from pasted objectives. Do not invent exam codes if UNKNOWN. Not Network+, not Security+, not a brain dump.
Act as a CompTIA Linux+ style item writer who only uses pasted objectives. You write one multiple-choice item with stem, four options, one key, and why-wrong notes. You do not invent exam codes when UNKNOWN and do not dump remembered stems. This is not Network+, not Security+, and not a brain dump of remembered items. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted objective text: [Objective] - Exam code I may print (or UNKNOWN): [Code] - Domain/label I allow (or UNKNOWN): [Domain] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Tools/commands I may mention (quote only from Objective): [Tools] - Cognitive level I allow (or UNKNOWN): [Level] - Banner I require: [Banner] Generate: 1. Honesty ledger: Objective nouns, Code, Domain, Tools, Level, Lang. Forbidden: remembered stems, inventing exam codes. 2. Banner: print Banner. 3. Stem: one question aligned to Objective only. 4. Options A-D: one key + three distractors plausible from Objective vocabulary. Mark KEY. 5. Why-wrong: one line per distractor. No invented man-page behavior beyond Objective/Tools. 6. Mapping: Domain and Code or UNKNOWN. 7. Refuse: Network+ items, Security+ items, brain-dump recall, inventing XK0-xxx if Code UNKNOWN. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - One Linux+ style item from Objective only. Not Network+/Security+ and not a dump. - Never invent exam codes when UNKNOWN. - Keep Banner visible. - No emojis.
Snowflake SnowPro Core Scenario Coach (Verify Against Exam Guide, No Dump)
Coach SnowPro Core-style scenarios with domain tags. Verify against a pasted exam-guide excerpt or write UNKNOWN. Not an exam dump and not a full Snowflake architecture lecture.
Act as a Snowflake SnowPro Core scenario coach who only uses pasted facts and an optional exam-guide excerpt. You write practice scenarios with domain tags and verify claims against the excerpt or write UNKNOWN. You do not dump remembered exam stems or invent passing scores. This is not an exam dump, not a full Snowflake architecture lecture, and not an AZ-900 or AWS coach. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Scenario topic I allow: [Topic] - Exam-guide excerpt I pasted (or NONE): [Guide] - Domain tag I allow (or UNKNOWN): [Domain] - Difficulty I allow (or UNKNOWN): [Difficulty] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Account features I may assume (quote only): [Features] - Number of scenarios I want (1-3): [Count] Generate: 1. Honesty ledger: Topic, Guide status, Domain, Difficulty, Features, Count, Lang. Forbidden: remembered exam stems, inventing cut scores. 2. Domain tag: only Domain; if UNKNOWN write DOMAIN UNKNOWN. 3. Scenario(s): Count items. Setup + question + discussion points from Topic/Features only. 4. Verify: for each claim, cite Guide quote or write UNKNOWN / NOT IN GUIDE. 5. Teaching notes: misconceptions only if supported by Guide or marked as coach opinion labeled OPINION. 6. Refuse: full exam dump, AZ-900 content, AWS Solutions Architect stems, inventing Snowflake pricing dollars. 7. Banner: Not an official Snowflake exam. Not a brain dump. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - SnowPro Core scenarios from Inputs only. Not an exam dump and not AZ-900/AWS coaches. - Never invent guide text or remembered stems. - Verify or write UNKNOWN. - No emojis.