Notes on building software.
A personal blog of technical articles about software development.
Always Give Claude a Way to Check Its Work
Hand Claude a test, lint, or build command it can run itself, and it will catch and fix its own mistakes before you ever see them.
Be Specific: Prompts That Get Better Results
Vague prompts get vague code. Name the files, state the constraints, and describe what done looks like to get sharp results.
Point Claude at Examples and Patterns
Show Claude an existing file that does it the right way, and new code will match your conventions instead of inventing its own.
Paste Screenshots to Explain Bugs Faster
A screenshot of a broken layout or an error dialog tells Claude in one glance what a paragraph of description struggles to.
Use @ File Mentions Instead of Copy-Paste
Type @ and a path to have Claude read the real file, so you never paste stale code or lose the surrounding context.
Drop into a Shell with ! Bash Mode
Start a line with ! to run a shell command yourself without leaving Claude, and the output stays in the conversation.