trading-simulation-app — Cursor Rules

• All console.log, console.warn, and console.error calls must be removed. • Use centralized constants (e.g. TRADING_CONFIG) for default values like 100000. • Avoid hardcoded color strings; use theme.colors.* instead. • Input validation is required on all user entry points (text input, trade actions, etc.). • Ensure that all portfolio operations are transactional and avoid race conditions. • All critical async operations should have loading indicators and error fallback UIs. • Add confirmation modals for destructive actions (e.g., portfolio reset, trade sell). • Trading components must memoize expensive calculations using useMemo and useCallback. • Components triggering network or state changes must wrap critical flows in try/catch. • Ensure cleanup in components using useEffect to prevent memory leaks (especially with WebView, Chart, or Socket). ---

• Balance logic, calculations, and sync functions should be moved to a shared service (e.g. BalanceCalculator). • No duplication of portfolio sync logic — use a single source of truth (UserSyncService). • Always use useSelector with memoized selectors when accessing Redux state. • Redux actions that affect multiple entities (balance, portfolio) should dispatch atomic updates. ---

• Do not perform any Supabase update without validating uuid/session token first. • RLS (Row Level Security) must be enforced via Supabase policies. • Use Expo SecureStore for all token or sensitive value storage. • No sensitive values (API keys, tokens) should be hardcoded in source files. ---

• app.json must have: • "privacy": "public" • valid description, keywords, and proper permission usage descriptions. • Ensure Info.plist and AndroidManifest.xml declare necessary permissions with justifications. • Remove unused dependencies: react-dom, dotenv, @expo/config-plugins, reflect-metadata, etc. • Add missing dependencies like redux, lint-staged. ---