chore: update copilot instructions to emphasize code quality, structure, and error handling

Author: codeAbinash

.github/copilot-instructions.md

@@ -8,4 +8,18 @@
 
 - No need to fix formatting related issues.
 
-- You can use `bun ts` for type checking.
+- You can use `bun ts` for type checking.
+
+- Always check for typescript errors before providing the final code in the editor.
+
+- Keep the implementation simpler, keep the code cleaner, and if possible keep the utility functions or pure functions outside at the root.
+
+- Patch fixes are not allowed, always provide a proper solution to the problem. Find the root cause and fix it.
+
+- `as any` type usage is not allowed
+
+- No reparative code is allowed, use the DRY principle to avoid code repetition.
+
+- Think hard, take your time and implement it nicely, with good code quality, readable and efficient.
+
+- When I ask to fix anything do not patch fix, update anything you want but make the code very very well structured, clean, efficient and with good code quality.