lerelais-front-library 0.1.0

package/.cursor/skills/project-structure/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: project-structure
+description: Conventions de structure des répertoires et fichiers d'un projet React TypeScript (organisation par feature, nommage, imports, barrels). À utiliser quand on crée un nouveau fichier, composant, hook, feature, ou quand on réorganise le code.
+---
+
+# Structure du projet
+
+## Arborescence cible
+```
+src/
+├── components/          # Composants UI partagés, sans logique métier
+│   └── Button/
+│       ├── Button.tsx
+│       ├── Button.test.tsx
+│       ├── Button.stories.tsx
+│       └── index.ts
+├── hooks/               # Hooks génériques réutilisables
+├── lib/                 # Utilitaires, clients (axios, dayjs…), config
+├── types/               # Types globaux partagés
+├── styles/              # Styles globaux, tokens
+└── test/                # setup.ts, utils.tsx, mocks MSW
+e2e/                     # Tests Playwright
+```
+
+## Règles
+1. **Organisation par feature**, pas par type technique : tout ce qui concerne « panier » vit dans `features/cart/`.
+2. Une feature n'importe **jamais** les fichiers internes d'une autre feature : uniquement via son `index.ts`.
+3. Sens des dépendances : `app` → `features` → `components` / `hooks` / `lib`. Jamais l'inverse. `components/` ne dépend pas de `features/`.
+4. Un composant = un dossier contenant `.tsx`, `.test.tsx`, `.stories.tsx` (si UI partagée) et `index.ts`.
+5. Colocaliser : tests, stories et styles à côté du fichier concerné.
+6. Ne créer un dossier `hooks/`, `api/` ou `types.ts` dans une feature que s'il est nécessaire.
+
+## Nommage
+| Élément | Convention | Exemple |
+|---|---|---|
+| Composant | PascalCase | `UserCard.tsx` |
+| Hook | camelCase, préfixe `use` | `useCart.ts` |
+| Utilitaire | camelCase | `formatPrice.ts` |
+| Dossier | kebab-case (features) / PascalCase (composants) | `user-profile/`, `Button/` |
+| Type / Interface | PascalCase, sans préfixe `I` | `CartItem` |
+| Constante | UPPER_SNAKE_CASE | `MAX_ITEMS` |
+
+## Imports
+- Alias `@/` vers `src/` (configurés dans `tsconfig.json` **et** `vite.config.ts`).
+- Ordre : externes → alias `@/` → relatifs → styles.
+- Pas de barrel `index.ts` géant à la racine de `components/` (casse le tree-shaking et ralentit les tests) : un `index.ts` par composant ou feature seulement.
+
+## Avant de créer un fichier
+1. Vérifier qu'un équivalent n'existe pas déjà.
+2. Choisir : feature ou UI partagée ?
+3. Créer le fichier au bon endroit avec son test associé.

package/.cursor/skills/storybook-react/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: storybook-react
+description: Installer, configurer et écrire des stories Storybook (CSF3) pour les composants React TypeScript, avec tests d'interaction et addon a11y. À utiliser quand on crée ou modifie un composant UI partagé, ou quand on demande d'ajouter/corriger Storybook.
+---
+
+# Storybook pour React
+
+## Installation (si absent)
+```bash
+npx storybook@latest init
+```
+Addons à garder/ajouter : `@storybook/addon-essentials`, `@storybook/addon-a11y`, `@storybook/addon-interactions`.
+
+Scripts :
+```json
+"storybook": "storybook dev -p 6006",
+"build-storybook": "storybook build"
+```
+
+## Configuration
+- `.storybook/main.ts` : `stories: ['../src/**/*.stories.@(ts|tsx)']`, alias `@/` identique à Vite, `docs: { autodocs: 'tag' }`.
+- `.storybook/preview.ts` : importer les styles globaux, ajouter les décorateurs de providers (thème, router, i18n…), `parameters.controls` pour les matchers `color` et `date`.
+
+## Écrire une story (format CSF3, typé)
+```tsx
+import type { Meta, StoryObj } from '@storybook/react';
+import { Button } from './Button';
+
+const meta = {
+  title: 'Components/Button',
+  component: Button,
+  tags: ['autodocs'],
+  args: { children: 'Valider' },
+} satisfies Meta<typeof Button>;
+
+export default meta;
+type Story = StoryObj<typeof meta>;
+
+export const Primary: Story = { args: { variant: 'primary' } };
+export const Disabled: Story = { args: { disabled: true } };
+```
+
+## Règles
+1. Fichier `Composant.stories.tsx` **colocalisé** avec le composant.
+2. `title` = chemin hiérarchique (`Components/…`, `Features/<feature>/…`).
+3. Une story par **état significatif** : défaut, variantes, désactivé, chargement, erreur, vide, contenu long.
+4. Utiliser `args` et `argTypes` pour les contrôles ; pas de données en dur dans le JSX.
+5. Composants avec interactions : ajouter une fonction `play` (`@storybook/test` : `userEvent`, `expect`, `within`).
+6. Composants dépendant de l'API : mocker avec MSW (`msw-storybook-addon`), pas de vrais appels.
+7. Vérifier l'onglet **Accessibility** : aucune violation avant de valider.
+8. Ne pas dupliquer les tests unitaires : la story documente et vérifie le rendu, Vitest vérifie la logique.
+
+## Option : réutiliser les stories comme tests
+Avec `@storybook/experimental-addon-test` ou `composeStories`, on peut exécuter les stories dans Vitest pour éviter d'écrire deux fois les mêmes cas.
+
+## Checklist
+- [ ] Toutes les variantes visibles dans `npm run storybook`
+- [ ] `npm run build-storybook` passe sans erreur
+- [ ] Addon a11y sans violation
+- [ ] Props documentées (JSDoc dans le type, visibles en autodocs)

package/.cursor/skills/testing-react/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: testing-react
+description: Mettre en place et écrire les tests unitaires (Vitest + React Testing Library) et fonctionnels/E2E (Playwright) dans un projet React TypeScript. À utiliser quand on crée un composant, un hook, une fonction utilitaire, une feature, ou quand on demande d'ajouter/corriger des tests.
+---
+
+# Tests React : unitaires, intégration, fonctionnels
+
+## Stack
+- **Unitaires / intégration** : Vitest + @testing-library/react + @testing-library/user-event + @testing-library/jest-dom
+- **Mock réseau** : MSW (Mock Service Worker)
+- **Fonctionnels / E2E** : Playwright
+
+## Installation (si absente)
+```bash
+npm i -D vitest jsdom @testing-library/react @testing-library/user-event @testing-library/jest-dom msw @playwright/test
+npx playwright install
+```
+
+## Configuration
+`vitest.config.ts` : environnement `jsdom`, `globals: true`, `setupFiles: ['./src/test/setup.ts']`, coverage `v8`.
+`src/test/setup.ts` : importer `@testing-library/jest-dom/vitest` et démarrer/arrêter le serveur MSW (`beforeAll`, `afterEach` reset, `afterAll`).
+`playwright.config.ts` : `testDir: './e2e'`, `webServer` qui lance l'app, projet Chromium au minimum.
+
+Scripts `package.json` :
+```json
+"test": "vitest",
+"test:run": "vitest run",
+"test:coverage": "vitest run --coverage",
+"e2e": "playwright test"
+```
+
+## Règles d'écriture
+1. Fichier de test **colocalisé** : `Button.tsx` → `Button.test.tsx`.
+2. Nommage : `describe('<Composant>')` puis `it('should <comportement observable>')`.
+3. Structure **Arrange / Act / Assert**, un comportement par test.
+4. Requêtes RTL par ordre de priorité : `getByRole` > `getByLabelText` > `getByText` > `getByTestId` (dernier recours).
+5. Toujours `userEvent` (pas `fireEvent`) ; `await` sur les interactions.
+6. Tester le **comportement visible par l'utilisateur**, pas l'implémentation (pas de test sur l'état interne ou les noms de fonctions privées).
+7. Mocker uniquement les frontières (réseau via MSW, horloge, stockage) ; ne pas mocker ce qu'on teste.
+8. Hooks : `renderHook` ; composants dépendant de providers : utiliser un `renderWithProviders` dans `src/test/utils.tsx`.
+9. Pas de `setTimeout` dans les tests : utiliser `findBy*` ou `waitFor`.
+
+## Ce qu'il faut tester
+- **Unitaire** : fonctions pures, hooks, composants UI isolés (états : défaut, chargement, erreur, vide).
+- **Intégration** : une feature complète avec ses providers et MSW.
+- **E2E (Playwright)** : parcours critiques uniquement (auth, création, paiement…), dans `e2e/`. Sélecteurs par `getByRole`/`getByLabel`, jamais par classe CSS.
+
+## Checklist avant de terminer
+- [ ] Le test échoue si on casse le comportement (vérifier qu'il n'est pas faux-positif)
+- [ ] `npm run test:run` passe
+- [ ] Aucun `.only` / `.skip` oublié
+- [ ] Nouveau composant = au minimum un test de rendu + un test d'interaction

package/README.md

@@ -0,0 +1,93 @@
+# library
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+* [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
+* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/lerelais1/library.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+* [Set up project integrations](https://gitlab.com/lerelais1/library/-/settings/integrations)
+
+## Collaborate with your team
+
+* [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
+* [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
+* [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
+* [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
+* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+* [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
+* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
+* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
+* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
+* [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

package/index.html

@@ -0,0 +1,18 @@
+<!doctype html>
+<html lang="fr">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>LeRelais — Bibliothèque UI</title>
+    <link rel="preconnect" href="https://fonts.googleapis.com" />
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
+    <link
+      href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap"
+      rel="stylesheet"
+    />
+  </head>
+  <body>
+    <div id="root"></div>
+    <script type="module" src="/src/main.tsx"></script>
+  </body>
+</html>

package/package.json

@@ -0,0 +1,34 @@
+{
+  "name": "lerelais-front-library",
+  "version": "0.1.0",
+  "type": "module",
+  "scripts": {
+    "dev": "vite",
+    "build": "tsc -b && vite build",
+    "preview": "vite preview",
+    "test": "vitest",
+    "test:run": "vitest run",
+    "test:coverage": "vitest run --coverage",
+    "storybook": "storybook dev -p 6006",
+    "build-storybook": "storybook build"
+  },
+  "dependencies": {
+    "react": "^19.1.1",
+    "react-dom": "^19.1.1"
+  },
+  "devDependencies": {
+    "@testing-library/jest-dom": "^6.8.0",
+    "@testing-library/react": "^16.3.0",
+    "@testing-library/user-event": "^14.6.1",
+    "@types/node": "^24.5.2",
+    "@types/react": "^19.1.12",
+    "@types/react-dom": "^19.1.9",
+    "@vitejs/plugin-react": "^5.0.2",
+    "@vitest/coverage-v8": "^3.2.4",
+    "jsdom": "^26.1.0",
+    "msw": "^2.11.1",
+    "typescript": "~5.9.2",
+    "vite": "^7.1.5",
+    "vitest": "^3.2.4"
+  }
+}

package/src/App.css

@@ -0,0 +1,49 @@
+.catalog {
+  display: flex;
+  flex-direction: column;
+  gap: 32px;
+  padding-bottom: 48px;
+  background: #fff;
+}
+
+.catalog-hero {
+  padding: 42px 64px 0;
+}
+
+.catalog-hero p {
+  margin: 0;
+  color: var(--color-primary);
+  font-weight: 700;
+}
+
+.catalog-hero h1,
+section h2 {
+  margin: 0 0 16px;
+}
+
+section {
+  display: flex;
+  flex-direction: column;
+  gap: 16px;
+  padding: 0 64px;
+}
+
+.row {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 16px;
+  align-items: flex-start;
+}
+
+.split {
+  display: grid;
+  grid-template-columns: 248px 1fr;
+  gap: 24px;
+  align-items: start;
+}
+
+.dark {
+  padding: 16px;
+  border-radius: 12px;
+  background: var(--color-sidebar);
+}