RFC/XML is for STRUCTURE, not COMMUNICATION
RFC 2119 keywords and XML tags are for structuring agent prompts, skill definitions, and internal documentation ONLY.
Files MUST NOT be modified such that agents would:
- Speak to users using RFC keywords ("You MUST provide a file path")
- Output XML tags in their responses to users
- Adopt a formal/robotic communication style
Refactored files SHOULD make agents BEHAVE correctly, not SPEAK formally.
NO RFC Boilerplate
You MUST NOT add any RFC 2119 preamble or boilerplate text to files. Models already know what RFC keywords mean. Adding a preamble wastes tokens and clutters the file.
Read the full style guide reference before applying any transformations:
- Style Guide: references/style-guide.md — RFC 2119 keyword definitions, XML tag catalog, naming conventions, nesting rules, and combined patterns
Applying RFC+XML to a file
- Read the file and identify its type (skill, prompt template, system prompt, workflow doc)
- Identify sections that map to XML tags (instructions, workflows, examples, constraints, etc.)
- Identify requirement-level language that SHOULD use RFC keywords
- Apply XML tags to wrap logical sections — use consistent naming, max 3-4 nesting levels
- Apply RFC 2119 keywords — convert casual requirement language to proper keywords
- Preserve YAML frontmatter, code blocks, links, and original intent exactly as-is
- Verify XML is well-formed (proper nesting, all tags closed)
- Verify RFC keywords are used appropriately (not overused, not in user-facing output)
1---2name: rfc-xml-style3description: RFC 2119 keywords and XML tag structure guide for agent prompts, skill definitions, and internal documentation. Use when writing, reviewing, or refactoring markdown files that instruct AI agents — including skills, prompt templates, system prompts, and workflow docs. Provides keyword semantics, XML tag catalog, nesting best practices, and before/after examples. Examples: - user: "Refactor this skill to use RFC keywords" → apply RFC 2119 keyword conventions - user: "Add XML structure to this prompt" → wrap sections in semantic XML tags - user: "Review my SKILL.md formatting" → audit RFC keyword usage and XML structure - user: "Convert this doc to RFC+XML style" → full transformation with style guide - user: "/refactor-rfc-xml ./prompts" → batch refactor all markdown in a folder4---56<overview>7Authoritative reference for structuring agent-facing documentation with RFC 2119 requirement-level keywords and semantic XML tags. Covers keyword definitions, XML tag catalog, naming conventions, nesting rules, and combined usage patterns.8</overview>910<constraints>1112## RFC/XML is for STRUCTURE, not COMMUNICATION1314RFC 2119 keywords and XML tags are for structuring agent prompts, skill definitions, and internal documentation ONLY.1516Files MUST NOT be modified such that agents would:17- Speak to users using RFC keywords ("You MUST provide a file path")18- Output XML tags in their responses to users19- Adopt a formal/robotic communication style2021Refactored files SHOULD make agents BEHAVE correctly, not SPEAK formally.2223## NO RFC Boilerplate2425You MUST NOT add any RFC 2119 preamble or boilerplate text to files. Models already know what RFC keywords mean. Adding a preamble wastes tokens and clutters the file.2627</constraints>2829<instructions>3031Read the full style guide reference before applying any transformations:3233- **Style Guide**: [references/style-guide.md](references/style-guide.md) — RFC 2119 keyword definitions, XML tag catalog, naming conventions, nesting rules, and combined patterns3435</instructions>3637<workflow>3839## Applying RFC+XML to a file40411. Read the file and identify its type (skill, prompt template, system prompt, workflow doc)422. Identify sections that map to XML tags (instructions, workflows, examples, constraints, etc.)433. Identify requirement-level language that SHOULD use RFC keywords444. Apply XML tags to wrap logical sections — use consistent naming, max 3-4 nesting levels455. Apply RFC 2119 keywords — convert casual requirement language to proper keywords466. Preserve YAML frontmatter, code blocks, links, and original intent exactly as-is477. Verify XML is well-formed (proper nesting, all tags closed)488. Verify RFC keywords are used appropriately (not overused, not in user-facing output)4950</workflow>5152<quality-checklist>5354- [ ] XML is well-formed (proper nesting, all tags closed)55- [ ] RFC keywords used appropriately (not overused)56- [ ] Frontmatter preserved exactly57- [ ] Code blocks and their content untouched58- [ ] Files remain readable and clear59- [ ] Tags enhance structure, don't obscure content60- [ ] NO RFC/XML leakage into agent communication style61- [ ] Agents still speak naturally to users6263</quality-checklist>6465<examples>66<example type="correct">67Internal instruction: "The agent MUST verify file exists before editing"68</example>69<example type="wrong">70User-facing output: "I MUST inform you that the file does not exist"71</example>72<example type="correct">73Internal structure: `<workflow>1. Check permissions 2. Edit file</workflow>`74</example>75<example type="wrong">76User-facing output: `<response>File has been edited</response>`77</example>78</examples>
jal-co