✍️ Writing
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.
0Reviews
Prompt
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.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Spec: Harbor Desk Status Line. User agents MAY render a one-sentence guest-facing status from a pasted ticket note. User agents MUST NOT print a last name. User agents SHOULD omit medical advice. This section does not define a JSON schema. Section: 3.2 Status Line as pasted Name: Harbor Desk Notes Module, Editor's Draft date UNKNOWN Banned: errata ID invent, MUST upgrade, RFC 9110 invent, browser already ships this Never: invent errata, invent a JSON schema, promote MAY to MUST, invent section 3.3 Format: banner + ledger + quotes + explainer + refuse Lang: English Audience: Harbor Desk implementers who did not write the spec Normative: MAY, MUST NOT, SHOULD as pasted Not: not errata, not a bug report, not legal advice, not an IETF RFC
Example Output
1. Banner. Not errata. Not a bug report. Not legal advice. Not an IETF RFC. Explainer of pasted W3C-style section text only. 2. Ledger. Name: Harbor Desk Notes Module, Editor's Draft date UNKNOWN. Section: 3.2 Status Line as pasted. Audience: Harbor Desk implementers who did not write the spec. Lang English. RFC2119 in paste: MAY, MUST NOT, SHOULD. JSON schema explicitly not defined. Forbidden: errata ID invent, MUST upgrade, RFC 9110 invent, browser already ships this, invented errata, invented JSON schema, MAY to MUST, invented section 3.3. 3. Quote map. Q1 'User agents MAY render a one-sentence guest-facing status from a pasted ticket note.' Q2 'User agents MUST NOT print a last name.' Q3 'User agents SHOULD omit medical advice.' Q4 'This section does not define a JSON schema.' 4. Plain explainer. Section 3.2 Status Line (pasted heading). An implementation is allowed (MAY) to show one sentence on the guest-facing board from a pasted ticket note. It is required not to print a last name (MUST NOT). It is recommended to omit medical advice (SHOULD). A JSON schema is not defined here; do not invent one. MAY is not upgraded to MUST. Date of the draft is UNKNOWN. 5. Out of scope. Section 3.3 NOT IN PASTE. Error handling algorithm NOT IN PASTE. IETF RFC number NOT IN PASTE. 6. Refuse. Errata ID: refused. RFC 9110 invent: refused. 'Browsers already ship this': refused. JSON schema: refused. 7. Never. No MAY to MUST. No invented 3.3. 8. Compliance. Banned hits none in explainer. Normative words kept as pasted. Format banner+ledger+quotes+explainer+refuse. Gaps: spec date, URL, extra sections, test suite, which UA is in scope. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.