"Write an article about why I ditched Redux for Zustand after 3 years."
The skill opens in medias res (a production situation going sideways), builds the piece across 5 narrative sections, and scrubs AI tics before returning the draft. The conclusion lands on a meta observation about the ecosystem, not a recap of what was just said.
What it does
Story-first method: the article is a story that contains technique, not the reverse. In-medias-res hook, 4 to 6 sections, a conclusion that's a meta-observation (never a recap). Plus a systematic hunt for AI tells (English and French), the fluency mechanics (old then new, strong word at the end, subject and verb close), and the "essential oil" cut that removes half the words without losing meaning.
When to use it
When you write or publish a technical blog article and want it to sound human. Stack-agnostic: the skill writes the article, you wire it into your CMS, static-site generator or template. Not for docs, a README or a reference page.
The stance: most AI articles give themselves away through phrasing ("it's important to note") and a flat rhythm. This skill attacks both: a per-language banned-phrase list, and fluency rules grounded in linguistics research. It's the generalization of this site's writing workflow.
Install this skill
$ /plugin marketplace add ohugonnot/claude-skills
$ /plugin install tech-article@web-developpeur-skills
Frequently asked questions
What exactly is the AI tic hunt?
A per-language blocklist: hollow French phrases ("il est important de noter", "n'hésitez pas") and their English counterparts ("it's worth noting", "leverage"). The skill detects and removes them before handing back the draft.
How is this different from a plain "write me an article" prompt?
The structure is locked in from the start: in medias res hook, narrative sections, meta observation as a close (never a recap). And the given-new flow (known context before new information) is applied sentence by sentence to keep reading smooth.
Can I use it for any stack or language?
Yes, the skill is stack-agnostic. It handles structure and tone, not your CMS or static generator. That said, it's not built for technical docs, READMEs, or reference pages: the narrative format doesn't fit those.
Feedback & discussion · 0
No feedback yet. Tried it? Tell us what you think.