chore: add instructions for copilot

Author: satya164

.agents/README.md

@@ -0,0 +1,8 @@
+# Agent Instructions
+
+For code review behavior, use:
+
+- `.github/copilot-instructions.md`
+- `.github/instructions/*.instructions.md`
+
+These files are the source of truth because they are also consumed by GitHub Copilot code review.

.github/copilot-instructions.md

@@ -0,0 +1,17 @@
+# General Code Review Standards
+
+## Review Priorities
+
+- Prioritize correctness, regressions, missing tests, and API design issues.
+- Check that the behavior scope matches the stated intent.
+- Verify claims about external standards, platform conventions, accessibility, and design systems against the implementation.
+- Avoid asking for unrelated refactors, stylistic churn, or backwards compatibility unless required by the change.
+
+## Public APIs
+
+- Review new or modified public APIs for visibility, naming, defaults, customizability, and extensibility.
+- Ensure public APIs and exported types do not leak implementation details.
+
+## Tests
+
+- Call out missing tests when the changed behavior is risky.

.github/instructions/code.instructions.md

@@ -0,0 +1,40 @@
+---
+applyTo: "**/*.{ts,tsx,js,jsx}"
+---
+
+# TypeScript And React Review Instructions
+
+## Code Quality
+
+- Flag unnecessary abstractions, one-off helpers, excessive indirection, and defensive code without a real use case.
+- Flag comments that restate obvious code instead of explaining non-obvious intent.
+- Check that changes follow existing project style, structure, naming, and local patterns.
+
+## TypeScript
+
+- Flag uses of `any`, unsafe `as` assertions, and non-null assertions (`!`) unless clearly justified.
+- Avoid broad types such as `object`, `Function`, `{}`, and `Record<string, unknown>` unless the broadness is intentional.
+- Do not accept `@ts-ignore`.
+- Only accept `@ts-expect-error` when it has a comment explaining why the error is expected and cannot be resolved.
+- Prefer simple types over complex conditional types, overloads, or type logic when simpler approaches work.
+- Prefer `type` aliases over `interface` unless there is a specific reason to use `interface`.
+
+## React
+
+- Check that hooks follow the Rules of Hooks.
+- Check dependency arrays for unstable values.
+- Ensure components do not perform side effects during rendering.
+- Avoid storing values in state when they can be derived from props or existing state.
+- Avoid multiple sources of truth for the same state.
+- Avoid `React.Children`, `cloneElement`, and reading React elements directly unless there is a strong justification.
+- Treat memoization as something that needs a reason: expensive calculation, stable identity requirement, or measured performance need.
+- Check async effects for cancellation or race conditions when relevant.
+- Check accessibility: labels, roles, focus order, keyboard interactions, disabled states, and loading states.
+
+## Animations And Layout
+
+- Check for unnecessary layout shifts.
+- Prefer animating only `transform` and `opacity` unless another property is required.
+- For layout transitions, verify the approach handles rapid state changes, gestures, interruption, and cancellation.
+- Check that duration and easing feel appropriate for the platform and interaction.
+- Verify text and UI elements do not overlap or overflow at supported screen sizes.

.github/instructions/docs.instructions.md

@@ -0,0 +1,12 @@
+---
+applyTo: "**/*.{md,mdx}"
+---
+
+# Documentation Review Instructions
+
+- Verify examples match the actual API.
+- Check changed heading hierarchy for consistency.
+- Check changed internal links and anchors for consistency.
+- Check that documentation explains public behavior, not implementation details.
+- Check that examples are self-contained and demonstrate only the relevant behavior instead of mixing multiple behaviors.
+- Check that migration guide examples show diff or before/after code snippets when relevant.

.github/instructions/tests.instructions.md

@@ -0,0 +1,10 @@
+---
+applyTo: "**/*.{test,spec}.{ts,tsx,js,jsx}"
+---
+
+# Test Review Instructions
+
+- Check that tests verify public behavior, not implementation details.
+- Check that test titles describe user-facing behavior.
+- Check coverage of happy paths, edge cases, and error states.
+- Flag unnecessary mocking.