Vibe coding safety tips summary Been using vibe coding a lot these past few weeks, and after some Twitter exchanges with @evilcos and @rtk17025, I’ve summarized a few tips: 1. Use separate computers or virtual machines to isolate vibe coding and crypto assets. 2. Don’t store private data like keys, API keys, session login info, etc., in your code or input them into prompt dialogs. 3. Avoid downloading unknown plugins in the Vibe Coding IDE or running `npm install` for unknown programs. Due to hallucinations in large language models, always double-check. 4. Don’t use cursor to directly open unverified folders—cursor might automatically execute programs inside the folder. 5. Don’t randomly download Claude’s skills. Recently, hackers have been using skills to inject malicious code and steal crypto users’ assets. 6. If you need AI to perform security checks, you can add security defense prompts to your project or use cursor’s security rules files (Rules Files) to define security rules in the file. 7. Before going live, have one or more AIs scan for vulnerabilities, and it’s best to manually review as well, especially for operations involving asset transfers. Any other tips to add?