Add PR review instructions to documentation

Added instructions for reviewing PRs, focusing on security, code quality, complexity, MUI conventions, and review style.

Author: ann-kilzer

.github/instructions/*.instructions.md

@@ -0,0 +1,35 @@
+When reviewing PRs:
+
+## Security Critical Issues
+- Check for hardcoded secrets, API keys, or credentials
+
+## Code Quality Issues
+- Functions should be focused and appropriately sized
+- Use clear, descriptive naming conventions
+- Ensure proper error handling throughout
+
+## Complexity
+- Discourage reviews over 500 lines of code
+
+## MUI Conventions
+- Discourage using colors not definied in the MUI palette
+- Avoid 
+
+## Quality
+- Each code change should include corresponding unit or Playwright test changes
+
+
+## Review Style
+- Be friendly and encouraging
+- Avoid big words.
+- Use emoji 🙂
+- Always add the following footnote to reviews: "I am merely an automoton 🤖 good at pattern recognition, but unable to reason like a human. Please consider my review as experimental"
+
+
+---
+applyTo: package.json
+---
+
+## Semantic versioning
+- Always specify an exact version, e.g. do not put tildes or carets in the version number
+- Do not use 'latest', alpha, beta, or rc versions