Medication Aide

Here's a thinking process: 1. **Analyze User Input:** - The user provides a job posting fragment with sections: "Role", "Responsibilities", "Qualifications & Skills" - They want me to reformat it into clean, well-structured semantic HTML - They provided specific rules: use `

` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule), use `

• ` for lists, `

  ` for prose - Don't repeat job title as heading (page already shows it) - Don't put Job ID / requisition numbers as headings - Preserve ALL substantive information; don't invent or summarize away detail - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Identify the Content:** Looking at the input: - "Role: Certified Medication Aide" -> This is the job title. Rule: "Do NOT repeat the job title as a heading (the page already shows it)". So I should NOT create an "About the role" or "Role" heading with this content. I need to decide how to handle it. The input has "Role: Certified Medication Aide". I could either drop it entirely (since the page already shows the title) or maybe fold it into a brief intro paragraph? The rules say: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say I can't include it as prose, but it also says "Remove... duplicated lines". Since the page already shows the title, I should probably not output a heading for it, and maybe not repeat the title text either unless it's needed. I'll treat the "Role:" line as metadata to be dropped or folded minimally. Actually, looking at the rules: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So I can fold it into a short

  or drop it. I think dropping it is fine since the heading structure will start from Responsibilities/Qualifications etc. But the user might expect the content to be structured. I'll check the sections they want: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So the expected headings are examples. I need to pick which sections have real content. Let's map the input to potential sections: - "Role: Certified Medication Aide" -> Job title. Not a section heading per rules. Fold into

  or drop. I'll drop it or maybe put it in a minimal intro, but rules say "Prefer a few substantive sections over many thin ones" and "never emit a heading followed by filler/placeholder text". So if I don't have substantial content for "About the role", I shouldn't create that heading. I'll just start with Responsibilities since that has content. - "Responsibilities" section has content: list of duties. Should use `

  • `. - "Qualifications & Skills" section has content: list of qualifications/skills. Should use `
    • `. The input has: Responsibilities: - Safely administer medications under nurse supervision - Monitor and report resident responses - Accurately document treatments and care activities - Assist residents with daily living activities - Promote resident comfort, dignity, and well-being - Maintain infection control and safety standards - Contribute to a team-focused, faith- and values-based environment - Provide person-centered care to enhance quality of life and support recovery - Grow clinical skills through ongoing engagement Qualifications & Skills: - Certification as a Medication Aide - Knowledge of medication administration and safety protocols - Strong observation and reporting skills - Ability to work collaboratively within a team - Commitment to resident-centered care and safety standards There's no content for Benefits, Pay, Schedule, etc. Rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." and "include a section ONLY when the posting has real, specific content for it". So I should NOT include Benefits, Pay, Schedule sections. Also remove boilerplate: none present in the input, but I should ensure none leaks in. Structure: I'll create `

      ` for Responsibilities and Qualifications & Skills (or maybe split into Qualifications and Skills? The input combines them as "Qualifications & Skills:". I can keep it as one section or split. Rules say use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Qualifications" and "Skills" are separate examples, but the input has them combined. I think I should keep them as one section titled "Qualifications & Skills" or maybe "Qualifications" since that's the heading pattern. But the rule says "never emit a heading followed by filler/placeholder text". If I title it "Qualifications" and then have skills content, that's fine. Or I could do "Qualifications & Skills" as the heading. I'll check the exact input: "Qualifications & Skills:". I'll use `

      Qualifications & Skills

      ` or maybe just `

      Qualifications

      ` and list both? The examples list "Qualifications, Skills" as separate headings, but the input combines them. To be safe and follow "include a section ONLY when the posting has real, specific content for it", I'll create one section for the combined content. I could title it "Qualifications & Skills" but that might be redundant with the input's colon. I'll use `

      Qualifications & Skills

      ` and then the list. Or I could split into two headings "Qualifications" and "Skills" but the input doesn't clearly delineate them; it's one block "Qualifications & Skills:". I think best is to have one section `

      Qualifications & Skills

      ` since that's the exact label and has content. But wait, the rule says: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists "Qualifications, Skills" as separate examples. It might expect them as separate sections if the content separates them. But the input has them together. I'll keep them as one section titled "Qualifications & Skills" to avoid creating thin sections with placeholder text. Actually, re-read: "Prefer a few substantive sections over many thin ones." So combining is better. What about "Responsibilities"? The input has "Responsibilities" as a heading. I'll use `

      Responsibilities

      `. Now, format the lists: Responsibilities list items: - Safely administer medications under nurse supervision - Monitor and report resident responses - Accurately document treatments and care activities - Assist residents with daily living activities - Promote resident comfort, dignity, and well-being - Maintain infection control and safety standards - Contribute to a team-focused, faith- and values-based environment - Provide person-centered care to enhance quality of life and support recovery - Grow clinical skills through ongoing engagement Qualifications & Skills list items: - Certification as a Medication Aide - Knowledge of medication administration and safety protocols - Strong observation and reporting skills - Ability to work collaboratively within a team - Commitment to resident-centered care and safety standards I need to wrap each in `
      • `. The rule: "Use
        • for any list of duties/requirements/benefits". So I'll do `
          ` with `
          • ` items. Prose: Any prose? The input has headings and lists. No plain prose paragraphs except maybe the role title, but I'm dropping that. I'll check if there's any non-list text. The input is just headings and lists. So I'll just have the headings and lists. Ensure no boilerplate, no job ID, no application instructions. The input doesn't have those, good. Output: ONLY the HTML fragment, no /, no markdown code fences. So I'll just output the HTML directly, like:

            Responsibilities

            • ...
            ...

            Qualifications & Skills

            • ...
            ...
            But wait, rules: "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so those are examples. I should use headings that match the content. "Responsibilities" is explicitly listed. "Qualifications & Skills" maps to "Qualifications" or "Skills". I'll use `

            Qualifications & Skills

            ` or maybe `

            Qualifications

            ` and `

            Skills

            ` separately? Given "Prefer a few substantive sections over many thin ones", combining is better. I'll go with `

            Qualifications & Skills

            `. Check if "Role" should be a section. The input starts with "Role: Certified Medication Aide". Rules: "Do NOT repeat the job title as a heading (the page already shows it)". So I should not create an "About the role" heading with "Certified Medication Aide" in it, unless I fold it into a

            . But then it says "fold minor metadata into a short

            or drop it." I could do `

            Certified Medication Aide

            ` but that might be considered repeating the title. The rule says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

            or drop it." So I can fold it into a short

            . But then if I include it, I'd have a

            with the title. However, the overall structure would start with Responsibilities. I think it's safer to drop it entirely, as the page already shows the title, and including it as prose might be redundant or violate "Do NOT repeat the job title". I'll drop it. Let's re-read carefully: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

            or drop it." This implies I can fold it into a

            , but since the page already shows the title, and we're outputting a fragment, maybe dropping is fine. I'll drop it to keep it clean and avoid any potential repetition. Now, check for any other sections: The input only has Role, Responsibilities, Qualifications & Skills. No Benefits, Pay, Schedule. So I won't create those. Final HTML structure:

            Responsibilities

            • Safely administer medications under nurse supervision
            • Monitor and report resident responses
            • Accurately document treatments and care activities
            • Assist residents with daily living activities
            • Promote resident