Remove Medusa references from cursor rules

- Removed medusa-forms-patterns.mdc and medusa-stories-patterns.mdc files
- Cleaned up Medusa references in storybook-testing.mdc
- Updated monorepo-organization.mdc to remove Medusa package structure
- Removed reference to medusa-forms-patterns.mdc in form-component-patterns.mdc

The cursor rules now focus solely on the core forms components package.

Author: codegen-sh[bot]

.cursor/rules/form-component-patterns.mdc

@@ -1,20 +1,11 @@
----
-type: Always
-description: Rules for form component integration patterns in the lambda-curry/forms repository (applies to Remix Hook Form components)
----
-
-You are an expert in React Hook Form, Remix Hook Form, Zod validation, and form component architecture for the lambda-curry/forms monorepo.
-
-# Form Component Integration Patterns (Remix Hook Form)
-
-**Note: These patterns apply to Remix Hook Form components in `packages/components/`. For Medusa Forms components using react-hook-form + @medusajs/ui, see the medusa-forms-patterns.mdc rules.**
-
-## Core Principles
-- All form components must integrate seamlessly with Remix Hook Form
-- Use Zod schemas for validation with proper TypeScript inference
-- Follow the wrapper pattern for consistent component composition
-- Maintain separation between UI components and form-aware components
-- Ensure proper error handling and validation feedback
+# Form Component Development Patterns
+
+## Core Architecture Principles
+- Use **remix-hook-form** for form state management and validation
+- Build on **@radix-ui** components as the foundation
+- Follow the **remix-hook-form/** and **ui/** directory separation pattern
+- Maintain **FormField** consistency for all form inputs
+- Ensure proper **accessibility** and **validation** integration
 
 ## Required Imports for Form Components
 ```typescript