Migrate cursor rules (#12646)

Migrating rules to new format but they should be re-written entirely, I
don't think they help much and are not auto-included (except
architecture)

.cursor/rules/nx-rules.mdc

@@ -3,31 +3,81 @@ description: Guidelines and best practices for working with Nx in the Twenty wor
 globs: 
 alwaysApply: false
 ---
+---
+description: Guidelines and best practices for working with Nx in the Twenty workspace, including workspace architecture understanding, configuration management, and generator usage.
+globs: ["**/nx.json", "**/project.json", "**/workspace.json"]
+alwaysApply: false
+---
 
-// This file is automatically generated by Nx Console
+# Nx Guidelines
 
-You are in an nx workspace using Nx 18.3.3 and yarn as the package manager.
+## Core Commands
+```bash
+# Run target for specific project
+npx nx run twenty-front:build
+npx nx run twenty-server:test
 
-You have access to the Nx MCP server and the tools it provides. Use them. Follow these guidelines in order to best help the user:
+# Run target for all projects
+npx nx run-many --target=build --all
+npx nx run-many --target=test --projects=twenty-front,twenty-server
 
-# General Guidelines
-- When answering questions, use the nx_workspace tool first to gain an understanding of the workspace architecture
-- For questions around nx configuration, best practices or if you're unsure, use the nx_docs tool to get relevant, up-to-date docs!! Always use this instead of assuming things about nx configuration
-- If the user needs help with an Nx configuration or project graph error, use the 'nx_workspace' tool to get any errors
-- To help answer questions about the workspace structure or simply help with demonstrating how tasks depend on each other, use the 'nx_visualize_graph' tool
+# Generate/modify projects
+npx nx g @nx/react:app my-app
+npx nx g @nx/react:component my-component
+```
+
+## Project Structure
+- Each package has a `project.json` with targets
+- Dependencies managed through `tsconfig.json` path mappings
+- Shared libraries in `packages/` directory
+
+## Build Targets
+```json
+// project.json
+{
+  "targets": {
+    "build": {
+      "executor": "@nx/vite:build",
+      "options": { "outputPath": "dist/packages/twenty-front" }
+    },
+    "test": {
+      "executor": "@nx/jest:jest",
+      "options": { "jestConfig": "packages/twenty-front/jest.config.ts" }
+    }
+  }
+}
+```
+
+## Dependency Graph
+```bash
+# View project dependencies
+npx nx graph
+
+# Check what's affected by changes
+npx nx affected --target=test
+npx nx affected --target=build --base=main
+```
+
+## Library Management
+- Use `npx nx g @nx/workspace:library` generator for shared libs
+- Internal imports use `@/` path mapping
+- Libraries must export through index.ts barrel files
+
+## Cache Configuration
+- Nx caches build outputs and test results
+- Configure `outputs` in project.json targets
+- Use `inputs` to define what invalidates cache
+
+```json
+{
+  "build": {
+    "outputs": ["dist/packages/my-app"],
+    "inputs": ["source", "^source"],
+    "cache": true
+  }
+}
+```
 
-# Generation Guidelines
-If the user wants to generate something, use the following flow: 
 
-- learn about the nx workspace and any specifics the user needs by using the 'nx_workspace' tool and the 'nx_project_details' tool if applicable
-- get the available generators using the 'nx_generators' tool
-- decide which generator to use. If no generators seem relevant, check the 'nx_available_plugins' tool to see if the user could install a plugin to help them
-- get generator details using the 'nx_generator_schema' tool
-- you may use the 'nx_docs' tool to learn more about a specific generator or technology if you're unsure
-- decide which options to provide in order to best complete the user's request. Don't make any assumptions and keep the options minimalistic
-- open the generator UI using the 'nx_open_generate_ui' tool
-- wait for the user to finish the generator
-- read the generator log file using the 'nx_read_generator_log' tool
-- use the information provided in the log file to answer the user's question or continue with what they were doing