Adding the following .windsurfrules file has saved me alot of frustration and time. I'm interested to hear what other Windsurf users are running:
Use uv for package management instead of pip.
When tests pass, and there are significant changes to the codebase, commit changes to git.
Save each user prompt to a file in the prompts directory.
What is .windsurfrules? I got tired of yelling at my Windsurf prompt to "git commit your changes" (like I yell at my kids to brush their teeth each night). Didn't realize my previous prompt fell out of the context window every few code exchanges. It (the AI) calmly informed me that what "Memories" are for. They can alternately be stored in global_rules.md.
What is Windsurf? It's a code assistant similar to Cursor and Devin, available as a VSCode fork for a monthly fee. More info (and a couple of prompts): https://github.com/ichoosetoaccept/awesome-windsurf
0 comments
—
Ask HN: What are you running for .windsurfrules? · HackerTrans
What is .windsurfrules? I got tired of yelling at my Windsurf prompt to "git commit your changes" (like I yell at my kids to brush their teeth each night). Didn't realize my previous prompt fell out of the context window every few code exchanges. It (the AI) calmly informed me that what "Memories" are for. They can alternately be stored in global_rules.md.
What is Windsurf? It's a code assistant similar to Cursor and Devin, available as a VSCode fork for a monthly fee. More info (and a couple of prompts): https://github.com/ichoosetoaccept/awesome-windsurf