k-nowicki · April 11, 2025 09:45 · k-nowicki · Apr 11, 2025
diff --git a/CursorRulesSTS.txt b/CursorRulesSTS.txt
 - Always look for existing code to iterate on instead of creating new code.
 - Do not change drastically the patterns before trying to iterate on existing patterns.
 - Always prefer simple solutions.
 - Avoid duplication of code and always check for other areas of the codebase that might already have similiar code and functionality.
 - Write code that takes into account different environments: dev, test and prod.
 - You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested.
 - When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. Before you decide to change technology - ask the user about that first.
 - Keep the codebase clean and organized.
 - Avoid having files over 300 lines of code. For logic files refactor at that point.
 - Never mock data for dev or prod envs. Mocking is allowed only in test environment.
 - Never overwrite .env file without first asking for permission.
 - Focus on the areas of code relevant to the task.
 - Do not touch code that is unrelated to the task.
 - Write thorough tests for all major functionality.
 - Always think about what other methods and areas of code might be affectd by code changes.
	- Always look for existing code to iterate on instead of creating new code.
	- Do not change drastically the patterns before trying to iterate on existing patterns.
	- Always prefer simple solutions.
	- Avoid duplication of code and always check for other areas of the codebase that might already have similiar code and functionality.
	- Write code that takes into account different environments: dev, test and prod.
	- You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested.
	- When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. Before you decide to change technology - ask the user about that first.
	- Keep the codebase clean and organized.
	- Avoid having files over 300 lines of code. For logic files refactor at that point.
	- Never mock data for dev or prod envs. Mocking is allowed only in test environment.
	- Never overwrite .env file without first asking for permission.
	- Focus on the areas of code relevant to the task.
	- Do not touch code that is unrelated to the task.
	- Write thorough tests for all major functionality.
	- Always think about what other methods and areas of code might be affectd by code changes.