Home / Cursor rules / React Mobx
React Mobx
Cursor rules for React development with MobX integration.
Cursor rules (.mdc)Public domain (CC0)
–unranked
Install
mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/react-mobx-cursorrules-prompt-file.mdc -o .cursor/rules/react-mobx.mdcDownloads the file at commit b044f956f021 into .cursor/rules/.
To remove it later:
rm .cursor/rules/react-mobx.mdcContext cost: ≈279 tokens when used.
Rules file
--- description: "Cursor rules for React development with MobX integration." globs: **/* alwaysApply: false --- // React + MobX .cursorrules // Prefer functional components with hooks const preferFunctionalComponents = true; // MobX best practices const mobxBestPractices = [ "Use MobX-react-lite for optimal performance with functional components", "Implement stores for managing application state", "Utilize computed values for derived state", "Use actions for modifying observable state", "Implement proper error handling in asynchronous actions", ]; // Folder structure const folderStructure = ` src/ components/ stores/ hooks/ pages/ utils/ `; // Additional instructions const additionalInstructions = ` 1. Use TypeScript for type safety with MobX 2. Implement strict mode for MobX for better debugging 3. Use observer HOC or useObserver hook for reactive components 4. Implement proper dependency injection for stores 5. Use reaction for side-effects based on observable changes 6. Utilize MobX DevTools for debugging 7. Follow MobX best practices for scalable state management `;
Security
Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.
None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.
A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan