First line must be: # <A proper article title, under 60 characters, includes the keyword naturally>
After title, one blank line, then article body.
Must include ## Quick Verdict section right after the title.
Then narrative review content (following anti-AI rules).
Then ## Pros & Cons section.
Then ## Pricing at a Glance section (markdown table).
Then ## FAQ section.
No closing paragraph after FAQ.

Anti-AI rules:

Forbidden words/phrases (lots).
Human writing tactics: casual, texting a friend, specific details, varied sentence length, inconsistent formatting, one embarrassing personal failure, negative comment about popular tool, at least one 1am line, no perfect 3-point lists in narrative, every paragraph different mood, end narrative abruptly but after structured sections.

Let me count the required sections:

Title
Quick Verdict (with star ratings for each tool)
Narrative story
Pros & Cons
Pricing at a Glance
FAQ

The tools: Figma, Sketch, Adobe XD.

For the Quick Verdict, the example says ChatGPT/Claude, but I need to adapt to Figma/Sketch/Adobe XD.

Let me think about the narrative:

Start with moment you realized you needed to pick. Specific time, food, frustration.
Talk about Tool A (maybe Sketch first).
Talk about Tool B (Figma).
Talk about Tool C (Adobe XD).
"The parts nobody talks about" section.
"## What I Actually Use Now" section.

Wait, the instructions say "Talk about Tool A. What you expected vs what happened. Something that surprised you (good OR bad). Talk about Tool B. Same." — but there are three tools. I should cover all three. Maybe A, B, C.

Also "Include a section that’s basically ‘the parts nobody talks about’ — weird quirks, bad support experiences, hidden fees."

And "A section titled something like ‘## What I Actually Use Now’ where you pick a winner."

Let me structure:

Title
Quick Verdict with star ratings
Narrative intro (realization moment)
Sketch (Tool A)
Figma (Tool B)
Adobe XD (Tool C)
The parts nobody talks about
What I Actually Use Now
Pros & Cons
Pricing at a Glance
FAQ

Wait, the Quick Verdict should be "right after the title" then "write your narrative review content". So:

Title
blank line
Quick Verdict
[verdict text]
narrative…

Then after narrative:

Pros & Cons
Pricing at a Glance
FAQ

But where does "## What I Actually Use Now" go? The instructions say: "After the narrative, add these sections IN ORDER: ## Pros & Cons, ## Pricing at a Glance, ## FAQ." So "What I Actually Use Now" should be part of the narrative? Or between narrative and Pros & Cons? Let me re-read.

"Include a section titled something like ‘## What I Actually Use Now’ where you pick a winner and explain why in 1-2 blunt paragraphs."

And section 10 says "End the narrative abruptly — but AFTER the structured sections below."

Hmm, this is a bit contradictory. Let me parse it again:

"Write a comparison post… CRITICAL — ARTICLE MUST INCLUDE THESE STRUCTURED SECTIONS FOR AI SEARCH ENGINES: After the title, start with: ## Quick Verdict [verdict]. Then write your narrative review content (apply ANTI_AI_RULES for this part). After the narrative, add these sections IN ORDER: ## Pros & Cons, ## Pricing at a Glance, ## FAQ. END HERE. No closing paragraph."

And in the earlier part: "Include a section that’s basically ‘the parts nobody talks about’… A section titled something like ‘## What I Actually Use Now’ where you pick a winner and explain why in 1-2 blunt paragraphs."

So the narrative includes "## What I Actually Use Now" as part of the narrative? Or it should be placed before the Pros & Cons? I think the safest is to make "## What I Actually Use Now" part of the narrative flow, before the Pros & Cons section. Because the narrative is supposed to include picking a winner.

Actually, re-reading: "After the narrative, add these sections IN ORDER: ## Pros & Cons, ## Pricing at a Glance, ## FAQ." So the narrative ends, and then Pros & Cons comes. And "What I Actually Use Now" is part of the narrative — it’s a section within the narrative. So order: title → Quick Verdict → narrative (including "parts nobody talks about" section and "What I Actually Use Now" section) → Pros & Cons → Pricing → FAQ.

Hmm, but "What I Actually Use Now" has a "##" heading, so it’s a section. But it’s within the narrative portion. Let me place it before Pros & Cons but after the "parts nobody talks about" part. That seems logical.

Let me draft the title. Under 60 characters, includes keyword naturally. Options:

"Figma vs Sketch vs Adobe XD: Design Tool Face-off" — that’s 44 characters. Good.
"Figma, Sketch, or Adobe XD? My Honest Take" — 46.

The prompt literally says "Write a comparison post: ‘Figma vs Sketch vs Adobe XD: Design Tool Face-off’." So I’ll use that as the title.

Title: # Figma vs Sketch vs Adobe XD: Design Tool Face-off (44 chars)

Quick Verdict:

Figma ***** (5/5) — best overall, real-time collab
Sketch *** (3/5) — Mac-only, fading fast
Adobe XD *** (3/5) — decent but Adobe baggage

Need to use star emojis. Let me do: Figma ***** (5/5) — best overall, actually fun Sketch **½ (2.5/5) — resting on laurels Adobe XD ***½ (3.5/5) — solid but annoying

Half star emoji: ⭐½ or ⭐⭐½? The example uses "4.5/5" and "*****". For half, I can use "***½" or "⭐⭐½". Let me use ⭐ with half: ⭐⭐⭐½ or similar. Actually simpler: "Figma ⭐⭐⭐⭐⭐ (5/5)" etc.

Let me craft the narrative:

Start: "It was 11pm on a Tuesday. I was eating stale popcorn and crying into a wireframe that absolutely refused to align. That’s when I realized I couldn’t keep pretending all design tools were the same."

Embarrassing personal failure: "I once sent a client a Sketch file with seventeen layers all named ‘Group 2’. They never hired me again. Fine, they did, but they mentioned it. It was weird."

Negative about popular tool: Sketch was the king, now it’s basically a screensaver.

1am line: "and honestly, at that point, the grid could go f*** itself. or whatever."

Let me structure the narrative:

Paragraph 1 (happy? no, frustrated): the realization moment. Paragraph 2: Sketch — what I expected vs what happened. Paragraph 3: Figma — same. Paragraph 4: Adobe XD — same. Paragraph 5: The parts nobody talks about. Paragraph 6: What I Actually Use Now.

Then Pros & Cons, Pricing, FAQ.

Forbidden words I must avoid: dive into, deep dive, unlock, unleash, revolutionize, game-changer, in today’s fast-paced, in the ever-evolving, in the digital age, whether you’re a, whether you’re looking for, seamless, robust, cutting-edge, state-of-the-art, elevate your, take your X to the next level, in conclusion, to sum up, as we’ve seen, it’s important to note, it’s worth noting.

Also should avoid "dive" in general. Let me watch out.

Let me draft:

Figma vs Sketch vs Adobe XD: Design Tool Face-off

Quick Verdict

Figma wins, and it’s not even close. Sketch is living on nostalgia, and Adobe XD is the tool Adobe remembers exists every other Tuesday. Here’s how it shook out for me:

Figma ⭐⭐⭐⭐⭐ (5/5) — best all-around, collab that actually works Sketch ⭐⭐½ (2.5/5) — fine if you’re a solo Mac user in 2018 Adobe XD ⭐⭐⭐ (3/5) — solid, but Adobe’s pricing is a hostage situation

It was 11pm on a Tuesday. I was eating microwave popcorn that had gone slightly stale, staring at a landing page mockup that refused to align no matter what I did. Three hours. Three hours I lost to a spacing issue that should’ve taken thirty seconds. My cursor was trembling. Okay, my cursor wasn’t trembling, but I wanted to throw my MacBook at the wall. That’s when I said "enough" and went looking for a design tool that didn’t make me want to cry.

I’d been using Sketch for years at that point. It was the "pro" tool, the one everyone bragged about on Dribbble. I expected it to feel powerful. Instead it felt… stuck. Every update was slower than the last. Plugins that broke for no reason. And the collaboration — ha. I’d export a file, email it to my dev, he’d send back screenshots with red circles, I’d fix things, re-export, and we’d repeat that dance until we both wanted to quit. Sketch was fine for sitting alone in a dark room, but it wasn’t made for humans working together. Also, it’s Mac-only. I said that like it’s a bad thing. It is, if your team has one Windows person. You know who. The guy who keeps asking for "the Sketch thing" to open on his Surface.

So I tried Figma. Everyone online was screaming about it like it was the second coming, and I’m a skeptic by nature. But the first time I opened a Figma file and my teammate was literally moving layers around in real-time, I felt my brain short-circuit. Wait, that’s real? That just… works? I expected a clunky web app that lagged every three seconds. What I got was crisp, fast, and genuinely fun — which sounds stupid to say about a design tool, but there you go. It runs in the browser. It works on Windows. It has components that don’t spontaneously explode (looking at you, Sketch). And the cursor shows you what other people are doing, which is annoying when someone’s idling in the middle of your artwork, but incredible when you’re actually collaborating. I sent a link to a client once, and she commented directly on the design. I nearly wept.

Now Adobe XD. I tried it because I already pay Adobe a small fortune for Photoshop and Illustrator, so what’s one more app in the graveyard, right? Actually, XD surprised me. It’s clean. It’s fast. It does prototyping better than Figma out of the box, honestly. But here’s the thing — it exists in Adobe’s ecosystem, and Adobe treats every product like it’s a hostage negotiation. "Want to share a link with your client? That’ll require the ‘Share’ plan. Oh, you want unlimited? That’s a different subscription." Also, I have a deep, personal hatred for Creative Cloud’s background updates. I opened XD once and it paused for twelve minutes updating some font service. Twelve minutes. I could’ve redrawn the whole layout by hand.

The parts nobody talks about — alright, here’s the stuff the fanboys won’t tell you. Figma’s free tier is genuinely generous, but you’ll hit the "3 files" limit faster than you think, and then suddenly you’re paying $15/month per editor. Per editor. That adds up if you have a team. Sketch has moved to a subscription model too, which made all the "I bought Sketch forever" people furious. And XD — man, the plugins are a mess. Half of them are abandoned. Also, all three tools have that moment where you load a huge file and your laptop sounds like a jet engine. Figma’s web version ate my RAM once at the worst possible time — I was presenting, my screen froze, and I had to close the tab and reopen it in front of the client. Embarrassing. Also, Sketch’s file format is proprietary, and converting to Figma requires an importer that works fine until it doesn’t and then you’re in a nightmare of nested symbols.

One more thing — the support. Good luck getting a human from any of these companies. Figma’s help center is decent, but I filed a ticket about a shared component behavior once and got a reply six days later that referenced a different problem entirely. Adobe XD support is hidden somewhere in the Creative Cloud maze. I called once and the automated system asked me to input my account number three times before giving up. Sketch? I don’t even know how to reach a human over there.

What I Actually Use Now

Figma. Obviously. I use it for everything.

Look, Sketch was good to me once, but it never grew up. Adobe XD is genuinely capable, but Adobe’s pricing and update roulette drive me insane. Figma isn’t perfect — the free tier restrictions are annoying, and sometimes the text tool does something weird with line-height — but it’s the only one that feels like it was built for how design actually works now. Real-time collaboration isn’t a gimmick. It changes the entire workflow. I open a file, my dev gets a link, we’re both in the same design at the same time, commenting,