| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 0 | 0% |
What each file covers
Sections
0 shared · 0 only in A · 1 only in B- + REQUIRED FOR EVERY INTERACTION
Commands
neither file has anySection tags
0 shared · 1 only in A · 0 only in B- − code-style
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/inventory.mdc
@@ +1 @@
1---
2description:
3globs:
4alwaysApply: true
5---
6# REQUIRED FOR EVERY INTERACTION
7
81. Read .cursor/inventory.mdx at the start of each interaction
92. Before ending ANY response, if you've learned anything useful about project-specific architectural details that are NOT immediately obvious from reading the code, you MUST update .cursor/inventory.mdx with this information
103. When updating .cursor/inventory.mdx:
11 - Only add new information not already documented
12 - Place information in the appropriate section
13 - If no appropriate section exists, create one
14 - ONLY document project-specific architectural decisions, custom patterns, and non-obvious implementation details
15
@@ −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.
6+# REQUIRED FOR EVERY INTERACTION
7+
8+1. Read .cursor/inventory.mdx at the start of each interaction
9+2. Before ending ANY response, if you've learned anything useful about project-specific architectural details that are NOT immediately obvious from reading the code, you MUST update .cursor/inventory.mdx with this information
10+3. When updating .cursor/inventory.mdx:
11+ - Only add new information not already documented
12+ - Place information in the appropriate section
13+ - If no appropriate section exists, create one
14+ - ONLY document project-specific architectural decisions, custom patterns, and non-obvious implementation details
1615
