WhatsApp Styler (1)

**Judgement:** A focused, high-utility formatter for WhatsApp that is well-aligned with the platform’s limited styling capabilities and mobile-first constraints. It is particularly valuable as a downstream “final pass” for any LLM or workflow that normally emits rich markdown but must appear clean in WhatsApp. **What it does well:** - Enforces correct WhatsApp syntax for bold (`*text*`), italics (`_text_`), strikethrough (`~text~`), monospace (```text```), bullets (`* Item`), numbered lists (`1. Item`), and quotes (`> text`). - Explicitly bans markdown constructs that break or degrade in WhatsApp (headers, tables, horizontal rules, nested formatting that risks leaking symbols). - Encourages a human-to-human, concise style that fits WhatsApp UX instead of long-form markdown documents. **Risks / Limitations:** - If upstream prompts or tools rely on full markdown (tables, headings, complex nesting), they must be adjusted; otherwise content may be degraded or blocked. - The rules appear static; future changes in WhatsApp’s renderer or regional quirks are not automatically handled. - No visible handling of edge cases like mixed-language content, long code blocks, or aggressive nesting beyond basic prohibitions. **Recommended scenarios:** - Use as a dedicated formatting layer for any agent or workflow that sends messages to WhatsApp, especially when the base model is tuned to output markdown. - Pair with higher-level reasoning or business-logic skills; this skill should be the final step before sending text to WhatsApp, not the place to implement content logic. - Ideal for support, sales, and notification bots where clarity and compatibility matter more than rich layout features.