Files
posthog.com/.cursor/rules/components.mdc
Cory Watilo 15c925b43d version bump (#12254)
Co-authored-by: Cory Watilo <corywatilo@gmail.com>
Co-authored-by: Eli Kinsey <eli@ekinsey.dev>
Co-authored-by: Lucas Faria <12522524+lucasheriques@users.noreply.github.com>
Co-authored-by: Ben White <ben@posthog.com>
Co-authored-by: Juraj Majerik <juro.majerik@gmail.com>
Co-authored-by: Rafael Audibert <32079912+rafaeelaudibert@users.noreply.github.com>
2025-09-10 16:33:30 +00:00

33 lines
849 B
Plaintext

---
description:
globs:
alwaysApply: true
---
# Component structure and naming
**Radix UI**
- Custom components go in `/src/components/RadixUI`
### Radix UI
We use Radix UI components. To get them to match our design, we typically create our own version of these components and place them in `/src/components/RadixUI`.
Use `Radix` prefix for imports, then wrap as `<Tabs />`, etc. Example:
```
import { Tabs as RadixTabs } from 'radix-ui'
```
This allows us to have simple naming conventions for our components like `<Tabs />`.
### Other components
We also have custom built components (for things that are outside the scope of Radix primatives). They start with `OS` in the name, like:
1. ``/src/components/OSButton`
1. `/src/components/OSFieldset`
1. `/src/components/OSIcons`
1. `/src/components/OSTable`
1. ``/src/components/OSTabs`