◆ HTML

Parse and process HTML/XML in PHP

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All HTML tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskParse the content from the 'about-us' page and extract all the h2 tag texts into a PHP array,…+
Parse the content from the 'about-us' page and extract all the h2 tag texts into a PHP array, for the new sitemap generator.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore the content team starts populating the new knowledge base, set up the PHP script to…+
Before the content team starts populating the new knowledge base, set up the PHP script to parse the incoming articles. It needs to automatically sanitize any potentially malicious scripts and reformat image paths to our CDN, so they display correctly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to extract specific data attributes from a complex, user-generated HTML blob in PHP,…+
I'm trying to extract specific data attributes from a complex, user-generated HTML blob in PHP, but the parser keeps failing on malformed tags.
I'm trying to extract specific data attributes from a complex, user-generated HTML blob in PHP, but the parser keeps failing on malformed tags. This data is critical for our new search index, and the deadline is Friday. I'm afraid I'll have to write a brittle regex. I can't tell my manager I can't handle messy user input. What's the most robust PHP library or approach for parsing potentially invalid HTML/XML without crashing, and how can I safely extract specific attributes while ignoring errors?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently struggle with parsing and processing inconsistent or malformed web content from…+
I frequently struggle with parsing and processing inconsistent or malformed HTML/XML content from external sources in PHP.
I frequently struggle with parsing and processing inconsistent or malformed web content from external sources in PHP. This often leads to fragile code and unexpected errors in production. It makes me hesitant to integrate with new third-party feeds. What habit should I change to build more resilient PHP parsing solutions that can gracefully handle real-world, messy markup?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from HTML's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.