| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 1 | 0% |
What each file covers
Sections
0 shared · 0 only in A · 1 only in B- + TDD
Commands
neither file has anySection tags
0 shared · 1 only in A · 1 only in B- − code-style
- + testing-strategy
Line diff
aviemet/inventory · .cursor/rules/styles.mdc
@@ −1 @@
1---
2description:
3globs: *.tsx,*.css.ts
4alwaysApply: false
5---
6- DO NOT USE TAILWIND.
7- I repeat: DO NOT USE TAILWIND!
8- This project uses Mantine as a component library.
9- CSS is written using CSS modules with Linaria. CSS is written in separate files with a `css.ts` extension.
10- CSS is imported into React components using `import * as classes from (filename).css`. It should always be accompanied by `import cx from clsx` and referencing classes should always use `cx`.
11- Mantine CSS variables are exported using Mantine's `themeToVars` which converts the base Mantine theme object into CSS variables. This list of mantine css vars is available at `app/frontent/lib`, which is aliased as `@/lib`.
12- Each css.ts file starts with the following imports:
13 `import { css } from "@linaria/core"`
14 `import { vars } from "@/lib"`
15- Styles in css.ts files are built using the `css` function from linaria with string template literals.
16
aviemet/inventory · .cursor/rules/conventions.mdc
@@ +1 @@
1---
2description:
3globs:
4alwaysApply: true
5---
6
7Only work on the task at hand. Limit the scope of your response to exactly what is being worked on in the moment.
8
9### TDD
10
11For every change, find the corresponding test and ensure it passes.
12Ensure that the tests accurately test the interfaces, adjusting tests as needed to accurately test the intention of the code. Do not change tests to fit the implementation just to make them pass. The tests need to accurately indicate the intention of the code, and the code needs to be made to pass the tests, not the other way around.
13
14* For ruby files, tests are in /rspec
15* For typescript files, tests are in /app/frontend/tests
@@ −1 +1 @@
11 ---
22 description:
3−globs: *.tsx,*.css.ts
4−alwaysApply: false
3+globs:
4+alwaysApply: true
55 ---
6−- DO NOT USE TAILWIND.
7−- I repeat: DO NOT USE TAILWIND!
8−- This project uses Mantine as a component library.
9−- CSS is written using CSS modules with Linaria. CSS is written in separate files with a `css.ts` extension.
10−- CSS is imported into React components using `import * as classes from (filename).css`. It should always be accompanied by `import cx from clsx` and referencing classes should always use `cx`.
11−- Mantine CSS variables are exported using Mantine's `themeToVars` which converts the base Mantine theme object into CSS variables. This list of mantine css vars is available at `app/frontent/lib`, which is aliased as `@/lib`.
12−- Each css.ts file starts with the following imports:
13− `import { css } from "@linaria/core"`
14− `import { vars } from "@/lib"`
15−- Styles in css.ts files are built using the `css` function from linaria with string template literals.
166
7+Only work on the task at hand. Limit the scope of your response to exactly what is being worked on in the moment.
8+
9+### TDD
10+
11+For every change, find the corresponding test and ensure it passes.
12+Ensure that the tests accurately test the interfaces, adjusting tests as needed to accurately test the intention of the code. Do not change tests to fit the implementation just to make them pass. The tests need to accurately indicate the intention of the code, and the code needs to be made to pass the tests, not the other way around.
13+
14+* For ruby files, tests are in /rspec
15+* For typescript files, tests are in /app/frontend/tests
