Re:Claude Code Cheat Sheet
by droidjj on Monday March 23, 2026 @06:35PM
(#47496071)
The fact this needs to exist seems like a UX red flag.
[ Parent
| on HN ]
Similar to prompting hacks to produce better results. If the machine we built for taking dumb input that will transform it into an answer needs special structuring around the input then it's not doing a good job at taking dumb input.
Re:Claude Code Cheat Sheet
by rtaylorgarlock on Monday March 23, 2026 @06:57PM
(#47496271)
Reminds me of Vercel's Rauch talking about his aggressive 'any UX mistake is our fault, never the user's' model for evaluating UIX.
(It is/was Guillermo who says that, right?)
Re:Claude Code Cheat Sheet
by conception on Monday March 23, 2026 @07:07PM
(#47496349)
This should be all of Information Technology’s take. Your computers get hacked - IT’s fault. Users complain about how hard your software is or that it breaks all the time - IT’s fault.
The fact users deal with almost everything being objectively not very good if not outright bad is a testament to people adapting to bad circumstances more than anything.
This. TUIs are not the correct paradigm for agentic operations. They are too constrained, and too linear.
> Ctrl-F "help"
> Ctrl-F "h"
> 0 results found
Interesting set of shortcuts and slash commands.
Re:Claude Code Cheat Sheet
by skywhopper on Monday March 23, 2026 @08:53PM
(#47497334)
You have a sad narrow point of view about what UX can be.
Enlighten me?
it doesn't need to exist, its all in claudes help, and easily discoverable.
Re:Claude Code Cheat Sheet
by bartwaardenburg on Tuesday March 24, 2026 @05:59AM
(#47500488)
It's a CLI. CLIs have man pages and cheat sheets. That's not a UX failure, that's the format. The same argument would apply to git, ripgrep, or ffmpeg.
The actual complexity in Claude Code isn't the commands, it's figuring out a workflow that works for your codebase. CLAUDE.md files, hooks, MCP servers, custom skills. Once you have that set up the daily usage is just typing what you want done.