Investigate and refactor
When the same issue keeps appearing, it often signals a deeper problem. Instead of applying another patch, ask Play to investigate the root cause and refactor that part of the system.
The pattern
You've tried fixing something a few times. Each time, it works temporarily or a different problem emerges. This usually means the underlying structure has a weakness.
Repeated failures are a signal. Stop fixing symptoms and ask Play to examine the system itself.
How to ask
Be direct about the pattern you're seeing. Ask Play to investigate and rebuild.
Examples
"This save button has failed three times. Can you investigate why and refactor the save logic?"
"The filter keeps breaking in different ways. Look into the data flow and redesign it to be more reliable."
"This automation worked twice then stopped. Can you find the root cause and fix it properly?"
"I keep running into issues with this section. Can you rebuild it from scratch with a cleaner approach?"
What Play does
When you ask for investigation and refactoring, Play:
Examines the structure — Looks at how the component is built, how data flows through it, and where the weak points are.
Identifies the root cause — Finds what's actually going wrong, not just the surface symptom.
Rebuilds for reliability — Restructures the component to be more robust, often with cleaner logic and better error handling.
Asking for investigation and refactoring is often faster than incremental fixes. You solve the real problem instead of chasing symptoms.
When to use this approach
The same error appears multiple times
Fixes work temporarily then break again
You're unsure what's actually causing the problem
The component feels fragile or unpredictable
What's next
For initial troubleshooting, see When something isn't working.
For general prompting, see Just describe what you want.