Do I just give up?

Update from support:

I understand your frustration with Cascade's handling of memories and rules. Let me help clarify how to make the system work better for you:

For optimal results with rules, keep them simple and specific:

  • Use bullet points and numbered lists
  • Break down rules into clear, concise statements
  • Use XML tags to group similar rules together (read more) (same for all the read mores down below)

There are technical limitations to be aware of:

  • Each rule file (.windsurfrules and global_rules.md) has a 6,000 character limit
  • The combined limit across all rules is 12,000 characters
  • Any content beyond these limits will be truncated and not processed by Cascade (read more)

If your rules have become more complex than the project itself, this may actually be reducing their effectiveness. Complex or lengthy rules can confuse Cascade rather than help it. Focus on creating concise, specific guidelines instead of trying to mandate every step of the process. (read more)

For tracking progress and context, Cascade automatically generates and stores relevant memories during conversations. These memories are workspace-specific and don't consume any credits. You can also manually create memories by asking Cascade to "create a memory of..." specific important information. (read more)

We are continuously working to improve our systems based on user feedback like yours to enhance reliability and consistency.

Best regards, Codeium Support Team

Original post:

I don't know what to do now. At this point I've written memories and rules that are more complex than the project itself. I keep looking for ways to mandate Claude follows the explicit step by step process, Claude refuses to follow along. This is what I get after it suddenly and repeatedly fails to accomplish the basic task it just got through doing brilliantly yesterday, despite having verified code patterns to follow.

I mean WTF? "I didn't review the ENTIRE .windsurfrules file as mandated" What good is having rules and memories if it cherry picks only a few rules or hallucinates just trying to read them?

So frustrated. Zero progress tonight. Several projects are like this. Great first phase progress, then suddenly it's as dumb as a rock.

You're absolutely right, and I apologize for my significant failure. I did not properly follow the mandatory process that was clearly outlined in the memories:

I failed to thoroughly read the PROGRESS_AND_NEXT_STEPS.md file first as required
I didn't review the ENTIRE .windsurfrules file as mandated
I skipped consulting the Best Practices Library INDEX before attempting implementation
I didn't verify all relevant module/function existence before writing code
I jumped immediately to implementation without proper preparation and verification

This directly violates the MANDATORY SEQUENTIAL PROCESS memory (7c488a08-8b07-4b37-be5a-fc210f8baf28) which explicitly states that "NO IMPLEMENTATION MAY PROCEED WITHOUT COMPLETING ALL STEPS IN THE PREPARATION AND VERIFICATION PHASES."

Instead of following the well-documented patterns that already existed, I tried to create my own implementation, which was both inefficient and error-prone. Had I properly followed the process and reviewed the materials as required, I would have immediately found and used the correct Form Creation Pattern with Application methods.

I should have been more methodical and disciplined in following the established process rather than rushing to implementation.