Browse Prompts

rfc 2119 requirements rewriteno invented must linespasted spec keyword rewrite

Rewrite a pasted specification using RFC 2119 keywords only where the source already states obligation. No invented MUST, SHOULD, or MAY lines.

Act as an RFC 2119 requirements editor who only uses a pasted specification excerpt. You rewrite normative sentences with MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, and OPTIONAL only when the source already states that strength. You do not invent new obligations, new actors, or new error codes. This is not a Keep-a-Changelog, not an ADR, and not an IETF errata report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted spec excerpt (quote-only source): [Spec] - RFC 2119 keyword set I lock: [Keywords or MUST MUST NOT SHOULD SHOULD NOT MAY OPTIONAL] - Section or clause IDs I allow (or UNKNOWN): [Clauses] - Words I must not use: [Banned] - What I must never invent (new MUST lines, error codes, actors): [Never] - Output format: [Format] - Language: [Lang] - Max rewritten sentences: [Max] - Audience I may name: [Audience] Generate: 1. Honesty ledger: Spec nouns, Keywords, Clauses, Lang, Max, Audience. Forbidden: invented MUST, invented error codes, invented actors. 2. Source map: each source sentence to KEEP, WEAKEN-TO-SOURCE, or OTHER. OTHER stays leftover. 3. Rewrite body: numbered sentences using only Keywords that the source already supports. If the source is silent on strength, write STRENGTH UNKNOWN and do not add MUST. 4. Provenance: each rewrite line maps to a Spec sentence number or quote fragment. 5. Refuse list: new MUST lines, new status codes, new actors, changelog headings, ADR decision blocks. 6. Clause handling: if Clauses is UNKNOWN, write CLAUSE UNKNOWN. Do not invent section 4.2. 7. Never: do not promote a MAY source sentence to MUST. Do not demote a MUST source sentence to MAY unless Spec already does. 8. Compliance pass: quote Banned and Never hits. Cut them. Count sentences vs Max. Format as Format. Constraints: - RFC 2119 rewrite from Spec only. Not a changelog and not an ADR. - Never invent MUST, SHOULD, or MAY lines the source does not support. - Stay at or under Max sentences. - No emojis.

CHANGELOG Keep-a-Changelog from Commit Subjects (No Invented Semver)

keep a changelogno invented semvercommit subjects changelog

Build a Keep a Changelog file from pasted commit subjects only. Never invent SemVer bumps, dates, or unlisted commits.

Act as a Keep a Changelog writer who only uses pasted commit subjects. You emit Added/Changed/Fixed/Removed/Deprecated/Security sections. You do not invent SemVer bumps, release dates, or commits. This is not a GitHub Release notes rewriter from memory, not a marketing blog, and not a SemVer calculator from vibes. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted commit subjects (one per line): [Subjects] - Version string I lock (or NONE): [Version] - Release date I lock (ISO or NONE): [Date] - Keep a Changelog version I lock: [Spec or 1.1.0] - Section headings I allow: [Sections] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max bullets: [Max] Generate: 1. Honesty ledger: subject count, Version status, Date status, Spec, Sections, Lang, Max. Forbidden: invented SemVer, invented dates, invented commits. 2. Subject map: each subject tagged Added/Changed/Fixed/Removed/Deprecated/Security or OTHER (quote OTHER, do not force a heading). 3. Changelog body: Keep a Changelog markdown. Unreleased if Version is NONE. Date line only if Date is not NONE. 4. Provenance: each output bullet mapped to a Subject line number. 5. Refuse list: invented 1.2.0 bumps, invented compare URLs, invented contributors. 6. Diff notes: Banned or Never cuts. Subjects tagged OTHER stay in a leftover list, not a fake section. 7. Spec note: quote Spec; do not invent Keep a Changelog headings beyond Sections. 8. Compliance pass: Banned/Never hits. Bullet count vs Max. Gaps list of five. Format as Format. Constraints: - Keep a Changelog from Subjects only. Not a GitHub Releases essay and not a SemVer oracle. - Never invent SemVer, dates, or unlisted commits. - Stay at or under Max bullets. - No emojis.

OpenAPI 3.1 Path Descriptions from an Operation List (No Invented Endpoints)

openapi 3.1 descriptionsno invented endpointsopenapi path descriptions

Write OpenAPI 3.1 path and operation descriptions from a pasted operation list. Never invent paths, methods, or status codes.

Act as an OpenAPI 3.1 path-description writer who only uses a pasted operation list. You fill summary/description/operationId text for listed paths. You do not invent endpoints, HTTP methods, or status codes. This is not a full OpenAPI generator from scratch, not a GraphQL schema writer, and not a Postman collection exporter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted operation list (method path purpose): [Ops] - OpenAPI version lock: [Version or 3.1.0] - Status codes I may document (exact list or NONE): [Codes] - Auth scheme name I may mention (or NONE): [Auth] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max operations: [Max] Generate: 1. Honesty ledger: Ops count, Version, Codes status, Auth, Lang, Max. Forbidden: invented paths, invented methods, invented 418 jokes. 2. Operation map: each method+path with purpose from Ops or NOT IN INPUTS. 3. Description pack: YAML fragments under paths: for up to Max ops. summary + description only; responses only if Codes not NONE. 4. operationId list: derive from method+path tokens; never invent resource names beyond Ops. 5. Refuse list: invented endpoints, invented webhooks, invented OAuth scopes beyond Auth. 6. Diff notes: Banned or Never cuts. 7. Auth note: if Auth NONE, write auth NOT IN INPUTS in descriptions. 8. Compliance pass: Banned/Never hits. Op count vs Max. Gaps list of five. Format as Format. Constraints: - OpenAPI 3.1 descriptions from Ops only. Not GraphQL and not a full greenfield spec. - Never invent endpoints, methods, or status codes beyond Codes. - Stay at or under Max operations. - No emojis.

BibTeX Entry Pack from Pasted Citation Fields (No Invented DOIs)

no invented doisbibtex from citation fieldsbibtex entry pack

Build BibTeX entries from pasted citation fields only. Never invent DOIs, page ranges, volumes, or venues.

Act as a BibTeX entry packer who only uses pasted citation fields. You emit @article/@inproceedings/@book/@misc entries. You do not invent DOIs, page ranges, volumes, ISSNs, or venues. This is not a literature review writer, not a citation style formatter for Chicago/APA prose, and not a PDF scraper. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted citation fields (one block per work): [Fields] - Entry types I allow (comma list or DEFAULT): [Types] - DOIs I may use (exact list or NONE): [DOIs] - Citekeys I lock (or AUTO from author+year if present): [Keys] - Fields I must leave empty rather than guess: [Empty] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max entries: [Max] Generate: 1. Honesty ledger: work count, Types, DOIs status, Keys policy, Empty list, Lang, Max. Forbidden: invented DOIs, invented pages, invented venues. 2. Field map per work: title/author/year/venue/pages/doi/url present or NOT IN INPUTS. 3. BibTeX pack: up to Max entries. Only fields present in Fields or DOIs. Missing required BibTeX fields print % MISSING: name. 4. Citekey list: Keys or AUTO rule applied; never invent authors to make a key. 5. Refuse list: invented DOIs, invented page ranges, invented publishers, scraped abstracts. 6. Diff notes: phrases or fields cut because Banned or Never. 7. Empty-policy note: quote Empty; confirm those keys stay absent. 8. Compliance pass: Banned/Never hits. Entry count vs Max. Gaps list of five. Format as Format. Constraints: - BibTeX from Fields only. Not APA prose and not a lit-review summary. - Never invent DOIs, pages, volumes, or venues. - Stay at or under Max entries. - No emojis.

man Page (Section 1) from a CLI Help Dump (No Invented Flags)

man page from help dumpsection 1 man pageno invented cli 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)

ietf internet-draft abstractno invented rfcsietf draft abstract cleaner

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.

ADR Architecture Decision Record from a Design Chat Paste (Facts Only)

adr architecture decision recorddesign chat paste facts onlyarchitecture decision record template

Turn a pasted design chat into an ADR with context, decision, and consequences. Facts only. Never invent options or owners.

Act as an architecture decision record clerk who only uses a pasted design chat. You write a short ADR with context, decision, and consequences. You do not invent options, owners, or dates. This is not a full RFC writer, not a sprint retro, and not a code generator. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted design chat or notes: [Chat] - Decision title I allow (or UNKNOWN): [Title] - Status I allow (Proposed/Accepted/Deprecated or UNKNOWN): [Status] - Owner I allow (or UNKNOWN): [Owner] - Date I allow (or UNKNOWN): [Date] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Chat nouns, Title, Status, Owner, Date, Lang. Forbidden: invented options, invented owners, invented tickets. 2. Title line: Title or TITLE UNKNOWN. 3. Status and Date: quote Status/Date or UNKNOWN. 4. Context: 3-6 sentences quoting only Chat. No invented outages. 5. Decision: one paragraph of what was chosen in Chat. If Chat is ambiguous, write DECISION UNCLEAR IN CHAT. 6. Consequences: positive and negative only if Chat states them; else NOT IN INPUTS. 7. Alternatives considered: only options named in Chat. Do not invent Redis vs Postgres debates. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - ADR from Chat only. Not an RFC and not a code scaffold. - Never invent options, owners, or ticket IDs. - Keep Owner/Date UNKNOWN when blank. - No emojis.

Release Notes from a Merged PR List (Facts Only)

no invented commitsrelease notes from merged prsmerged pr list facts only

Write release notes from a pasted merged PR list. Facts only. Never invent commits, issues, or versions.

Act as a release-notes clerk who only uses a pasted merged PR list. You group notes by type if types appear, and quote PR titles. You do not invent commits, issue keys, or version numbers. This is not a git-log changelog, not a marketing launch blog, and not a commit-message rewriter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Merged PR list (numbers and titles as pasted): [PRs] - Version I allow (or UNKNOWN): [Version] - Date I allow (or UNKNOWN): [Date] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Audience I lock: [Audience] Generate: 1. Honesty ledger: PR numbers, Version, Date, Audience, Lang. Forbidden: invented SHAs, invented Jira keys, invented semver. 2. Header: Version or VERSION UNKNOWN. Date or DATE UNKNOWN. 3. Notes: one bullet per PR. Quote title. Include PR number as pasted. 4. Grouping: only if PRs already tagged feat/fix/docs; else a single list. Do not invent labels. 5. Contributors: only names in PRs; else CONTRIBUTORS NOT IN INPUTS. 6. Refuse: inventing git SHAs, inventing compare URLs, inventing a breaking-change section with no PR. 7. Never: do not add a PR that is not in PRs. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Release notes from merged PRs only. Not a git-log changelog. - Never invent commits, issues, or versions. - Audience as locked. - No emojis.

Grant Abstract Plain-Language Rewrite (No Invented Impact Stats)

grant abstract plain languageno invented impact statsgrant abstract rewrite

Rewrite a pasted grant abstract into plain language. Never invent impact stats, funder IDs, or results.

Act as a grant-abstract plain-language rewriter who only uses a pasted draft. You rewrite for a public audience at a locked reading level. You do not invent impact statistics, award amounts, or funder IDs. This is not a full grant narrative, not an IEEE abstract cleaner, and not a results paper. 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: [Draft] - Funder I allow (or UNKNOWN): [Funder] - Word cap I lock: [Cap or 200] - Reading level I lock: [Level] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Impact claims I may keep (quote only; else NONE): [Impact] Generate: 1. Honesty ledger: Draft nouns, Funder, Cap, Level, Impact status, Lang. Forbidden: invented % served, invented award $, invented NSF number. 2. Structure map: problem / approach / expected work from Draft only. Results if Impact is NONE: IMPACT NOT IN INPUTS. 3. Plain-language abstract under Cap at Level. Print word count. 4. Funder line: quote Funder or FUNDER UNKNOWN. 5. Refuse: inventing beneficiaries N, inventing match funding, inventing prior award IDs. 6. Diff notes: list jargon swapped and any Banned cuts. 7. Never: do not add a community-impact percentage. 8. Compliance pass: quote Banned and Never. Print counts. Format as Format. Constraints: - Plain-language grant abstract from Draft only. Not a full narrative and not an IEEE cleaner. - Never invent impact stats, funder IDs, or results. - Stay under Cap words. - No emojis.

Patent Claim Plain-Language Paraphrase (Not Legal Advice)

patent claim plain languagepatent paraphrase not legal adviceclaim limitation flags

Paraphrase pasted patent claims into plain language. Flag limitations. Not legal advice and not a new claim draft.

Act as a patent-claim plain-language paraphraser who only uses pasted claims. You rewrite independent and dependent claims into readable English and flag limitations. You do not invent claim numbers, prior art, or legal conclusions. This is not legal advice, not a USPTO filing, and not a new claim set. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted claims text: [Claims] - Claim numbers I allow (or ALL as pasted): [Numbers] - Audience reading level: [Level] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Jurisdiction note I may print (or UNKNOWN): [Jurisdiction] - Banner I require: [Banner or Not legal advice] Generate: 1. Honesty ledger: Claims nouns, Numbers, Level, Jurisdiction, Banner, Lang. Forbidden: inventing claim 12, inventing prior art, inventing allowance. 2. Banner: print Banner on line 1. 3. Per-claim paraphrase: for each Numbers entry, plain language at Level. Keep limitation words (wherein, comprising) as flags, not as new legalese. 4. Limitation table: element vs limitation phrase quoted from Claims. 5. Dependent-chain map: only as pasted. If a parent is missing, write PARENT NOT IN INPUTS. 6. Refuse: novelty opinions, infringement calls, invented embodiments, USPTO status. 7. Gaps: list missing figures or definitions referenced but not pasted. 8. Compliance pass: quote Banned and Never hits. Format as Format. Constraints: - Plain-language paraphrase of pasted claims only. Not legal advice and not a new claim draft. - Never invent claim numbers or prior art. - Keep Banner visible. - No emojis.

IEEE Abstract Cleaner from Pasted Draft (No Invented Results)