Files
gps-denied-onboard/.cursor/rules/react.mdc
T
Oleksandr Bezdieniezhnykh 1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
Update demo replay validation and testing documentation
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests.
- Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps.
- Updated architectural documentation to include the new demo replay operator flow and its dependencies.
- Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation.
- Added new entries in the dependencies table for upcoming tasks related to the demo replay flow.

These changes improve clarity and usability for operators and developers working with the demo replay system.
2026-06-20 11:24:43 +03:00

18 lines
903 B
Plaintext

---
description: "React/TypeScript/Tailwind conventions: components, hooks, strict typing, utility-first styling"
globs: ["**/*.tsx", "**/*.jsx", "**/*.ts", "**/*.css"]
---
# React / TypeScript / Tailwind
- Use TypeScript strict mode; define `Props` interface for every component
- Use named exports, not default exports
- Functional components only; use hooks for state/side effects
- Server Components by default; add `"use client"` only when needed (if Next.js)
- Use Tailwind utility classes for styling; no CSS modules or inline styles
- Name event handlers `handle[Action]` (e.g., `handleSubmit`)
- Use `React.memo` for expensive pure components
- Implement lazy loading for routes (`React.lazy` + `Suspense`)
- Organize by feature: `components/`, `hooks/`, `lib/`, `types/`
- Never use `any`; prefer unknown + type narrowing
- Use `useCallback`/`useMemo` only when there's a measured perf issue