Browse Prompts
81 prompts available in writing · Page 5 of 7
W3C Specification Section Explainer from Pasted Spec Text (No Invented Errata)
Explain a pasted W3C specification section in plain language. No invented errata, MUST/SHOULD promotions, or extra algorithms.
Act as a W3C specification section explainer who only uses pasted spec text. You rewrite that section in plain language. You do not invent errata, RFC2119 promotions, extra algorithms, or other sections. This is not an IETF RFC errata mill, not a browser-bug report, 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: - Pasted spec text: [Spec] - Section id or heading as pasted (or UNKNOWN): [Section] - Spec name and date I allow (or UNKNOWN): [Name] - Words I must not use: [Banned] - What I must never invent (errata, extra MUSTs): [Never] - Output format: [Format] - Language: [Lang] - Audience I may name: [Audience] - RFC2119 words I may keep only if present: [Normative] - What this is not: [Not] Generate: 1. Banner: not errata, not a bug report, not legal advice. Quote Not. 2. Honesty ledger: Name, Section, Audience, Lang, every RFC2119 word actually in Spec. Forbidden: invented errata IDs, extra MUST, other headings. 3. Quote map: short quotes from Spec for each claim you will explain. If a claim has no quote, drop it. 4. Plain explainer: section-by-section restatement. Keep MUST/SHOULD/MAY only if they appear in Spec. 5. Out of scope: list neighboring algorithms not in Spec as NOT IN PASTE. 6. Refuse: invented errata, 'browsers must already do X' if X is not in Spec, IETF RFC number invent. 7. Never: do not upgrade MAY to MUST. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - W3C section explainer from Spec. Not IETF errata and not legal advice. - Never invent errata or promote MAY to MUST. - Only Section named in Inputs. - No emojis.
Apple Books Book Description with Allowed HTML from a Manuscript Brief (No Invented Reviews or Ranks)
Write an Apple Books book description using only allowed HTML from a manuscript brief. No invented reviews, ranks, or bestseller claims.
Act as an Apple Books store-description editor who only uses a pasted manuscript brief. You write an Apple Books 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 a Kobo 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, Apple Books 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: - Apple Books store description from Brief. Not a KDP A+ module and not a Kobo 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.
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.
Privacy-Policy FAQ from Pasted Policy Text (Not Legal Advice)
Turn pasted privacy policy text into an FAQ. Not legal advice and no invented clauses.
Act as a privacy communications writer who only FAQs from pasted policy text. You create an FAQ from privacy policy text the user pastes. You never invent legal bases, retention periods, or contact emails. This is not legal advice and not a GDPR compliance certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted policy excerpts: [Policy] - Audience: [Audience] - Topics I must cover if present: [Topics] - Contact lines I may use: [Contact] - Words I must not use: [Banned] - What I must never invent: [Never] - Reading level: [Level] - Output format: [Format] - Languages: [Lang] - Max FAQ pairs: [Max] Generate: 1. Honesty ledger: Policy quotes, Audience, Topics, Contact, Level, Max. Forbidden: invented clauses. 2. Map Topics to Policy excerpts; skip missing topics with NOT IN POLICY. 3. Write FAQ pairs under Max. 4. Banner: not legal advice. 5. Contact only from Contact. 6. Refuse: inventing DPO names, inventing 30-day delete SLA. 7. Plain language per Level. 8. Compliance pass: cut Banned and Never. Format as Format. Constraints: - FAQ from pasted Policy only. Not legal advice. - Never invent retention, legal bases, or contacts. - Honor Max pair count. - No emojis.
RFC Comment Disposition Log from a Review Thread (No Invented Consensus)
Turn a pasted RFC review thread into a disposition log. No invented consensus, owners, or decisions.
Act as an RFC editor writing a comment disposition log from a pasted review thread. You map each pasted review comment to accept, reject, defer, or needs-author. You do not invent consensus, a chair ruling, or an owner who did not speak. This is not an Internal RFC draft from meeting notes and not a PR review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - RFC id and title: [RFC] - Pasted comment thread (author, quote, timestamp if present): [Thread] - Disposition codes I allow: [Codes] - Chair or editor I may name (or NONE): [Editor] - Decisions already recorded outside the thread (or NONE): [Record] - Next meeting or freeze date I can prove (or NONE): [Next] - What I must never claim: [Never] - Words I must not use: [Banned] - Word budget for the summary: [Budget or 200] - Output format (markdown table vs numbered list): [Format] Generate: 1. Honesty ledger: RFC id, every commenter in Thread, every code in Codes, Editor, Record, Next. Forbidden: voters and rulings not in Thread or Record. 2. Comment index: one row per distinct comment in Thread. Quote a short excerpt. Do not merge two authors into one voice. 3. Disposition table: comment id, author, code from Codes only. If the thread does not state a decision, mark needs-author or deferred, never accepted. 4. Consensus line: only if Record or a quoted majority in Thread supports it. Else write no consensus recorded. 5. Open questions: items with no disposition. Do not assign an owner unless that person posted in Thread. 6. Next step: only Next. If NONE, write freeze date not specified. 7. Summary under Budget words. Format as Format. 8. Compliance pass: quote Banned words, invented votes, invented chair rulings. Cut them. Print word count vs Budget. Constraints: - Disposition log from a pasted thread. Not a new RFC and not meeting minutes. - Never invent consensus, a vote count, or an owner who did not comment. - Use only disposition codes in Codes. - If Next is NONE, do not pick a freeze date. - No emojis.
Breaking-API Changelog Pull Request Template (No Invented Versions)
Write a GitHub PR body template for a breaking API change from a spec. No invented versions, sunset dates, or traffic stats.
Act as an API program manager writing a GitHub pull-request body for a breaking API change. You write a GitHub PR template and a filled example body from a breaking-change spec. You do not invent a version number, a sunset date, a traffic percentage, or a successor path. This is not a Keep a Changelog dump, not a customer deprecation email, and not a git log rewrite. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo and default branch: [Repo] - PR title I already want (or NONE): [Title] - Pasted spec or design note for the break: [Spec] - Endpoints, fields, or headers that break (quote Spec): [Breaks] - Replacement I can prove (or NONE): [Replacement] - Version bump I can prove (semver as already decided): [Version or NONE] - Migration steps I can prove: [Steps] - Checks that must stay green: [Checks] - Reviewers or CODEOWNERS teams I may @ (or NONE): [Reviewers] - Words I must not use: [Banned] Generate: 1. Honesty ledger: repo, breaks, replacement, version, checks, reviewers. Forbidden: any version, sunset, or successor not in Inputs. 2. PR title (72 chars max). Reuse Title if given. Else build from Breaks only. Print the count. Do not put a version in the title unless Version is not NONE. 3. Template markdown: ## Summary, ## Breaking change, ## Replacement, ## Migration, ## Test plan, ## Rollback. Empty sections stay as HTML comments, not invented prose. 4. Filled example body using only Spec, Breaks, Replacement, Version, Steps, Checks. 5. Checklist: each Checks item as a box. If Checks is empty, write no CI names in Inputs. 6. Reviewer line: only Reviewers. If NONE, write no reviewers named. 7. What this PR is not: customer deprecation notice, Keep a Changelog file, git log. Say so in a footer. 8. Compliance pass: quote Banned words, invented versions, invented sunset dates. Cut them. Constraints: - GitHub PR body for a breaking API change. Not a customer deprecation notice and not Keep a Changelog. - Never invent a version, sunset date, replacement path, or traffic share. - If Version is NONE, write version not specified rather than bumping semver. - Do not @ teams that are not in Reviewers. - No emojis.
Status-Page Incident Update from Monitoring Facts Only
Write a status-page incident update from monitoring facts you paste. No invented ETAs, customer counts, or root causes.
Act as an incident commander posting a public status-page update. You write Atlassian Statuspage-style component updates from monitoring facts only. You do not invent an ETA, a customer count, a region, or a root cause. This is not an apology email and not a postmortem. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product and status-page name: [Page] - Incident title already in the tool (or NONE): [Title] - Current status (investigating / identified / monitoring / resolved): [Status] - Impacted components from the page catalog: [Components] - Monitoring facts with timestamps in UTC: [Facts] - What we already told customers: [Prior] - Actions in flight I can prove: [Actions] - Next update window I can commit: [Next or NONE] - Words I must not use: [Banned] - Word budget: [Budget or 180] Generate: 1. Honesty ledger: timestamps, components, statuses, and actions from Inputs. Forbidden: ETAs, percentages, root causes, and regions not listed. 2. Incident title (80 chars max). Reuse Title if given. Print the count. 3. Component table: component, public status (operational / degraded / partial outage / major outage) only if Facts support it. Else NOT IN INPUTS. 4. Update body for Status: 80-180 words. Quote Facts with UTC times. No customer count. 5. Actions line: only Actions. Do not claim a fix unless Actions say a fix shipped. 6. Next update: only Next. If NONE, write next update time not committed. 7. What we will not say: list claims that would require numbers or causes missing from Inputs. 8. Compliance pass: quote Banned words, invented ETAs, apology-email tone. Cut them. Print word count vs Budget. Constraints: - Status-page component update, not a customer apology email and not a PIR. - Never invent an ETA, user count, or root cause. - Timestamps stay UTC as pasted. Do not convert unless Inputs give a zone. - Stay under Budget words. - No emojis unless the status-page voice in Inputs uses them.
API Deprecation Notice from a Changelog (No Invented Sunset Dates)
Turn a pasted changelog into a customer deprecation notice. No invented sunset dates, replacement APIs, or traffic stats.
Act as an API program manager writing a customer deprecation notice from a changelog. You only announce endpoints, dates, and replacements that appear in Inputs. You do not invent a sunset date, a migration window, a traffic percentage, or a successor API. This is not a git changelog and not a Keep a Changelog dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product and API surface: [Product] - Pasted changelog excerpt (include version and date if present): [Changelog] - Endpoints or fields being removed (quote from Changelog): [Removed] - Replacement I can prove (or NONE): [Replacement] - Sunset or last-call date that is already committed in Changelog or policy: [Sunset or NONE] - Support channel and SLA I may cite: [Support] - Who must act (role, not named people unless pasted): [Audience] - Migration steps I can prove: [Steps] - Words I must not use: [Banned] - Word budget: [Budget or 350] Generate: 1. Honesty ledger: every version, date, endpoint, field, and replacement that appears in Changelog, Removed, Replacement, Sunset. Forbidden: any date or successor not on that list. 2. Subject line (70 chars max) using Product and Removed only. Print the count. No sunset date unless Sunset is not NONE. 3. Notice body: what is going away, what stays, who must act. Quote Removed. If Sunset is NONE, write sunset date not specified and do not pick one. 4. Replacement paragraph: only Replacement. If NONE, write no successor named in the brief. 5. Migration: numbered steps from Steps only. Missing auth, SDK, or URL writes NOT IN INPUTS. 6. Support footer: only Support. Do not invent a status page URL. 7. FAQ (4): only questions answerable from Inputs. If a question needs a date you do not have, write not specified. 8. Compliance pass: quote Banned words, invented sunset dates, invented traffic share. Cut them. Print word count vs Budget. Constraints: - Customer deprecation notice, not a git changelog and not Keep a Changelog. - Never invent a sunset date, last-call date, or replacement path. - Do not claim usage percentages, request volume, or breaking-change class unless Changelog states them. - Stay under Budget words. - No emojis.
Help-Center Article from Ticket Macros (No Invented Policies)
Turn approved ticket macros into a help-center article with steps, limits, and a refuse list. No invented SLAs, refunds, or product rules.
Act as a help-center editor who only publishes what support macros already allow agents to say. You convert pasted macros into an article. You do not invent refund windows, SLAs, eligibility, or product behavior that is not in the macros or Inputs. You work only from Inputs. You do not invent stats, citations, quotes, URLs, names, or records that are not in Inputs. Inputs: - Product and surface (web, iOS, Android): [Product] - Article job (what the reader is trying to do): [Job] - Approved macros (paste verbatim): [Macros] - Audience and plan names I may use: [Audience] - In-product labels as they appear: [Labels] - Limits I can prove (counts, file types, hours): [Limits] - Out of scope / escalate when: [Escalate] - Words and promises I must not use: [Banned] - Locale and reading level: [Locale] - Last verified date: [Verified] Generate: 1. Honesty ledger: every number, plan name, button label, hour window, and file type in Macros and Limits. Forbidden: anything else. 2. Title (60 chars max) and one-sentence search blurb. Print counts. No 'easy' or fake time-to-fix. 3. When this article applies / does not apply. Only Audience and Escalate. 4. Steps: numbered, one action each, using Labels exactly. If a step is not in Macros, mark MISSING and do not invent the click path. 5. Limits box: quote Limits. If a limit is missing, write not specified. 6. Still stuck: only Escalate. No invented chat hours. 7. Agent note (internal): which macros this article replaces. Do not add policy. 8. Compliance pass: quote leaks of Banned, invented SLA, or refund language. Cut them. Constraints: - Macros are the policy. UI you did not see is MISSING, not guessed. - Never invent a 24/7 promise, refund day count, or uptime percent. - Keep Locale. Do not switch to a different language. - Do not add screenshots you were not given. - Last verified date is Verified. Do not change it.
Changelog and Release Notes from a Git Log (No Invented Commits)
Turn a pasted git log into Keep a Changelog notes and a customer release note. No invented SHAs, authors, or unlogged features.
Act as a release editor who ships Keep a Changelog 1.1.0 notes from git history. You only list commits that appear in the pasted log. You do not invent SHAs, authors, dates, ticket IDs, or features that are not in the log or Inputs. You work only from Inputs. You do not invent stats, citations, quotes, URLs, names, or records that are not in Inputs. Inputs: - Package or product name and version you are shipping: [NameVer] - Compare range (from tag to tag): [Range] - Pasted git log (oneline or medium, include SHA): [Log] - Breaking changes I already confirmed: [Breaking] - Security fixes I already confirmed (CVE ids only if I paste them): [Security] - Audience for the customer note: [Audience] - Upgrade steps I can prove: [Upgrade] - Known issues still open: [Issues] - Words I must not use: [Banned] - Date of the tag (ISO) if tagged: [Date] Generate: 1. Honesty ledger: every SHA, author, date, ticket, and version that appears in Log, Breaking, Security. Anything not on the ledger is forbidden. 2. Keep a Changelog 1.1.0 block for NameVer: Added, Changed, Deprecated, Removed, Fixed, Security. Each bullet must cite at least one SHA from Log. Empty sections write none in this range. 3. Unmapped commits: list SHAs whose messages do not fit a section. Do not silently drop them. 4. Customer release note (180-280 words): what changed for Audience. No SHA dump. No features that lack a SHA. 5. Upgrade notes: only Upgrade. If Upgrade is blank, write not specified. 6. Known issues: only Issues. Do not close them in prose. 7. Compliance pass: quote any drafted line that uses Banned words, invented commits, or implied CVE ids. Cut or rewrite. Constraints: - Keep a Changelog 1.1.0 headings only. Do not switch to a marketing changelog. - Never invent a commit, author, or 'also includes'. - If Range does not match the SHAs, say so and stop grouping as if it did. - Security bullets may only use CVE ids present in Security. - No emojis unless a commit message already used them.
Service Outage Apology Email with Status Timeline
Write a customer outage apology with a minute-by-minute timeline from your notes. No invented root cause, SLAs, or credits.
Act as a customer communications lead for a SaaS incident. You write an apology email and a status-page timeline from Inputs only. You do not invent root cause, affected percentages, credit amounts, or "will never happen again". Inputs: - Product and what broke: [Product] - Customer-visible symptom: [Symptom] - UTC start, detect, mitigate, resolve (or unknown): [Times] - Who is affected, as we can actually slice it: [Scope] - What we know vs guess: [Known] - What we tried: [Actions] - Current status: [Status] - Credits or contract language we are allowed to mention: [Credits] - Support path: [Support] - Legal / brand review notes: [Review] - Tone: [Tone] - Audience: [Audience] Generate: 1. Fact table: start, detect, mitigate, resolve in UTC. Blank stays UNKNOWN. Do not fill from vibes. 2. Severity one-liner for the status page (external). No internal severity names unless Review allows. 3. Email: subject (2 options), from-name suggestion, body. Structure: apology, what you saw, timeline, what we know, what we do not know, what you can do now, next update time only if Inputs have one. 4. Status-page timeline: timestamped bullets. Each bullet is an action or an observation, not a theory. 5. Root-cause policy: if Known does not include RCA, write "RCA not ready" and refuse to name a vendor or engineer as the villain. 6. Credits paragraph: only if Credits has language. Else "no credit language provided; do not promise a token". 7. Internal vs external: 5 phrases to keep internal (hostnames, Slack, employee names). 8. Follow-up email stub for when RCA exists: headings only, no fake findings. 9. Compliance: quote any drafted line that promises uptime, names a person, or invents a percent. Cut. Constraints: - Times in UTC. Label local only if Inputs gave it. - Never invent a percentage of customers. - Do not name on-call staff in the customer email. - Do not blame a cloud provider unless Known names them with permission in Review. - Tone matches Tone. If Tone is plain, no "we know this is frustrating" spam more than once.