Here's a pro tip regarding Claude Code usage if you're a dev - save your Claude skills and more to git. This gives you a mechanism to: keep all your setups in sync (personal, work, etc) iteratively develop your setup (skills) blame and revert bad changes and more++ setup for a simple chill setup: git init ~/.claude add the following .gitignore # always ignore cache/ debug/ file-history/ ide/ session-env/ sessions/ shell-snapshots/ telemetry/ usage-data/ backups/ downloads/ history.jsonl plugins/ agents/**/*.jsonl projects/**/*.jsonl projects/**/*.json projects/**/*.txt # rm below if machines are similar (os, term setup) settings.json statusline-command.sh # rm below if folder structure across machines is compatible projects/ # rm below for record-keeping plans/ todos/ push to a private repo push and pull from various comps to keep things in sync. (you can also get fancier and use dotfiles or GNU Stow) ~/.claude tree claude saves everything to disk in a neat little unobscured .claude…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.