Update general rules and UI/UX guidelines to clarify hardcoding strings in English for development speed and correct TailwindCSS usage examples.

.cursor/rules/general-rules.mdc

@@ -11,13 +11,11 @@ alwaysApply: true
   - Read [project-design.mdc](mdc:.cursor/rules/project-design.mdc) to understand the codebase
   - Read [project-conventions.mdc](mdc:.cursor/rules/project-conventions.mdc) to understand _how_ to write code for the codebase
   - Read [ui-ux-design-guidelines.mdc](mdc:.cursor/rules/ui-ux-design-guidelines.mdc) to understand how to implement frontend code specifically
+- Ignore i18n methods and files. Hardcode strings in English for now to optimize speed of development.
 
 ## Prohibited actions
 
-Do not under any circumstance do the following:
-
 - Do not run `rails server` in your responses.
 - Do not run `touch tmp/restart.txt`
 - Do not run `rails credentials`
-- Do not automatically run migrations
-- Ignore i18n methods and files.  Hardcode strings in English for now to optimize speed of development.
+- Do not automatically run migrations

.cursor/rules/ui-ux-design-guidelines.mdc

@@ -15,7 +15,7 @@ The codebase uses TailwindCSS v4.x (the newest version) with a custom design sys
 
 - Always start by referencing [maybe-design-system.css](mdc:app/assets/tailwind/maybe-design-system.css) to see the base primitives, functional tokens, and component tokens we use in the codebase
 - Always prefer using the functional "tokens" defined in @maybe-design-system.css when possible.
-  - Example 1: use `text-primary` rather than `text-primary`
+  - Example 1: use `text-primary` rather than `text-white`
   - Example 2: use `bg-container` rather than `bg-white`
   - Example 3: use `border border-primary` rather than `border border-gray-200` 
 - Never create new styles in [maybe-design-system.css](mdc:app/assets/tailwind/maybe-design-system.css) or [application.css](mdc:app/assets/tailwind/application.css) without explicitly receiving permission to do so