hubermjonathan/communication
Write for people and reach them: writing standards, briefs, visuals, Slack messages, texts, and QR codes
Turn an investigation, the session so far, or a block of text into a short, plain, non-technical version for a person to read. Use when asked for a short, concise, or non-technical version of something, a summary for a person or channel, or text under a length limit, and when another skill needs text written for someone outside the work.
Generate a QR code for a link with the qrencode CLI and show it in the reply. Use when asked for a QR code, whether the request gives the link or refers to one from earlier in the conversation.
Explain something already said in more depth by walking through one concrete example, step by step. Use when the user asks for more detail on a finding, a decision, a bug, or how something works, asks for an example, or says they don't follow an explanation.
Interview the user round by round to stress-test a plan, decision, or idea. Use when asked to stress-test or poke holes in a plan, decision, or idea, or to be interviewed about it, and when a plan or decision needs its open questions surfaced before any work starts.
Text the user, or people or group chats they name, with a blue bubble (iMessage). Use when asked to text or iMessage me, someone, or a group, such as "text me when you finish", "text me and Jac the budget update", or "text the budget updates group".
Draft and send Slack messages: review asks, status updates, questions to a teammate, and ticket links posted into a thread. Use when asked to message a person, post in a channel or thread, or draft a Slack message.
Show a point as the smallest visual that makes it clear: pseudocode, a call tree, a component or file tree, a Mermaid diagram, a diff-shaped sketch, or a focused HTML page. Use when a point about code or a change is clearer drawn than told, when the user asks to see something, and when another skill needs a visual of a change, such as a PR body or walkthrough.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for every chat reply, and when writing or reviewing docs, RFCs, READMEs, PR descriptions, tickets, or commit messages.
Cut AI writing tells from prose a person outside the session reads: PR bodies, tickets, Slack messages, and docs. Use on that prose, or when asked to make text sound less like AI.