<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>UX on Unbound Force</title><link>https://unboundforce.dev/tags/ux/</link><description>Recent content in UX on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/ux/index.xml" rel="self" type="application/rss+xml"/><item><title>Zero-Code UX — How a Markdown File Became Dewey's Best Feature</title><link>https://unboundforce.dev/blog/dewey-slash-command-ux/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/dewey-slash-command-ux/</guid><description>&lt;h2 id="the-problem-nobody-talks-about"&gt;The Problem Nobody Talks About&lt;/h2&gt;
&lt;p&gt;Developer tools optimize for the power user who already knows the flags. Documentation lists every parameter, every option, every edge case — and assumes the reader arrives with a mental model of how the tool works. But the most common interaction with Dewey&amp;rsquo;s &lt;code&gt;store_learning&lt;/code&gt; tool looks nothing like a power user session.&lt;/p&gt;</description></item></channel></rss>