1. always use plan mode (shift-tab) first
2. always generate a CLAUDE.md file (like cursor rules)
   • call /init (this will generate the file)
   • make sure is up-to-date
3. commit often and use git as a checkpoint
   • yes, claude IDE has a "Restore Checpoint" feature and it will go to that point in time
   • but I use git on Claude Code (this doesn't have "Restore" feature)
     • i often git commit if everything looks good
     • or discard it!
   • NEED TO TRY: seem this can interact with git (maybe we can instruct to commit after each feature is added)
4. use screenshots (you can drag screenshots into claude code)
   • I am using a screenshot folder (with initial draft ideas)
   • and update CLAUDE.md with
     • I've put some screenshots of the app in the screenshots directory. If you're working on the UI at all, take a look at them. Keep in mind, though, that they may not be up to date with the latest code changes.
5. use claude web search too (claude code has a builtin agent for accessing browser)
   • you can paste link to documentation
   • even use google search
6. you can use Subagents
   • ask to break the problem down and use subagents (all will run in parallel)
7. alway ask it to double check the work done (or ask the user to manually do that)
   • seems sometimes will find things
8. always REVIEW the code that will produce!
   • as if we will review the code of another developer
   • don't be tempted to auto-accept what will generate