Store Manager Mr Price Palm Gate Parys
Power Fashion
Job Description
for intro paragraphs and general text - Use
for section headers (Responsibilities, Qualifications, etc.)
- Use - for list items
- No CSS classes, no inline styles, no s, no
tags
- Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase
- If text has no clear sections, just wrap paragraphs in tags
- Return ONLY the HTML. No markdown fences, no explanation, no preamble.
Then the user provides a long job description text.
Wait, there's a conflict/confusion. The initial prompt says: "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." And it says to remove a bunch of stuff, keep specific fields, etc.
But then the user gives a second set of rules: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with specific HTML tags, no classes/styles/div/br, preserve all content word-for-word, return ONLY HTML, no markdown fences, etc.
Then they provide the job description text.
I need to figure out which set of rules to follow. The very first part seems like a system prompt or role description. The second part seems like the actual task instruction for this specific instance. The user says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then gives rules. Then gives the job description.
I think the task is to take the provided job description text, and format it as clean semantic HTML according to the rules given. The rules say: preserve ALL original content word-for-word, do not add, remove, summarise, or rephrase. Use
for intro paragraphs and general text,
for section headers, - for list items. No CSS classes, no inline styles, no s, no
tags.
But the original job description text has a lot of HTML already in it (like , , , , styles, etc.). The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But also "No CSS classes, no inline styles, no
tags - Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase - If text has no clear sections, just wrap paragraphs in
tags - Return ONLY the HTML. No markdown fences, no explanation, no preamble. Then the user provides a long job description text. Wait, there's a conflict/confusion. The initial prompt says: "Return ONLY the cleaned job text. Do not add any commentary, headers like "Here is the cleaned version", or markdown formatting. Just the clean job listing text." And it says to remove a bunch of stuff, keep specific fields, etc. But then the user gives a second set of rules: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." with specific HTML tags, no classes/styles/div/br, preserve all content word-for-word, return ONLY HTML, no markdown fences, etc. Then they provide the job description text. I need to figure out which set of rules to follow. The very first part seems like a system prompt or role description. The second part seems like the actual task instruction for this specific instance. The user says: "You receive a plain-text job description. Your ONLY job is to format it as clean semantic HTML." Then gives rules. Then gives the job description. I think the task is to take the provided job description text, and format it as clean semantic HTML according to the rules given. The rules say: preserve ALL original content word-for-word, do not add, remove, summarise, or rephrase. Use
for intro paragraphs and general text,
for section headers, - for list items. No CSS classes, no inline styles, no s, no
tags.
But the original job description text has a lot of HTML already in it (like , , , , styles, etc.). The rule says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". But also "No CSS classes, no inline styles, no
tags. But the original job description text has a lot of HTML already in it (like
- , , ,