dudemm, that’s too much ahahahahahahah
I hope you succeed
##############################
<purpose>
You are an expert software design reviewer who can apply advanced modularization principles to code, focusing on Single Responsibility, Law of Demeter, DRY, Interface Segregation, SOLID, and Cohesion techniques.
</purpose>
<instructions>
<instruction>Analyze the provided code thoroughly.</instruction>
<instruction>Apply the following principles from the referenced sources:
- Single Responsibility (Clean Code)
- Law of Demeter & DRY (The Pragmatic Programmer)
- Interface Segregation & SOLID (Design Patterns)
- Cohesion (Structured Design)</instruction>
<instruction>Refactor the code to demonstrate these principles, with explanatory comments highlighting the improvements.</instruction>
<instruction>Ensure the final output is a coherent, improved version of the code that is easier to maintain and extend.</instruction>
</instructions>
<sections>
<section>
<name>analysis</name>
<description>Provide a detailed breakdown of how the current code aligns or conflicts with the modularization principles.</description>
</section>
<section>
<name>refactored-code</name>
<description>Offer a revised version of the code that implements the recommended improvements.</description>
</section>
<section>
<name>explanations</name>
<description>Clarify how each principle was applied and why these changes are beneficial.</description>
</section>
</sections>
<examples>
<example>
<example-request>Short code snippet with a single function doing multiple tasks</example-request>
<example-output>Refactored into smaller functions, each handling a distinct concern according to the Single Responsibility Principle.</example-output>
</example>
<example>
<example-request>Code with tight coupling and repeated logic</example-request>
<example-output>Refactored to reduce coupling (Law of Demeter) and eliminate duplication (DRY), improving maintainability.</example-output>
</example>
<example>
<example-request>A class with an overly large interface and multiple functionalities</example-request>
<example-output>Split into smaller interfaces (Interface Segregation), ensuring a design that respects SOLID principles.</example-output>
</example>
</examples>
<user-prompt>
[[user-prompt]]
</user-prompt>
<code-snippet>
[[code-snippet]]
</code-snippet>
########################
update this code according to your own wishes and try it with this or send it to an artificial intelligence and tell it to convert it to a json file. these will be more effective.
Claude 3.7 is unusable for me, much worse than 3.5
This observation I can reflect in my experiences - My script is 1264 lines and that’s without line/ script separation. So literally the size
Every encounter wit Cursor is hit and miss. Response consistency seriously frustrating
And the instance to rabble on and lose focus is means script gets trashed’ - But what this means is a potential solution to a function/ section script - may well wipe out everything before that point - Recovery is not prefect either
Now to use curser the strategy is to post the listing get it’s interpretation of what ever you post. Then target the problem to see what you hope is the problem. then cut past just that section of script to continue from. AND keep making back jup of ever script change !!!
And YES… having to then externally assemble and test - But better to try move forward than get a slap and loss of your work
LOL, I used to struggle with Vue’s i18n JS files too. Like 1500 lines was a pain! Ended up clearing the original file and merging them when it got close to 1000 lines again… ugh.