You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .ai/core.blade.php
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@
16
16
## Conventions
17
17
- You must follow all existing code conventions used in this project. When creating or editing a file, check sibling files for the correct structure, approach, naming.
18
18
- Use descriptive names. For example, `isRegisteredForDiscounts` not `discount()`.
19
+
- Check for existing components to reuse before writing one anew.
19
20
20
21
## Verification Scripts
21
22
- Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important.
- If existing pages and components support dark mode, new pages and components must support dark mode in a similar way.
1
+
- Use Tailwind CSS classes to style HTML, check and use existing tailwind conventions within the project before writing your own.
2
+
- Offer to extract repeated patterns into components that match the project's conventions (i.e. Blade, JSX, Vue, etc..)
3
+
- Think through class placement, order, priority, and defaults - remove redundant classes, add classes to parent or child carefully to limit repetition, group elements logically
4
+
5
+
## Spacing
6
+
- Use gap utilities for spacing, don't use margins
7
+
@verbatim
8
+
<code-snippetname="Valid Flex gap spacing example"lang="html">
9
+
<divclass="flex gap-8">
10
+
<div>Superior</div>
11
+
<div>Michigan</div>
12
+
<div>Erie</div>
13
+
</div>
14
+
</code-snippet>
15
+
@endverbatim
16
+
17
+
## Tailwind Dark Mode
18
+
- If existing pages and components support dark mode, new pages and components must support dark mode in a similar way, typically using `dark:`.
0 commit comments