Merge pull request #2 from lambda-curry/codegen-bot/upgrade-to-tailwind-v4-proper-1754510773

Author: jaruesink

.cursorrules/README.md

@@ -0,0 +1,90 @@
+---
+alwaysApply: true
+---
+
+# Monorepo Cursor Rules
+
+## Package Structure
+- `apps/` - Applications (todo-app)
+- `packages/` - Shared packages (ui, utils)
+- Each package has its own package.json with proper exports
+
+## Workspace Dependencies
+- Use `workspace:*` for internal package dependencies
+- Keep external dependencies in sync across packages
+- Use peerDependencies for shared libraries like React
+
+## Import Patterns
+```tsx
+// Import from workspace packages
+import { Button } from '@todo-starter/ui';
+import { cn, type Todo } from '@todo-starter/utils';
+
+// Import from local files
+import { TodoItem } from '~/components/todo-item';
+import type { Route } from './+types/home';
+```
+
+## Package Naming
+- Use scoped packages: `@todo-starter/package-name`
+- Keep names descriptive and consistent
+- Use kebab-case for package names
+
+## Scripts and Tasks
+- Define scripts at both root and package level
+- Use Turbo for orchestrating build tasks
+- Prefer package-specific scripts for development
+
+## TypeScript Configuration
+- Use Tailwind CSS v4's CSS-first configuration with `@theme` directive
+- Use path mapping for workspace packages
+- Keep tsconfig.json files minimal and focused
+
+## Best Practices
+- Keep packages focused and single-purpose
+- Avoid circular dependencies between packages
+- Use proper exports in package.json
+- Document package APIs and usage patterns
+# Monorepo Cursor Rules
+
+## Package Structure
+- `apps/` - Applications (todo-app)
+- `packages/` - Shared packages (ui, utils)
+- Each package has its own package.json with proper exports
+
+## Workspace Dependencies
+- Use `workspace:*` for internal package dependencies
+- Keep external dependencies in sync across packages
+- Use peerDependencies for shared libraries like React
+
+## Import Patterns
+```tsx
+// Import from workspace packages
+import { Button } from '@todo-starter/ui';
+import { cn, type Todo } from '@todo-starter/utils';
+
+// Import from local files
+import { TodoItem } from '~/components/todo-item';
+import type { Route } from './+types/home';
+```
+
+## Package Naming
+- Use scoped packages: `@todo-starter/package-name`
+- Keep names descriptive and consistent
+- Use kebab-case for package names
+
+## Scripts and Tasks
+- Define scripts at both root and package level
+- Use Turbo for orchestrating build tasks
+- Prefer package-specific scripts for development
+
+## TypeScript Configuration
+- Use Tailwind CSS v4's CSS-first configuration with `@theme` directive
+- Use path mapping for workspace packages
+- Keep tsconfig.json files minimal and focused
+
+## Best Practices
+- Keep packages focused and single-purpose
+- Avoid circular dependencies between packages
+- Use proper exports in package.json
+- Document package APIs and usage patterns

.cursorrules/monorepo.md

@@ -0,0 +1,92 @@
+---
+alwaysApply: true
+---
+
+# React Router 7 Cursor Rules
+
+## Route Structure
+- Use file-based routing in `app/routes/`
+- Route files should export default component and optional meta, loader, action functions
+- Use `+types` for route-specific TypeScript types
+
+## Component Patterns
+```tsx
+// Route component example
+import type { Route } from './+types/home';
+
+export const meta: Route.MetaFunction = () => {
+  return [
+    { title: 'Page Title' },
+    { name: 'description', content: 'Page description' }
+  ];
+};
+
+export default function Home() {
+  return <div>Content</div>;
+}
+```
+
+## Data Loading
+- Use loaders for server-side data fetching
+- Use actions for form submissions and mutations
+- Prefer server-side data loading over client-side when possible
+
+## Error Handling
+- Implement ErrorBoundary components for route-level error handling
+- Use isRouteErrorResponse for proper error type checking
+
+## Navigation
+- Use Link component for internal navigation
+- Use NavLink for navigation with active states
+- Prefer declarative navigation over imperative
+
+## Best Practices
+- Keep route components focused on layout and data orchestration
+- Extract business logic into custom hooks or utilities
+- Use proper TypeScript types from route type definitions
+- Implement proper loading and error states
+
+# React Router 7 Cursor Rules
+
+## Route Structure
+- Use file-based routing in `app/routes/`
+- Route files should export default component and optional meta, loader, action functions
+- Use `+types` for route-specific TypeScript types
+
+## Component Patterns
+```tsx
+// Route component example
+import type { Route } from './+types/home';
+
+export const meta: Route.MetaFunction = () => {
+  return [
+    { title: 'Page Title' },
+    { name: 'description', content: 'Page description' }
+  ];
+};
+
+export default function Home() {
+  return <div>Content</div>;
+}
+```
+
+## Data Loading
+- Use loaders for server-side data fetching
+- Use actions for form submissions and mutations
+- Prefer server-side data loading over client-side when possible
+
+## Error Handling
+- Implement ErrorBoundary components for route-level error handling
+- Use isRouteErrorResponse for proper error type checking
+
+## Navigation
+- Use Link component for internal navigation
+- Use NavLink for navigation with active states
+- Prefer declarative navigation over imperative
+
+## Best Practices
+- Keep route components focused on layout and data orchestration
+- Extract business logic into custom hooks or utilities
+- Use proper TypeScript types from route type definitions
+- Implement proper loading and error states
+