mirror of
https://github.com/maybe-finance/maybe.git
synced 2025-07-19 05:09:38 +02:00
71bc51ca15
Changed transaction form to only display relevant categories based on transaction type (income or expense), improving usability and preventing misclassification. Created a shared transaction type tabs component for consistent navigation between expense, income, and transfer forms, providing a better user experience and reducing code duplication. Signed-off-by: Zach Gollwitzer <zach@maybe.co> Co-authored-by: Zach Gollwitzer <zach@maybe.co>
22 lines
1.2 KiB
Text
22 lines
1.2 KiB
Text
---
|
|
description: This file describes Maybe's design system and how views should be styled
|
|
globs: app/views/**,app/helpers/**,app/javascript/controllers/**
|
|
alwaysApply: true
|
|
---
|
|
Use the rules below when:
|
|
|
|
- You are writing HTML
|
|
- You are writing CSS
|
|
- You are writing styles in a JavaScript Stimulus controller
|
|
|
|
## Rules for AI (mandatory)
|
|
|
|
The codebase uses TailwindCSS v4.x (the newest version) with a custom design system defined in [maybe-design-system.css](mdc:app/assets/tailwind/maybe-design-system.css)
|
|
|
|
- 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-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
|
|
- Always generate semantic HTML
|