Browse Prompts

82 prompts available in writing ยท Page 3 of 7

Grant Narrative Sections from Locked Outcomes (No Invented Metrics)
โœ๏ธ Writing

Grant Narrative Sections from Locked Outcomes (No Invented Metrics)

PpromptstudioยทSep 2, 2026
No rating

Build grant narrative sections from locked outcomes. No invented metrics, dollar amounts, or impact stats.

Act as an editor for this job: Grant Narrative Sections from Locked Outcomes (No Invented Metrics). Goal: Build grant narrative sections from locked outcomes. No invented metrics, dollar amounts, or impact stats. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Grant Narrative Sections from Locked Outcomes (No Invented Metrics). - No invented evidence. Honor Cap. No emojis.

grant narrativelocked outcomesmetrics lock
Privacy Policy Diff Notes from Two Policy Versions (No Invented Clauses) with example still
โœ๏ธ Writing

Privacy Policy Diff Notes from Two Policy Versions (No Invented Clauses) with example still

PpromptstudioยทSep 2, 2026
No rating

Compare two pasted privacy policy versions and draft diff notes. No invented clauses or legal advice.

Act as an editor for this job: Privacy Policy Diff Notes from Two Policy Versions (No Invented Clauses). Goal: Compare two pasted privacy policy versions and draft diff notes. No invented clauses or legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Privacy Policy Diff Notes from Two Policy Versions (No Invented Clauses). - No invented evidence. Honor Cap. No emojis.

privacy policydiff notescompliance
Technical White Paper Outline from Claims Pack (No Invented Citations) with example still
โœ๏ธ Writing

Technical White Paper Outline from Claims Pack (No Invented Citations) with example still

PpromptstudioยทSep 2, 2026
No rating

Build a technical white paper outline from a locked claims pack. No invented citations, DOIs, or study results.

Act as an editor for this job: Technical White Paper Outline from Claims Pack (No Invented Citations). Goal: Build a technical white paper outline from a locked claims pack. No invented citations, DOIs, or study results. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Technical White Paper Outline from Claims Pack (No Invented Citations). - No invented evidence. Honor Cap. No emojis.

white paperclaims packcitations lock
โœ๏ธ Writing

APA 7 Reference Cleaner from Pasted Citations (No Invented DOIs)

PpromptstudioยทSep 1, 2026
No rating

Clean pasted citations into APA 7 reference lines. No invented DOIs, years, or page ranges.

Act as an APA 7 reference editor who only uses pasted citation strings. You emit cleaned reference lines the pasted strings already support. You do not invent DOIs, years, volumes, issues, or page ranges. This is not a plagiarism checker and not a source finder. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted citations I lock: [Cites] - Style edition I lock: [Edition] - Item cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (DOIs, years, pages, extra sources): [Never] - Output format: [Format] - Language: [Lang] - Retrieval date I may quote (or NONE): [Retrieved] Generate: 1. Honesty ledger: Cites nouns, Edition, Cap, Retrieved, Lang. Forbidden: invented DOIs, years, pages, extra sources. 2. Cleaned list: at most Cap APA 7 lines. Missing elements write NOT IN INPUTS in place. 3. Element table per item: author, year, title, source, DOI. Empty cells stay NOT IN INPUTS. 4. Hanging-indent note and alphabetization using only names present in Cites. 5. Refuse list: inventing doi.org strings, inventing 2020, inventing pp. 1-20, adding a source not in Cites. 6. Compliance pass: quote Banned and Never hits. Cut them. Print item count. Format as Format. Constraints: - APA 7 lines from Cites only. No invented DOIs. - Honor Edition and Cap. - No emojis.

no invented doisapa 7reference cleaner
โœ๏ธ Writing

USCIS Cover Letter Checklist from a Form Inventory (No Invented Evidence)

PpromptstudioยทSep 1, 2026
No rating

Draft a USCIS cover letter checklist from a form inventory only. No invented evidence, receipt numbers, or eligibility claims.

Act as an immigration paperwork organizer who only uses a pasted form inventory. You write a cover-letter checklist the inventory already supports. You do not invent evidence, receipt numbers, eligibility, or statutory cites. This is not legal advice and not a representation that a filing will be approved. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Form inventory I lock (form numbers and copies on hand): [Inventory] - Packet purpose I lock (or UNKNOWN): [Purpose] - Exhibit cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (evidence, receipt numbers, eligibility, statutes): [Never] - Output format: [Format] - Language: [Lang] - Applicant name I may quote (or REDACTED): [Name] Generate: 1. Honesty ledger: Inventory nouns, Purpose, Cap, Name, Lang. Forbidden: invented evidence, receipts, eligibility, statutes. Banner: not legal advice; not a filing guarantee. 2. Cover-letter outline: greeting, purpose quote or UNKNOWN, enclosed-forms list from Inventory only. 3. Exhibit checklist: at most Cap lines. Missing exhibits write NOT IN INPUTS rather than adding documents. 4. Gaps table: forms named without copy counts, IDs, translations, photos. Empty cells stay NOT IN INPUTS. 5. Refuse list: inventing I-797 receipts, inventing INA cites, inventing a birth certificate, inventing approval odds. 6. Compliance pass: quote Banned and Never hits. Cut them. Print exhibit count. Format as Format. Constraints: - Checklist from Inventory only. No invented evidence. - Not legal advice. Honor Cap. - No emojis.

uscis cover letterform inventoryno invented evidence
โœ๏ธ Writing

KDP Book Description + Allowed HTML from a Facts Pack (No Invented Reviews)

PpromptstudioยทSep 1, 2026
No rating

Draft a KDP book description and allowed HTML from a facts pack only. No invented reviews, rankings, or reader quotes.

Act as a Kindle Direct Publishing description editor who only uses a pasted facts pack. You write a plain description and an allowed-HTML version the facts already support. You do not invent reviews, star ratings, bestseller ranks, or reader quotes. This is not a full manuscript ghostwriter and not a ranking predictor. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Facts pack I lock (title, genre, premise, audience, features): [Facts] - Allowed HTML tags I lock: [Html] - Character cap I lock: [Cap] - Bullet count I lock: [Count] - Words I must not use: [Banned] - What I must never invent (reviews, ranks, quotes, awards): [Never] - Output format: [Format] - Language: [Lang] - Series name I may quote (or NONE): [Series] Generate: 1. Honesty ledger: Facts nouns, Html, Cap, Count, Series, Lang. Forbidden: invented reviews, ranks, quotes, awards. 2. Plain description at or under Cap. Print character count. Premise and features from Facts only. 3. Allowed HTML version using only tags in Html. Print character count. No extra tags. 4. Feature bullets: exactly Count from Facts. Extra claims write NOT IN INPUTS. 5. Refuse list: inventing 4.8 stars, inventing Amazon charts, inventing Kirkus quotes, inventing awards. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - KDP description from Facts only. No invented reviews. - Use only Html tags. Honor Cap and Count. - No emojis.

no invented reviewskdp descriptionallowed html
โœ๏ธ Writing

OpenAPI Changelog from Two Spec Snippets (No Invented Endpoints)

PpromptstudioยทSep 1, 2026
No rating

Diff two pasted OpenAPI snippets into a human changelog. No invented paths, schemas, or status codes.

Act as an API docs editor who only diffs two pasted OpenAPI snippets. You list Added, Changed, Deprecated, and Removed paths and schemas the snippets already show. You do not invent endpoints, status codes, or auth schemes. This is not a full OpenAPI generator and not a marketing release note. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Old OpenAPI snippet I lock: [Old] - New OpenAPI snippet I lock: [New] - API name I may name (or UNKNOWN): [Api] - Version labels I may name (or UNKNOWN/UNKNOWN): [Labels] - Words I must not use: [Banned] - What I must never invent (paths, schemas, status codes, auth): [Never] - Output format: [Format] - Language: [Lang] - Max bullets per section I lock: [Max] Generate: 1. Honesty ledger: Api, Labels, path nouns seen in Old and New, Max, Lang. Forbidden: invented paths, schemas, status codes. 2. Diff table: path or schema -> Added|Changed|Deprecated|Removed|Unchanged with evidence quotes from snippets only. 3. Changelog: sections with at most Max bullets. Quote path strings exactly. Missing detail write NOT IN INPUTS. 4. Unchanged note: list Unchanged or write NONE. 5. Refuse list: inventing /v2/users, inventing 429 tables, inventing OAuth scopes, writing SDKs. 6. Compliance pass: quote Banned and Never hits. Cut them. Print bullet counts. Format as Format. Constraints: - OpenAPI changelog from Old and New only. - Never invent endpoints or status codes. - Honor Max. - No emojis.

no invented endpointsopenapi changelogspec diff
โœ๏ธ Writing

SemVer Keep a Changelog Release Notes from Merged PR Titles (No Invented Versions)

PpromptstudioยทSep 1, 2026
No rating

Draft Keep a Changelog style release notes from merged PR titles only. No invented SemVer bumps or ghost PRs.

Act as a release-notes editor who only uses a pasted list of merged PR titles. You group Added, Changed, Fixed, and Removed sections in Keep a Changelog style. You do not invent SemVer numbers, dates, authors, or PRs that are not in Inputs. This is not a marketing changelog and not a commit inventer. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Merged PR titles I lock (one per line, optional #id): [Titles] - Version I may name (or UNKNOWN): [Version] - Date I may name (or UNKNOWN): [Date] - Product name I may name (or UNKNOWN): [Product] - Words I must not use: [Banned] - What I must never invent (SemVer bumps, ghost PRs, metrics, authors): [Never] - Output format: [Format] - Language: [Lang] - Section order I lock: [Order] - Unmapped titles policy (keep Uncategorized or ask): [Unmapped] Generate: 1. Honesty ledger: Title count, Version, Date, Product, Order, Lang. Forbidden: invented SemVer, ghost PRs, authors, metrics. 2. Classification table: each title -> Added|Changed|Fixed|Removed|Uncategorized with a one-line reason from the title nouns only. 3. Keep a Changelog draft: ## [Version] - Date (or UNKNOWN). Sections in Order. Bullets quote title nouns. No invented detail. 4. Unmapped: list Uncategorized titles or write NONE. Honor Unmapped policy. 5. Refuse list: inventing v2.0.0, inventing PR #999, inventing download counts, writing a press release. 6. Never: do not mint authors. Do not invent compare links. 7. Compliance pass: quote Banned and Never hits. Cut them. Print bullet counts per section. Format as Format. Constraints: - Keep a Changelog from Titles only. No invented SemVer. - Honor Version and Date or write UNKNOWN. - No emojis.

keep a changelogno invented semvermerged pr titles
โœ๏ธ Writing

MkDocs nav.yml and Page Stub from a Locked Page List (No Invented nav Entries)

PpromptstudioยทAug 29, 2026
No rating

Draft an MkDocs nav.yml and a matching page stub from a locked page list. No invented nav entries, slugs, or include paths.

Act as an MkDocs nav.yml and page-stub editor who only uses a pasted locked page list. You write nav.yml keys and one Markdown stub whose titles and paths the list already names. You do not invent nav entries, extra slugs, or include paths. This is not a Sphinx RST page, not an Antora nav.adoc, and not a DITA map. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Page list I lock (titles, paths, section labels I allow): [Pages] - Fact pack I may quote: [Facts] - MkDocs version I lock (or UNKNOWN): [Version] - Theme I lock (or UNKNOWN): [Theme] - Words I must not use: [Banned] - What I must never invent (nav entries, slugs, include paths): [Never] - Output format: [Format] - Language: [Lang] - Max stub paragraphs: [Max] - Audience I may name: [Audience] Generate: 1. Honesty ledger: Pages titles and paths, Facts nouns, Version, Theme, Lang, Max, Audience. Forbidden: invented nav, invented slug, invented include. 2. Path map: each Pages path to KEEP. Paths not in Pages stay leftover OTHER. Do not mint docs/install.md. 3. nav.yml: keys only from Pages. Nested sections only if Pages named them. Theme from Theme or THEME UNKNOWN. 4. Page stub: title from Pages. Paragraphs quote Facts or write NOT IN INPUTS. Stay at or under Max body paragraphs. 5. Refuse list: Sphinx toctree, Antora nav.adoc, DITA map, extra mkdocs.yml plugins not in Inputs. 6. Version: quote Version or write VERSION UNKNOWN. 7. Never: do not add a nav item for a page not in Pages. Do not invent a GitHub Pages URL. 8. Compliance pass: quote Banned and Never hits. Cut them. Count stub paragraphs vs Max. Format as Format. Constraints: - MkDocs nav.yml and stub from Pages and Facts only. Not Sphinx and not Antora. - Never invent nav entries, slugs, or include paths. - Stay at or under Max body paragraphs. - No emojis.

mkdocs nav.yml stublocked page listno invented nav entries
โœ๏ธ Writing

Pandoc Markdown to DOCX Style Map from a Template Brief (No Invented Styles)

PpromptstudioยทAug 29, 2026
No rating

Write a Pandoc Markdown-to-DOCX style map from a template brief. No invented style names or reference-doc paths.

Act as a Pandoc Markdown-to-DOCX style-map editor who only uses a pasted template brief. You map Markdown elements to Word styles the brief already names. You do not invent style names, reference-doc paths, or extra Lua filters. This is not a Sphinx RST page, not an AsciiDoc chapter, and not a DITA stub. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Template brief I lock (Markdown elements, Word styles I allow): [Brief] - Reference-doc path I lock (or NONE): [RefDoc] - Pandoc version I lock (or UNKNOWN): [Version] - Words I must not use: [Banned] - What I must never invent (style names, reference-doc paths, Lua filters): [Never] - Output format: [Format] - Language: [Lang] - Filters I allow (or NONE): [Filters] - Output file name I lock (or UNKNOWN): [Out] Generate: 1. Honesty ledger: Brief pairs, RefDoc, Version, Filters, Out, Lang. Forbidden: invented styles, invented paths, extra filters. 2. Style map table: each Brief Markdown element to the Word style named beside it. Unnamed elements stay STYLE UNKNOWN. 3. Command sketch: pandoc from Version or VERSION UNKNOWN. --reference-doc only if RefDoc is not NONE. -o from Out or OUT UNKNOWN. 4. Filters: quote Filters or write NONE. Do not invent filters/styles.lua. 5. Refuse list: Sphinx conf.py, AsciiDoc :stylesheet:, DITA ditaval, invented Heading 3 if Brief omitted it. 6. RefDoc: quote RefDoc or write NONE. 7. Never: do not mint a style named Quote Intense. Do not invent /templates/ref.docx. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Pandoc style map from Brief only. Not Sphinx and not AsciiDoc. - Never invent style names, reference-doc paths, or extra filters. - Command flags only from Inputs. - No emojis.

pandoc markdown docx style maptemplate brief lockno invented styles
โœ๏ธ Writing

reStructuredText Sphinx Page from a TOC Stub (No Invented toctree or Labels)

PpromptstudioยทAug 29, 2026
No rating

Draft a Sphinx RST page from a locked TOC stub. No invented toctree entries, labels, or include paths.

Act as a Sphinx reStructuredText page editor who only uses a pasted TOC stub and fact pack. You write one .rst page with section titles and labels the stub already names. You do not invent toctree entries, :ref: targets, or include paths. This is not an AsciiDoc chapter, not a DITA topic, and not a Markdown dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - TOC stub I lock (page title, section titles, labels I allow): [Stub] - Fact pack I may quote: [Facts] - Sphinx / docutils version I lock (or UNKNOWN): [Version] - toctree glob I allow (or NONE): [Toctree] - Words I must not use: [Banned] - What I must never invent (toctree entries, labels, include paths): [Never] - Output format: [Format] - Language: [Lang] - Max body paragraphs: [Max] - Audience I may name: [Audience] Generate: 1. Honesty ledger: Stub titles, labels, Facts nouns, Version, Toctree, Lang, Max, Audience. Forbidden: invented toctree, invented label, invented include. 2. Label map: each Stub label to KEEP. Labels not in Stub stay leftover OTHER. Do not mint .. _new-label:. 3. Page body: title from Stub. Sections only from Stub. Paragraphs quote Facts or write NOT IN INPUTS. 4. Cross-refs: :ref: only to labels in Stub. If a needed target is missing, write REF UNKNOWN. 5. Refuse list: AsciiDoc = heading, DITA <topic>, Markdown # headings, toctree of a page not in Toctree. 6. toctree: quote Toctree or write NONE. Do not invent install.rst. 7. Never: do not add a footnote with a DOI. Do not invent .. include:: paths. 8. Compliance pass: quote Banned and Never hits. Cut them. Count body paragraphs vs Max. Format as Format. Constraints: - Sphinx RST page from Stub and Facts only. Not AsciiDoc and not Markdown. - Never invent toctree entries, labels, or include paths. - Stay at or under Max body paragraphs. - No emojis.

sphinx rst pageno invented toctreetoc stub lock
โœ๏ธ Writing

DITA Topic Stub from a Concept Brief (No Invented xrefs or Keys)

PpromptstudioยทAug 29, 2026
No rating

Draft a DITA topic stub from a concept brief. No invented xrefs, keys, or conrefs.

Act as a DITA topic-stub editor who only uses a pasted concept brief. You write one concept, task, or reference topic using IDs the brief already names. You do not invent xref hrefs, keyref names, or conref paths. This is not AsciiDoc, not DocBook, and not Markdown. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Concept brief (title, shortdesc facts, IDs I allow): [Brief] - Topic type I lock (concept, task, reference): [Type] - DITA version I lock (or UNKNOWN): [Version] - Keys I allow (or NONE): [Keys] - Words I must not use: [Banned] - What I must never invent (xrefs, keys, conrefs): [Never] - Output format: [Format] - Language: [Lang] - Max body paragraphs: [Max] - Audience I may name: [Audience] Generate: 1. Honesty ledger: Brief title, IDs, Type, Version, Keys, Lang, Max, Audience. Forbidden: invented xref, keyref, conref. 2. ID map: each Brief ID to KEEP. Other IDs stay OTHER leftover. 3. Topic stub: xml prolog optional. id from Brief. shortdesc from Brief facts only. 4. Links: xref only to IDs in Brief. If missing, write XREF UNKNOWN. 5. Refuse list: AsciiDoc xref:, Markdown [](), DocBook <olink>, invented keydef. 6. Keys: quote Keys or write NONE. Do not mint product-name. 7. Never: do not add conref to a map not named. Do not invent id='topic-99'. 8. Compliance pass: quote Banned and Never hits. Cut them. Count body paragraphs vs Max. Format as Format. Constraints: - DITA stub from Brief only. Not AsciiDoc and not Markdown. - Never invent xrefs, keys, or conrefs. - Stay at or under Max body paragraphs. - No emojis.

dita topic stubconcept brief lockno invented xrefs or keys