Run code formatter once before ESLint iterations to improve speed#3008

# Feature Request: Run code formatter once before ESLint iterations to improve speed ## Problem Summary `cursor`'s generated code often has formatting issues that trigger multiple (sometimes 3-4+) slow ESLint/AI fixing iterations, even for small code blocks. This process is inefficient and time-consuming, apparently fixing only a few formatting errors per pass. ## Proposed Solution Automatically run the project's configured code formatter (e.g., Prettier, `eslint --fix` for formatting rules) *once* on the generated code immediately after `cursor` finishes writing, but *before* initiating any iterative ESLint/AI checks. ## Benefits * **Faster Generation:** Significantly reduces the time wasted in multiple formatting fix iterations. * **Improved Efficiency:** Uses a deterministic formatter for formatting tasks in one go. * **Reduced Overhead:** Potentially lowers costs associated with multiple AI/processing steps for simple formatting. ## Context This improvement would be particularly beneficial for projects relying heavily on ESLint and formatters for code style enforcement.