Tips, tricks, and lessons from building software.
Tips, tricks, and lessons from building software — a personal dev blog by Tommy.
Writing Permission Rules That Match Commands
Allow and deny rules let you pre-approve safe tools and block risky ones by pattern.
Reducing Permission Prompts Safely
Cut down on prompts by allowlisting the safe commands you run often, not by turning off all checks.
When to Use (and Avoid) Bypass Permissions
Bypass permissions removes every prompt, which is powerful and risky; reserve it for controlled, throwaway environments.
Read-Only Exploration of an Unfamiliar Codebase
Open a new repository in plan mode and let Claude map it out for you before any change is made.
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.