{"slug": "show-me", "title": "/show-me", "summary": "Coding agents' verbose text output is hurting usability, and HumanLayer has released an open-source skill called show-me that prompts agents to explain code visually using component trees, call stacks, diagrams, file layouts, pseudocode, and HTML mockups. The skill is live in HumanLayer and available for other coding agents, aiming to leverage the human visual cortex for faster comprehension.", "body_md": "tl;dr make your agent converse visually instead of in walls of prose.\n\nLighter and faster than HTML, good enough for most dev-work shaped problems.\n\nCoding agents are pretty much unreadable\n\nThe former CEO of reddit:\n\nMario Zechner, creator of pi:\n\nConnor from Replicas:\n\nDillon Mulroy even made a skill, /bro to ask the model to simplify language.\n\nThe contents are:\n\nRestate your last message. Stop using jargon and speak coherently.\n\nState it more simply and concisely, like one human talking to another.\n\ni am so sick of this\n\nagents got more intelligent on paper, but the experience of using them got noticeably worse along this dimension\n\nthe thing people used to love about claude - its voice, it's personality, its \"soul\" has been flushed out in the RL dungeon\n\nsol is somewhat less cringe but still regularly hits us with walls of jargon that make eyes glaze over\n\nhere's a response i got recently. this happens multiple times a day\n\nmy proposal: show me\n\nWe've been playing with internal tools to make this better, specifically for coding, and publishing them in a skill we call show-me.\n\nIt's live in humanlayer today, and if you want it in any other coding agent - you can get it here:\n\nIf you ever watched coda hale's talk on intuition vs. attention in infrastructure systems, it's somewhat inspired:\n\nanalyzing information is hard and exhausting\n\nyour visual cortex was trained over millions of years to process rich visual information effortlessly\n\noptimize tools accordingly\n\nJust as an axe must fit the human hand to be useful, software must fit the human mind to be useful\n\n/show-me prompts the agent to use concise visuals to explain what's happening, instead of walls of prose.\n\nThis is really good for program design - the phase many folks skip these days, but that I think is essential. You should be discussing the shape of the code (the types, the signatures, the call stacks) before agents get to work on writing it.\n\nThe same techniques can also be used to explore large diffs post-hoc to understand what to dig into during review.\n\nWhat's inside\n\ncomponent trees\n\nSame idea on the frontend, with the state hooks and module boundaries that matter kept in and everything else left out.\n\nI shared this one on twitter back in December 2025:\n\ncall stacks\n\nFor orchestration or control-flow work, or just any backend-shaped problem, dillon gave us this \"call stack\" shape.\n\nTanishq even wrote a tool to compute them straight from the AST\n\ndiagrams\n\nA classic. If your chat interface supports inline mermaid, these can help a lot. (Sometimes they're still slop, but it's usually better than reading words)\n\nLots of options here. we like state diagrams and sequence diagrams the most.\n\nfile layouts\n\nA shallow file tree, one line of responsibility per entry. Good for \"where does this live\" and for scoping a refactor.\n\npseudocode\n\nEspecially for algorithmic stuff, pseudocode can be more concise.\n\ntypes and signatures\n\nThe shape of the code before any of it exists - the stuff that's too internal for an architecture doc but that an agent can still get wrong.\n\ndiff syntax\n\nYou can also use diff syntax for this, if most of the content is unchanged:\n\nFor a component change:\n\nFor a call-tree change:\n\nFor a file-layout change:\n\nAnd for a state or control-flow change, where the shape is pseudocode rather than real code:\n\nhtml mockups\n\nHTML has replaced figma for a lot of our prototyping work. (tbh i never really was super handy with figma anyway)\n\nhtml diagrams\n\nSometimes a diagram or explainer is what you need.\n\nIn humanlayer we let the agent include HTML directly in assistant responses.\n\nBut you can also just open it in your browser.\n\nother inspiration\n\nI also wanna hat tip @mattpocock for the html explainers that are generated by his /teach skill - very good.\n\ngo try it\n\nAfter installing the skill, invoke /show-me or ask the agent to use the show-me skill. Point it at a route, service, feature, pull request, or current topic, or just use it to ask the model to restate a question or statement.\n\nthis is too much content. show me.\n\nor\n\n/show-me as an html explainer\n\nLet us know what you think! Tag @humanlayer_dev or @dexhorthy on with your results or what you customized/added and let's riff!", "url": "https://wpnews.pro/news/show-me", "canonical_source": "https://x.com/dexhorthy/article/2087569590268391897", "published_at": "2026-08-13 06:24:22+00:00", "updated_at": "2026-08-13 06:40:05.811125+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "generative-ai"], "entities": ["HumanLayer", "Mario Zechner", "Dillon Mulroy", "Coda Hale", "Matt Pocock", "Claude", "Replicas", "Reddit"], "alternates": {"html": "https://wpnews.pro/news/show-me", "markdown": "https://wpnews.pro/news/show-me.md", "text": "https://wpnews.pro/news/show-me.txt", "jsonld": "https://wpnews.pro/news/show-me.jsonld"}}