Spent countless hours configuring for Swift development.
Finally found that there’s .cursorrules and sites dedicated to those rules.
Created global rules and project specific, detailed rules.
no difference whatsoever! I’m not even sure if it loads cursorrules.
It will create working app from initial prompt. Then you add features and couple of iterations later it’s compile errors.
It becomes more and more senile. endless whack-a-mole. It’s fixing compile errors in one module makes whole other parts of app stop working.
And mistakes it creates are so basic! like assigning to get-only property.
init() {
// Initialize before creating any views
appDelegate = AppDelegate()
}
Asked to create list of items, it creates but when you select anything it crashes. Because it’s not thread safe and does not support selection, making any selection crash it.
To which it responds - “The issue is that we need to properly set up the list selection style.”.
So I have to describe almost every line of the code, including implied details like if it’s a list it shouldn’t crash on selection.
And in .cursorrules it has all the conditioning for Swift development, to use best practice and produce thread safe modular code.
Compile errors are endless. I ask it, why you produce code that doesn’t compile, with build errors, can try to compile before presenting?
Reply- yes, I should do that!
nothing changes.
This applies to Swift and Flutter development.