vulgarizelisted

# Vulgarize — plain-language summary of what changed Produce a simple message for a **non-technical client** summarising the code changes. It reads like the developer texting the client directly, not like a release note. **Language:** `en` by default. If `$ARGUMENTS` starts with `fr`, write it in French, casual and informal (tutoiement, no polite formulas). Everything else below is identical. > Sibling skill: `/explain-dev` produces a *structured* WhatsApp update (bold numbered points + a > numbered "How to test" section). **This** one produces a flowing, casual text message. Pick by > how formal the recipient is. ## Steps 1. **Read the changes**: look at the git diff (staged + unstaged) and recent commits to understand what actually changed. 2. **Find the "why"**: for each change, identify the concrete impact for the user or the business. 3. **Write the message** following the rules below. ## Writing rules - **First person, speaking directly to them**: "I did…", "I added…" — as if you are the developer talking TO the client. Never refer to the client in the third person ("the client asked…"). Say "you mentioned that…" when referencing feedback you got. - **No technical jargon**: no file names, function names, variable names, component names. Ever. - **Casual tone**: like a WhatsApp/Slack message. No formal salutations, no sign-off boilerplate. - **Explain the WHY, not just the what**: e.g. "that way the numbers are frozen at the moment the order is accepted,