diff --git a/.ai-rules.md b/.ai-rules.md deleted file mode 100644 index 06de1ba..0000000 --- a/.ai-rules.md +++ /dev/null @@ -1,30 +0,0 @@ -# Regles de developpement du projet - -## Stack -- Backend : Laravel 12 + Filament v4 -- Frontend : React + Tailwind -- Tests : PHPUnit 11 - -## Architecture Backend -- Utiliser des Services -- Ne PAS utiliser de Repository pattern -- Les Controllers doivent rester fins -- Une feature = un service dedie -- Respecter la structure existante du projet - -## Tests -- Toute nouvelle feature DOIT inclure ses tests -- Tests clairs, lisibles, orientes metier -- Pas de mocks inutiles - -## Style de code -- Pas d'emoji -- Pas de commentaires inutiles -- Commentaires uniquement si necessaire et explicites -- Code simple > code "clever" - -## Comportement attendu -- Ne jamais modifier le code sans validation explicite -- Ne jamais refactorer sans demande explicite -- Toujours proposer un plan avant d'ecrire du code -- Toujours expliquer brievement ce qui va etre ajoute/modifie diff --git a/.claude/settings.local.json b/.claude/settings.local.json deleted file mode 100644 index 8dc8d9f..0000000 --- a/.claude/settings.local.json +++ /dev/null @@ -1,25 +0,0 @@ -{ - "permissions": { - "allow": [ - "mcp__laravel-boost__application-info", - "mcp__laravel-boost__database-schema", - "mcp__laravel-boost__list-routes", - "Bash(php artisan make:migration:*)", - "mcp__laravel-boost__search-docs", - "Bash(vendor/bin/pint:*)", - "Bash(php artisan test:*)", - "Bash(php artisan migrate:*)", - "Bash(php artisan make:filament-relation-manager:*)", - "mcp__laravel-boost__list-artisan-commands", - "mcp__laravel-boost__tinker", - "Bash(php artisan make:job:*)", - "mcp__laravel-boost__last-error", - "Bash(php artisan view:clear:*)", - "mcp__laravel-boost__database-query" - ] - }, - "enableAllProjectMcpServers": true, - "enabledMcpjsonServers": [ - "laravel-boost" - ] -} diff --git a/.claude/skills/inertia-react-development/SKILL.md b/.claude/skills/inertia-react-development/SKILL.md deleted file mode 100644 index 12a308c..0000000 --- a/.claude/skills/inertia-react-development/SKILL.md +++ /dev/null @@ -1,369 +0,0 @@ ---- -name: inertia-react-development -description: >- - Develops Inertia.js v2 React client-side applications. Activates when creating - React pages, forms, or navigation; using ,
, useForm, or router; - working with deferred props, prefetching, or polling; or when user mentions - React with Inertia, React pages, React forms, or React navigation. ---- - -# Inertia React Development - -## When to Apply - -Activate this skill when: - -- Creating or modifying React page components for Inertia -- Working with forms in React (using `` or `useForm`) -- Implementing client-side navigation with `` or `router` -- Using v2 features: deferred props, prefetching, or polling -- Building React-specific features with the Inertia protocol - -## Documentation - -Use `search-docs` for detailed Inertia v2 React patterns and documentation. - -## Basic Usage - -### Page Components Location - -React page components should be placed in the `resources/js/pages` directory. - -### Page Component Structure - - - -export default function UsersIndex({ users }) { - return ( -
-

Users

-
    - {users.map(user =>
  • {user.name}
    • )} -
-
- ) -} - - - -## Client-Side Navigation - -### Basic Link Component - -Use `` for client-side navigation instead of traditional `` tags: - - - -import { Link, router } from '@inertiajs/react' - -Home -Users -View User - - - -### Link with Method - - - -import { Link } from '@inertiajs/react' - - - Logout - - - - -### Prefetching - -Prefetch pages to improve perceived performance: - - - -import { Link } from '@inertiajs/react' - - - Users - - - - -### Programmatic Navigation - - - -import { router } from '@inertiajs/react' - -function handleClick() { - router.visit('/users') -} - -// Or with options -router.visit('/users', { - method: 'post', - data: { name: 'John' }, - onSuccess: () => console.log('Success!'), -}) - - - -## Form Handling - -### Form Component (Recommended) - -The recommended way to build forms is with the `` component: - - - -import { Form } from '@inertiajs/react' - -export default function CreateUser() { - return ( - - {({ errors, processing, wasSuccessful }) => ( - <> - - {errors.name &&
{errors.name}
} - - - {errors.email &&
{errors.email}
} - - - - {wasSuccessful &&
User created!
} - - )} - - ) -} - - - -### Form Component With All Props - - - -import { Form } from '@inertiajs/react' - -
- {({ - errors, - hasErrors, - processing, - progress, - wasSuccessful, - recentlySuccessful, - clearErrors, - resetAndClearErrors, - defaults, - isDirty, - reset, - submit - }) => ( - <> - - {errors.name &&
{errors.name}
} - - - - {progress && ( - - {progress.percentage}% - - )} - - {wasSuccessful &&
Saved!
} - - )} -
- - - -### Form Component Reset Props - -The `
` component supports automatic resetting: - -- `resetOnError` - Reset form data when the request fails -- `resetOnSuccess` - Reset form data when the request succeeds -- `setDefaultsOnSuccess` - Update default values on success - -Use the `search-docs` tool with a query of `form component resetting` for detailed guidance. - - - -import { Form } from '@inertiajs/react' - - - {({ errors, processing, wasSuccessful }) => ( - <> - - {errors.name &&
{errors.name}
} - - - - )} - - -
- -Forms can also be built using the `useForm` helper for more programmatic control. Use the `search-docs` tool with a query of `useForm helper` for guidance. - -### `useForm` Hook - -For more programmatic control or to follow existing conventions, use the `useForm` hook: - - - -import { useForm } from '@inertiajs/react' - -export default function CreateUser() { - const { data, setData, post, processing, errors, reset } = useForm({ - name: '', - email: '', - password: '', - }) - - function submit(e) { - e.preventDefault() - post('/users', { - onSuccess: () => reset('password'), - }) - } - - return ( -
- setData('name', e.target.value)} - /> - {errors.name &&
{errors.name}
} - - setData('email', e.target.value)} - /> - {errors.email &&
{errors.email}
} - - setData('password', e.target.value)} - /> - {errors.password &&
{errors.password}
} - - -
- ) -} - - - -## Inertia v2 Features - -### Deferred Props - -Use deferred props to load data after initial page render: - - - -export default function UsersIndex({ users }) { - // users will be undefined initially, then populated - return ( -
-

Users

- {!users ? ( -
-
-
-
- ) : ( -
    - {users.map(user => ( -
  • {user.name}
    • - ))} -
- )} -
- ) -} - - - -### Polling - -Automatically refresh data at intervals: - - - -import { router } from '@inertiajs/react' -import { useEffect } from 'react' - -export default function Dashboard({ stats }) { - useEffect(() => { - const interval = setInterval(() => { - router.reload({ only: ['stats'] }) - }, 5000) // Poll every 5 seconds - - return () => clearInterval(interval) - }, []) - - return ( -
-

Dashboard

-
Active Users: {stats.activeUsers}
-
- ) -} - - - -### WhenVisible (Infinite Scroll) - -Load more data when user scrolls to a specific element: - - - -import { WhenVisible } from '@inertiajs/react' - -export default function UsersList({ users }) { - return ( -
- {users.data.map(user => ( -
{user.name}
- ))} - - {users.next_page_url && ( - Loading more...
} - /> - )} - - ) -} - - - -## Common Pitfalls - -- Using traditional `
` links instead of Inertia's `` component (breaks SPA behavior) -- Forgetting to add loading states (skeleton screens) when using deferred props -- Not handling the `undefined` state of deferred props before data loads -- Using `
` without preventing default submission (use `` component or `e.preventDefault()`) -- Forgetting to check if `` component is available in your Inertia version \ No newline at end of file diff --git a/.claude/skills/tailwindcss-development/SKILL.md b/.claude/skills/tailwindcss-development/SKILL.md deleted file mode 100644 index 12bd896..0000000 --- a/.claude/skills/tailwindcss-development/SKILL.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -name: tailwindcss-development -description: >- - Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, - working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, - typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, - hero section, cards, buttons, or any visual/UI changes. ---- - -# Tailwind CSS Development - -## When to Apply - -Activate this skill when: - -- Adding styles to components or pages -- Working with responsive design -- Implementing dark mode -- Extracting repeated patterns into components -- Debugging spacing or layout issues - -## Documentation - -Use `search-docs` for detailed Tailwind CSS v4 patterns and documentation. - -## Basic Usage - -- Use Tailwind CSS classes to style HTML. Check and follow existing Tailwind conventions in the project before introducing new patterns. -- Offer to extract repeated patterns into components that match the project's conventions (e.g., Blade, JSX, Vue). -- Consider class placement, order, priority, and defaults. Remove redundant classes, add classes to parent or child elements carefully to reduce repetition, and group elements logically. - -## Tailwind CSS v4 Specifics - -- Always use Tailwind CSS v4 and avoid deprecated utilities. -- `corePlugins` is not supported in Tailwind v4. - -### CSS-First Configuration - -In Tailwind v4, configuration is CSS-first using the `@theme` directive — no separate `tailwind.config.js` file is needed: - - -@theme { - --color-brand: oklch(0.72 0.11 178); -} - - -### Import Syntax - -In Tailwind v4, import Tailwind with a regular CSS `@import` statement instead of the `@tailwind` directives used in v3: - - -- @tailwind base; -- @tailwind components; -- @tailwind utilities; -+ @import "tailwindcss"; - - -### Replaced Utilities - -Tailwind v4 removed deprecated utilities. Use the replacements shown below. Opacity values remain numeric. - -| Deprecated | Replacement | -|------------|-------------| -| bg-opacity-* | bg-black/* | -| text-opacity-* | text-black/* | -| border-opacity-* | border-black/* | -| divide-opacity-* | divide-black/* | -| ring-opacity-* | ring-black/* | -| placeholder-opacity-* | placeholder-black/* | -| flex-shrink-* | shrink-* | -| flex-grow-* | grow-* | -| overflow-ellipsis | text-ellipsis | -| decoration-slice | box-decoration-slice | -| decoration-clone | box-decoration-clone | - -## Spacing - -Use `gap` utilities instead of margins for spacing between siblings: - - -
-
Item 1
-
Item 2
-
- - -## Dark Mode - -If existing pages and components support dark mode, new pages and components must support it the same way, typically using the `dark:` variant: - - -
- Content adapts to color scheme -
- - -## Common Patterns - -### Flexbox Layout - - -
-
Left content
-
Right content
-
- - -### Grid Layout - - -
-
Card 1
-
Card 2
-
Card 3
-
- - -## Common Pitfalls - -- Using deprecated v3 utilities (bg-opacity-*, flex-shrink-*, etc.) -- Using `@tailwind` directives instead of `@import "tailwindcss"` -- Trying to use `tailwind.config.js` instead of CSS `@theme` directive -- Using margins for spacing between siblings instead of gap utilities -- Forgetting to add dark mode variants when the project uses dark mode \ No newline at end of file diff --git a/.claude/skills/wayfinder-development/SKILL.md b/.claude/skills/wayfinder-development/SKILL.md deleted file mode 100644 index d8d586e..0000000 --- a/.claude/skills/wayfinder-development/SKILL.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -name: wayfinder-development -description: >- - Activates whenever referencing backend routes in frontend components. Use when - importing from @/actions or @/routes, calling Laravel routes from TypeScript, - or working with Wayfinder route functions. ---- - -# Wayfinder Development - -## When to Apply - -Activate whenever referencing backend routes in frontend components: -- Importing from `@/actions/` or `@/routes/` -- Calling Laravel routes from TypeScript/JavaScript -- Creating links or navigation to backend endpoints - -## Documentation - -Use `search-docs` for detailed Wayfinder patterns and documentation. - -## Quick Reference - -### Generate Routes - -Run after route changes if Vite plugin isn't installed: - -php artisan wayfinder:generate --no-interaction - -For form helpers, use `--with-form` flag: - -php artisan wayfinder:generate --with-form --no-interaction - -### Import Patterns - - - -// Named imports for tree-shaking (preferred)... -import { show, store, update } from '@/actions/App/Http/Controllers/PostController' - -// Named route imports... -import { show as postShow } from '@/routes/post' - - - -### Common Methods - - - -// Get route object... -show(1) // { url: "/posts/1", method: "get" } - -// Get URL string... -show.url(1) // "/posts/1" - -// Specific HTTP methods... -show.get(1) -store.post() -update.patch(1) -destroy.delete(1) - -// Form attributes for HTML forms... -store.form() // { action: "/posts", method: "post" } - -// Query parameters... -show(1, { query: { page: 1 } }) // "/posts/1?page=1" - - - -## Wayfinder + Inertia - -Use Wayfinder with the `` component: - - - - -
- -## Verification - -1. Run `php artisan wayfinder:generate` to regenerate routes if Vite plugin isn't installed -2. Check TypeScript imports resolve correctly -3. Verify route URLs match expected paths - -## Common Pitfalls - -- Using default imports instead of named imports (breaks tree-shaking) -- Forgetting to regenerate after route changes -- Not using type-safe parameter objects for route model binding \ No newline at end of file diff --git a/.gitignore b/.gitignore index 7e3223a..976aa52 100644 --- a/.gitignore +++ b/.gitignore @@ -27,6 +27,8 @@ gitlab-ci.yml # Agents /.claude /.junie +.claude +.junie .ai-rules.md CLAUDE.md database-schema.md diff --git a/.junie/guidelines.md b/.junie/guidelines.md deleted file mode 100644 index db1f905..0000000 --- a/.junie/guidelines.md +++ /dev/null @@ -1,288 +0,0 @@ - -=== foundation rules === - -# Laravel Boost Guidelines - -The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to ensure the best experience when building Laravel applications. - -## Foundational Context - -This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions. - -- php - 8.3.28 -- filament/filament (FILAMENT) - v4 -- inertiajs/inertia-laravel (INERTIA) - v2 -- laravel/fortify (FORTIFY) - v1 -- laravel/framework (LARAVEL) - v12 -- laravel/prompts (PROMPTS) - v0 -- laravel/wayfinder (WAYFINDER) - v0 -- livewire/livewire (LIVEWIRE) - v3 -- laravel/mcp (MCP) - v0 -- laravel/pint (PINT) - v1 -- laravel/sail (SAIL) - v1 -- phpunit/phpunit (PHPUNIT) - v11 -- @inertiajs/react (INERTIA) - v2 -- react (REACT) - v19 -- tailwindcss (TAILWINDCSS) - v4 -- @laravel/vite-plugin-wayfinder (WAYFINDER) - v0 -- eslint (ESLINT) - v9 -- prettier (PRETTIER) - v3 - -## Skills Activation - -This project has domain-specific skills available. You MUST activate the relevant skill whenever you work in that domain—don't wait until you're stuck. - -- `wayfinder-development` — Activates whenever referencing backend routes in frontend components. Use when importing from @/actions or @/routes, calling Laravel routes from TypeScript, or working with Wayfinder route functions. -- `inertia-react-development` — Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation. -- `tailwindcss-development` — Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes. - -## Conventions - -- You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, and naming. -- Use descriptive names for variables and methods. For example, `isRegisteredForDiscounts`, not `discount()`. -- Check for existing components to reuse before writing a new one. - -## Verification Scripts - -- Do not create verification scripts or tinker when tests cover that functionality and prove they work. Unit and feature tests are more important. - -## Application Structure & Architecture - -- Stick to existing directory structure; don't create new base folders without approval. -- Do not change the application's dependencies without approval. - -## Frontend Bundling - -- If the user doesn't see a frontend change reflected in the UI, it could mean they need to run `npm run build`, `npm run dev`, or `composer run dev`. Ask them. - -## Documentation Files - -- You must only create documentation files if explicitly requested by the user. - -## Replies - -- Be concise in your explanations - focus on what's important rather than explaining obvious details. - -=== boost rules === - -# Laravel Boost - -- Laravel Boost is an MCP server that comes with powerful tools designed specifically for this application. Use them. - -## Artisan - -- Use the `list-artisan-commands` tool when you need to call an Artisan command to double-check the available parameters. - -## URLs - -- Whenever you share a project URL with the user, you should use the `get-absolute-url` tool to ensure you're using the correct scheme, domain/IP, and port. - -## Tinker / Debugging - -- You should use the `tinker` tool when you need to execute PHP to debug code or query Eloquent models directly. -- Use the `database-query` tool when you only need to read from the database. - -## Reading Browser Logs With the `browser-logs` Tool - -- You can read browser logs, errors, and exceptions using the `browser-logs` tool from Boost. -- Only recent browser logs will be useful - ignore old logs. - -## Searching Documentation (Critically Important) - -- Boost comes with a powerful `search-docs` tool you should use before trying other approaches when working with Laravel or Laravel ecosystem packages. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation for the user's circumstance. You should pass an array of packages to filter on if you know you need docs for particular packages. -- Search the documentation before making code changes to ensure we are taking the correct approach. -- Use multiple, broad, simple, topic-based queries at once. For example: `['rate limiting', 'routing rate limiting', 'routing']`. The most relevant results will be returned first. -- Do not add package names to queries; package information is already shared. For example, use `test resource table`, not `filament 4 test resource table`. - -### Available Search Syntax - -1. Simple Word Searches with auto-stemming - query=authentication - finds 'authenticate' and 'auth'. -2. Multiple Words (AND Logic) - query=rate limit - finds knowledge containing both "rate" AND "limit". -3. Quoted Phrases (Exact Position) - query="infinite scroll" - words must be adjacent and in that order. -4. Mixed Queries - query=middleware "rate limit" - "middleware" AND exact phrase "rate limit". -5. Multiple Queries - queries=["authentication", "middleware"] - ANY of these terms. - -=== php rules === - -# PHP - -- Always use curly braces for control structures, even for single-line bodies. - -## Constructors - -- Use PHP 8 constructor property promotion in `__construct()`. - - public function __construct(public GitHub $github) { } -- Do not allow empty `__construct()` methods with zero parameters unless the constructor is private. - -## Type Declarations - -- Always use explicit return type declarations for methods and functions. -- Use appropriate PHP type hints for method parameters. - - -protected function isAccessible(User $user, ?string $path = null): bool -{ - ... -} - - -## Enums - -- Typically, keys in an Enum should be TitleCase. For example: `FavoritePerson`, `BestLake`, `Monthly`. - -## Comments - -- Prefer PHPDoc blocks over inline comments. Never use comments within the code itself unless the logic is exceptionally complex. - -## PHPDoc Blocks - -- Add useful array shape type definitions when appropriate. - -=== inertia-laravel/core rules === - -# Inertia - -- Inertia creates fully client-side rendered SPAs without modern SPA complexity, leveraging existing server-side patterns. -- Components live in `resources/js/pages` (unless specified in `vite.config.js`). Use `Inertia::render()` for server-side routing instead of Blade views. -- ALWAYS use `search-docs` tool for version-specific Inertia documentation and updated code examples. -- IMPORTANT: Activate `inertia-react-development` when working with Inertia client-side patterns. - -=== inertia-laravel/v2 rules === - -# Inertia v2 - -- Use all Inertia features from v1 and v2. Check the documentation before making changes to ensure the correct approach. -- New features: deferred props, infinite scrolling (merging props + `WhenVisible`), lazy loading on scroll, polling, prefetching. -- When using deferred props, add an empty state with a pulsing or animated skeleton. - -=== laravel/core rules === - -# Do Things the Laravel Way - -- Use `php artisan make:` commands to create new files (i.e. migrations, controllers, models, etc.). You can list available Artisan commands using the `list-artisan-commands` tool. -- If you're creating a generic PHP class, use `php artisan make:class`. -- Pass `--no-interaction` to all Artisan commands to ensure they work without user input. You should also pass the correct `--options` to ensure correct behavior. - -## Database - -- Always use proper Eloquent relationship methods with return type hints. Prefer relationship methods over raw queries or manual joins. -- Use Eloquent models and relationships before suggesting raw database queries. -- Avoid `DB::`; prefer `Model::query()`. Generate code that leverages Laravel's ORM capabilities rather than bypassing them. -- Generate code that prevents N+1 query problems by using eager loading. -- Use Laravel's query builder for very complex database operations. - -### Model Creation - -- When creating new models, create useful factories and seeders for them too. Ask the user if they need any other things, using `list-artisan-commands` to check the available options to `php artisan make:model`. - -### APIs & Eloquent Resources - -- For APIs, default to using Eloquent API Resources and API versioning unless existing API routes do not, then you should follow existing application convention. - -## Controllers & Validation - -- Always create Form Request classes for validation rather than inline validation in controllers. Include both validation rules and custom error messages. -- Check sibling Form Requests to see if the application uses array or string based validation rules. - -## Authentication & Authorization - -- Use Laravel's built-in authentication and authorization features (gates, policies, Sanctum, etc.). - -## URL Generation - -- When generating links to other pages, prefer named routes and the `route()` function. - -## Queues - -- Use queued jobs for time-consuming operations with the `ShouldQueue` interface. - -## Configuration - -- Use environment variables only in configuration files - never use the `env()` function directly outside of config files. Always use `config('app.name')`, not `env('APP_NAME')`. - -## Testing - -- When creating models for tests, use the factories for the models. Check if the factory has custom states that can be used before manually setting up the model. -- Faker: Use methods such as `$this->faker->word()` or `fake()->randomDigit()`. Follow existing conventions whether to use `$this->faker` or `fake()`. -- When creating tests, make use of `php artisan make:test [options] {name}` to create a feature test, and pass `--unit` to create a unit test. Most tests should be feature tests. - -## Vite Error - -- If you receive an "Illuminate\Foundation\ViteException: Unable to locate file in Vite manifest" error, you can run `npm run build` or ask the user to run `npm run dev` or `composer run dev`. - -=== laravel/v12 rules === - -# Laravel 12 - -- CRITICAL: ALWAYS use `search-docs` tool for version-specific Laravel documentation and updated code examples. -- Since Laravel 11, Laravel has a new streamlined file structure which this project uses. - -## Laravel 12 Structure - -- In Laravel 12, middleware are no longer registered in `app/Http/Kernel.php`. -- Middleware are configured declaratively in `bootstrap/app.php` using `Application::configure()->withMiddleware()`. -- `bootstrap/app.php` is the file to register middleware, exceptions, and routing files. -- `bootstrap/providers.php` contains application specific service providers. -- The `app\Console\Kernel.php` file no longer exists; use `bootstrap/app.php` or `routes/console.php` for console configuration. -- Console commands in `app/Console/Commands/` are automatically available and do not require manual registration. - -## Database - -- When modifying a column, the migration must include all of the attributes that were previously defined on the column. Otherwise, they will be dropped and lost. -- Laravel 12 allows limiting eagerly loaded records natively, without external packages: `$query->latest()->limit(10);`. - -### Models - -- Casts can and likely should be set in a `casts()` method on a model rather than the `$casts` property. Follow existing conventions from other models. - -=== wayfinder/core rules === - -# Laravel Wayfinder - -Wayfinder generates TypeScript functions for Laravel routes. Import from `@/actions/` (controllers) or `@/routes/` (named routes). - -- IMPORTANT: Activate `wayfinder-development` skill whenever referencing backend routes in frontend components. -- Invokable Controllers: `import StorePost from '@/actions/.../StorePostController'; StorePost()`. -- Parameter Binding: Detects route keys (`{post:slug}`) — `show({ slug: "my-post" })`. -- Query Merging: `show(1, { mergeQuery: { page: 2, sort: null } })` merges with current URL, `null` removes params. -- Inertia: Use `.form()` with `
` component or `form.submit(store())` with useForm. - -=== pint/core rules === - -# Laravel Pint Code Formatter - -- You must run `vendor/bin/pint --dirty --format agent` before finalizing changes to ensure your code matches the project's expected style. -- Do not run `vendor/bin/pint --test --format agent`, simply run `vendor/bin/pint --format agent` to fix any formatting issues. - -=== phpunit/core rules === - -# PHPUnit - -- This application uses PHPUnit for testing. All tests must be written as PHPUnit classes. Use `php artisan make:test --phpunit {name}` to create a new test. -- If you see a test using "Pest", convert it to PHPUnit. -- Every time a test has been updated, run that singular test. -- When the tests relating to your feature are passing, ask the user if they would like to also run the entire test suite to make sure everything is still passing. -- Tests should cover all happy paths, failure paths, and edge cases. -- You must not remove any tests or test files from the tests directory without approval. These are not temporary or helper files; these are core to the application. - -## Running Tests - -- Run the minimal number of tests, using an appropriate filter, before finalizing. -- To run all tests: `php artisan test --compact`. -- To run all tests in a file: `php artisan test --compact tests/Feature/ExampleTest.php`. -- To filter on a particular test name: `php artisan test --compact --filter=testName` (recommended after making a change to a related file). - -=== inertia-react/core rules === - -# Inertia + React - -- IMPORTANT: Activate `inertia-react-development` when working with Inertia React client-side patterns. - -=== tailwindcss/core rules === - -# Tailwind CSS - -- Always use existing Tailwind conventions; check project patterns before adding new ones. -- IMPORTANT: Always use `search-docs` tool for version-specific Tailwind CSS documentation and updated code examples. Never rely on training data. -- IMPORTANT: Activate `tailwindcss-development` every time you're working with a Tailwind CSS or styling-related task. - diff --git a/.junie/mcp/mcp.json b/.junie/mcp/mcp.json deleted file mode 100644 index 6fc2a75..0000000 --- a/.junie/mcp/mcp.json +++ /dev/null @@ -1,11 +0,0 @@ -{ - "mcpServers": { - "laravel-boost": { - "command": "/usr/local/bin/php", - "args": [ - "/app/artisan", - "boost:mcp" - ] - } - } -} \ No newline at end of file diff --git a/.junie/skills/inertia-react-development/SKILL.md b/.junie/skills/inertia-react-development/SKILL.md deleted file mode 100644 index 12a308c..0000000 --- a/.junie/skills/inertia-react-development/SKILL.md +++ /dev/null @@ -1,369 +0,0 @@ ---- -name: inertia-react-development -description: >- - Develops Inertia.js v2 React client-side applications. Activates when creating - React pages, forms, or navigation; using , , useForm, or router; - working with deferred props, prefetching, or polling; or when user mentions - React with Inertia, React pages, React forms, or React navigation. ---- - -# Inertia React Development - -## When to Apply - -Activate this skill when: - -- Creating or modifying React page components for Inertia -- Working with forms in React (using `` or `useForm`) -- Implementing client-side navigation with `` or `router` -- Using v2 features: deferred props, prefetching, or polling -- Building React-specific features with the Inertia protocol - -## Documentation - -Use `search-docs` for detailed Inertia v2 React patterns and documentation. - -## Basic Usage - -### Page Components Location - -React page components should be placed in the `resources/js/pages` directory. - -### Page Component Structure - - - -export default function UsersIndex({ users }) { - return ( -
-

Users

-
    - {users.map(user =>
  • {user.name}
    • )} -
-
- ) -} - - - -## Client-Side Navigation - -### Basic Link Component - -Use `` for client-side navigation instead of traditional `` tags: - - - -import { Link, router } from '@inertiajs/react' - -Home -Users -View User - - - -### Link with Method - - - -import { Link } from '@inertiajs/react' - - - Logout - - - - -### Prefetching - -Prefetch pages to improve perceived performance: - - - -import { Link } from '@inertiajs/react' - - - Users - - - - -### Programmatic Navigation - - - -import { router } from '@inertiajs/react' - -function handleClick() { - router.visit('/users') -} - -// Or with options -router.visit('/users', { - method: 'post', - data: { name: 'John' }, - onSuccess: () => console.log('Success!'), -}) - - - -## Form Handling - -### Form Component (Recommended) - -The recommended way to build forms is with the `` component: - - - -import { Form } from '@inertiajs/react' - -export default function CreateUser() { - return ( - - {({ errors, processing, wasSuccessful }) => ( - <> - - {errors.name &&
{errors.name}
} - - - {errors.email &&
{errors.email}
} - - - - {wasSuccessful &&
User created!
} - - )} - - ) -} - - - -### Form Component With All Props - - - -import { Form } from '@inertiajs/react' - -
- {({ - errors, - hasErrors, - processing, - progress, - wasSuccessful, - recentlySuccessful, - clearErrors, - resetAndClearErrors, - defaults, - isDirty, - reset, - submit - }) => ( - <> - - {errors.name &&
{errors.name}
} - - - - {progress && ( - - {progress.percentage}% - - )} - - {wasSuccessful &&
Saved!
} - - )} -
- - - -### Form Component Reset Props - -The `
` component supports automatic resetting: - -- `resetOnError` - Reset form data when the request fails -- `resetOnSuccess` - Reset form data when the request succeeds -- `setDefaultsOnSuccess` - Update default values on success - -Use the `search-docs` tool with a query of `form component resetting` for detailed guidance. - - - -import { Form } from '@inertiajs/react' - - - {({ errors, processing, wasSuccessful }) => ( - <> - - {errors.name &&
{errors.name}
} - - - - )} - - -
- -Forms can also be built using the `useForm` helper for more programmatic control. Use the `search-docs` tool with a query of `useForm helper` for guidance. - -### `useForm` Hook - -For more programmatic control or to follow existing conventions, use the `useForm` hook: - - - -import { useForm } from '@inertiajs/react' - -export default function CreateUser() { - const { data, setData, post, processing, errors, reset } = useForm({ - name: '', - email: '', - password: '', - }) - - function submit(e) { - e.preventDefault() - post('/users', { - onSuccess: () => reset('password'), - }) - } - - return ( -
- setData('name', e.target.value)} - /> - {errors.name &&
{errors.name}
} - - setData('email', e.target.value)} - /> - {errors.email &&
{errors.email}
} - - setData('password', e.target.value)} - /> - {errors.password &&
{errors.password}
} - - -
- ) -} - - - -## Inertia v2 Features - -### Deferred Props - -Use deferred props to load data after initial page render: - - - -export default function UsersIndex({ users }) { - // users will be undefined initially, then populated - return ( -
-

Users

- {!users ? ( -
-
-
-
- ) : ( -
    - {users.map(user => ( -
  • {user.name}
    • - ))} -
- )} -
- ) -} - - - -### Polling - -Automatically refresh data at intervals: - - - -import { router } from '@inertiajs/react' -import { useEffect } from 'react' - -export default function Dashboard({ stats }) { - useEffect(() => { - const interval = setInterval(() => { - router.reload({ only: ['stats'] }) - }, 5000) // Poll every 5 seconds - - return () => clearInterval(interval) - }, []) - - return ( -
-

Dashboard

-
Active Users: {stats.activeUsers}
-
- ) -} - - - -### WhenVisible (Infinite Scroll) - -Load more data when user scrolls to a specific element: - - - -import { WhenVisible } from '@inertiajs/react' - -export default function UsersList({ users }) { - return ( -
- {users.data.map(user => ( -
{user.name}
- ))} - - {users.next_page_url && ( - Loading more...
} - /> - )} - - ) -} - - - -## Common Pitfalls - -- Using traditional `
` links instead of Inertia's `` component (breaks SPA behavior) -- Forgetting to add loading states (skeleton screens) when using deferred props -- Not handling the `undefined` state of deferred props before data loads -- Using `
` without preventing default submission (use `` component or `e.preventDefault()`) -- Forgetting to check if `` component is available in your Inertia version \ No newline at end of file diff --git a/.junie/skills/tailwindcss-development/SKILL.md b/.junie/skills/tailwindcss-development/SKILL.md deleted file mode 100644 index 12bd896..0000000 --- a/.junie/skills/tailwindcss-development/SKILL.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -name: tailwindcss-development -description: >- - Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, - working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, - typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, - hero section, cards, buttons, or any visual/UI changes. ---- - -# Tailwind CSS Development - -## When to Apply - -Activate this skill when: - -- Adding styles to components or pages -- Working with responsive design -- Implementing dark mode -- Extracting repeated patterns into components -- Debugging spacing or layout issues - -## Documentation - -Use `search-docs` for detailed Tailwind CSS v4 patterns and documentation. - -## Basic Usage - -- Use Tailwind CSS classes to style HTML. Check and follow existing Tailwind conventions in the project before introducing new patterns. -- Offer to extract repeated patterns into components that match the project's conventions (e.g., Blade, JSX, Vue). -- Consider class placement, order, priority, and defaults. Remove redundant classes, add classes to parent or child elements carefully to reduce repetition, and group elements logically. - -## Tailwind CSS v4 Specifics - -- Always use Tailwind CSS v4 and avoid deprecated utilities. -- `corePlugins` is not supported in Tailwind v4. - -### CSS-First Configuration - -In Tailwind v4, configuration is CSS-first using the `@theme` directive — no separate `tailwind.config.js` file is needed: - - -@theme { - --color-brand: oklch(0.72 0.11 178); -} - - -### Import Syntax - -In Tailwind v4, import Tailwind with a regular CSS `@import` statement instead of the `@tailwind` directives used in v3: - - -- @tailwind base; -- @tailwind components; -- @tailwind utilities; -+ @import "tailwindcss"; - - -### Replaced Utilities - -Tailwind v4 removed deprecated utilities. Use the replacements shown below. Opacity values remain numeric. - -| Deprecated | Replacement | -|------------|-------------| -| bg-opacity-* | bg-black/* | -| text-opacity-* | text-black/* | -| border-opacity-* | border-black/* | -| divide-opacity-* | divide-black/* | -| ring-opacity-* | ring-black/* | -| placeholder-opacity-* | placeholder-black/* | -| flex-shrink-* | shrink-* | -| flex-grow-* | grow-* | -| overflow-ellipsis | text-ellipsis | -| decoration-slice | box-decoration-slice | -| decoration-clone | box-decoration-clone | - -## Spacing - -Use `gap` utilities instead of margins for spacing between siblings: - - -
-
Item 1
-
Item 2
-
- - -## Dark Mode - -If existing pages and components support dark mode, new pages and components must support it the same way, typically using the `dark:` variant: - - -
- Content adapts to color scheme -
- - -## Common Patterns - -### Flexbox Layout - - -
-
Left content
-
Right content
-
- - -### Grid Layout - - -
-
Card 1
-
Card 2
-
Card 3
-
- - -## Common Pitfalls - -- Using deprecated v3 utilities (bg-opacity-*, flex-shrink-*, etc.) -- Using `@tailwind` directives instead of `@import "tailwindcss"` -- Trying to use `tailwind.config.js` instead of CSS `@theme` directive -- Using margins for spacing between siblings instead of gap utilities -- Forgetting to add dark mode variants when the project uses dark mode \ No newline at end of file diff --git a/.junie/skills/wayfinder-development/SKILL.md b/.junie/skills/wayfinder-development/SKILL.md deleted file mode 100644 index d8d586e..0000000 --- a/.junie/skills/wayfinder-development/SKILL.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -name: wayfinder-development -description: >- - Activates whenever referencing backend routes in frontend components. Use when - importing from @/actions or @/routes, calling Laravel routes from TypeScript, - or working with Wayfinder route functions. ---- - -# Wayfinder Development - -## When to Apply - -Activate whenever referencing backend routes in frontend components: -- Importing from `@/actions/` or `@/routes/` -- Calling Laravel routes from TypeScript/JavaScript -- Creating links or navigation to backend endpoints - -## Documentation - -Use `search-docs` for detailed Wayfinder patterns and documentation. - -## Quick Reference - -### Generate Routes - -Run after route changes if Vite plugin isn't installed: - -php artisan wayfinder:generate --no-interaction - -For form helpers, use `--with-form` flag: - -php artisan wayfinder:generate --with-form --no-interaction - -### Import Patterns - - - -// Named imports for tree-shaking (preferred)... -import { show, store, update } from '@/actions/App/Http/Controllers/PostController' - -// Named route imports... -import { show as postShow } from '@/routes/post' - - - -### Common Methods - - - -// Get route object... -show(1) // { url: "/posts/1", method: "get" } - -// Get URL string... -show.url(1) // "/posts/1" - -// Specific HTTP methods... -show.get(1) -store.post() -update.patch(1) -destroy.delete(1) - -// Form attributes for HTML forms... -store.form() // { action: "/posts", method: "post" } - -// Query parameters... -show(1, { query: { page: 1 } }) // "/posts/1?page=1" - - - -## Wayfinder + Inertia - -Use Wayfinder with the `` component: - - - - -
- -## Verification - -1. Run `php artisan wayfinder:generate` to regenerate routes if Vite plugin isn't installed -2. Check TypeScript imports resolve correctly -3. Verify route URLs match expected paths - -## Common Pitfalls - -- Using default imports instead of named imports (breaks tree-shaking) -- Forgetting to regenerate after route changes -- Not using type-safe parameter objects for route model binding \ No newline at end of file diff --git a/CLAUDE.md b/CLAUDE.md deleted file mode 100644 index 41be2fb..0000000 --- a/CLAUDE.md +++ /dev/null @@ -1,308 +0,0 @@ -# Configuration Claude Code - Projet Roxane - -Lire et appliquer avant toute action : - -- [.ai-rules.md](.ai-rules.md) : regles de developpement, stack, architecture, style de code, comportement attendu - -Lire avant chaque session de code et mettre à jour après ajout ou modification de fonctionnalités : -- [PROJECT_STRUCTURE.md](PROJECT_STRUCTURE.md) - -## Rappels critiques - -- Backend : Laravel 12 + Filament v4 | Frontend : React + Tailwind -- Architecture : Services (pas de Repository pattern), Controllers fins -- Toujours proposer un plan avant de coder -- Ne jamais modifier de code sans validation explicite -- Chaque feature doit inclure ses tests -- Pas d'emoji, pas de commentaires inutiles, code simple - -=== - - -=== foundation rules === - -# Laravel Boost Guidelines - -The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to ensure the best experience when building Laravel applications. - -## Foundational Context - -This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions. - -- php - 8.3.28 -- filament/filament (FILAMENT) - v4 -- inertiajs/inertia-laravel (INERTIA) - v2 -- laravel/fortify (FORTIFY) - v1 -- laravel/framework (LARAVEL) - v12 -- laravel/prompts (PROMPTS) - v0 -- laravel/wayfinder (WAYFINDER) - v0 -- livewire/livewire (LIVEWIRE) - v3 -- laravel/mcp (MCP) - v0 -- laravel/pint (PINT) - v1 -- laravel/sail (SAIL) - v1 -- phpunit/phpunit (PHPUNIT) - v11 -- @inertiajs/react (INERTIA) - v2 -- react (REACT) - v19 -- tailwindcss (TAILWINDCSS) - v4 -- @laravel/vite-plugin-wayfinder (WAYFINDER) - v0 -- eslint (ESLINT) - v9 -- prettier (PRETTIER) - v3 - -## Skills Activation - -This project has domain-specific skills available. You MUST activate the relevant skill whenever you work in that domain—don't wait until you're stuck. - -- `wayfinder-development` — Activates whenever referencing backend routes in frontend components. Use when importing from @/actions or @/routes, calling Laravel routes from TypeScript, or working with Wayfinder route functions. -- `inertia-react-development` — Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation. -- `tailwindcss-development` — Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes. - -## Conventions - -- You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, and naming. -- Use descriptive names for variables and methods. For example, `isRegisteredForDiscounts`, not `discount()`. -- Check for existing components to reuse before writing a new one. - -## Verification Scripts - -- Do not create verification scripts or tinker when tests cover that functionality and prove they work. Unit and feature tests are more important. - -## Application Structure & Architecture - -- Stick to existing directory structure; don't create new base folders without approval. -- Do not change the application's dependencies without approval. - -## Frontend Bundling - -- If the user doesn't see a frontend change reflected in the UI, it could mean they need to run `npm run build`, `npm run dev`, or `composer run dev`. Ask them. - -## Documentation Files - -- You must only create documentation files if explicitly requested by the user. - -## Replies - -- Be concise in your explanations - focus on what's important rather than explaining obvious details. - -=== boost rules === - -# Laravel Boost - -- Laravel Boost is an MCP server that comes with powerful tools designed specifically for this application. Use them. - -## Artisan - -- Use the `list-artisan-commands` tool when you need to call an Artisan command to double-check the available parameters. - -## URLs - -- Whenever you share a project URL with the user, you should use the `get-absolute-url` tool to ensure you're using the correct scheme, domain/IP, and port. - -## Tinker / Debugging - -- You should use the `tinker` tool when you need to execute PHP to debug code or query Eloquent models directly. -- Use the `database-query` tool when you only need to read from the database. - -## Reading Browser Logs With the `browser-logs` Tool - -- You can read browser logs, errors, and exceptions using the `browser-logs` tool from Boost. -- Only recent browser logs will be useful - ignore old logs. - -## Searching Documentation (Critically Important) - -- Boost comes with a powerful `search-docs` tool you should use before trying other approaches when working with Laravel or Laravel ecosystem packages. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation for the user's circumstance. You should pass an array of packages to filter on if you know you need docs for particular packages. -- Search the documentation before making code changes to ensure we are taking the correct approach. -- Use multiple, broad, simple, topic-based queries at once. For example: `['rate limiting', 'routing rate limiting', 'routing']`. The most relevant results will be returned first. -- Do not add package names to queries; package information is already shared. For example, use `test resource table`, not `filament 4 test resource table`. - -### Available Search Syntax - -1. Simple Word Searches with auto-stemming - query=authentication - finds 'authenticate' and 'auth'. -2. Multiple Words (AND Logic) - query=rate limit - finds knowledge containing both "rate" AND "limit". -3. Quoted Phrases (Exact Position) - query="infinite scroll" - words must be adjacent and in that order. -4. Mixed Queries - query=middleware "rate limit" - "middleware" AND exact phrase "rate limit". -5. Multiple Queries - queries=["authentication", "middleware"] - ANY of these terms. - -=== php rules === - -# PHP - -- Always use curly braces for control structures, even for single-line bodies. - -## Constructors - -- Use PHP 8 constructor property promotion in `__construct()`. - - public function __construct(public GitHub $github) { } -- Do not allow empty `__construct()` methods with zero parameters unless the constructor is private. - -## Type Declarations - -- Always use explicit return type declarations for methods and functions. -- Use appropriate PHP type hints for method parameters. - - -protected function isAccessible(User $user, ?string $path = null): bool -{ - ... -} - - -## Enums - -- Typically, keys in an Enum should be TitleCase. For example: `FavoritePerson`, `BestLake`, `Monthly`. - -## Comments - -- Prefer PHPDoc blocks over inline comments. Never use comments within the code itself unless the logic is exceptionally complex. - -## PHPDoc Blocks - -- Add useful array shape type definitions when appropriate. - -=== inertia-laravel/core rules === - -# Inertia - -- Inertia creates fully client-side rendered SPAs without modern SPA complexity, leveraging existing server-side patterns. -- Components live in `resources/js/pages` (unless specified in `vite.config.js`). Use `Inertia::render()` for server-side routing instead of Blade views. -- ALWAYS use `search-docs` tool for version-specific Inertia documentation and updated code examples. -- IMPORTANT: Activate `inertia-react-development` when working with Inertia client-side patterns. - -=== inertia-laravel/v2 rules === - -# Inertia v2 - -- Use all Inertia features from v1 and v2. Check the documentation before making changes to ensure the correct approach. -- New features: deferred props, infinite scrolling (merging props + `WhenVisible`), lazy loading on scroll, polling, prefetching. -- When using deferred props, add an empty state with a pulsing or animated skeleton. - -=== laravel/core rules === - -# Do Things the Laravel Way - -- Use `php artisan make:` commands to create new files (i.e. migrations, controllers, models, etc.). You can list available Artisan commands using the `list-artisan-commands` tool. -- If you're creating a generic PHP class, use `php artisan make:class`. -- Pass `--no-interaction` to all Artisan commands to ensure they work without user input. You should also pass the correct `--options` to ensure correct behavior. - -## Database - -- Always use proper Eloquent relationship methods with return type hints. Prefer relationship methods over raw queries or manual joins. -- Use Eloquent models and relationships before suggesting raw database queries. -- Avoid `DB::`; prefer `Model::query()`. Generate code that leverages Laravel's ORM capabilities rather than bypassing them. -- Generate code that prevents N+1 query problems by using eager loading. -- Use Laravel's query builder for very complex database operations. - -### Model Creation - -- When creating new models, create useful factories and seeders for them too. Ask the user if they need any other things, using `list-artisan-commands` to check the available options to `php artisan make:model`. - -### APIs & Eloquent Resources - -- For APIs, default to using Eloquent API Resources and API versioning unless existing API routes do not, then you should follow existing application convention. - -## Controllers & Validation - -- Always create Form Request classes for validation rather than inline validation in controllers. Include both validation rules and custom error messages. -- Check sibling Form Requests to see if the application uses array or string based validation rules. - -## Authentication & Authorization - -- Use Laravel's built-in authentication and authorization features (gates, policies, Sanctum, etc.). - -## URL Generation - -- When generating links to other pages, prefer named routes and the `route()` function. - -## Queues - -- Use queued jobs for time-consuming operations with the `ShouldQueue` interface. - -## Configuration - -- Use environment variables only in configuration files - never use the `env()` function directly outside of config files. Always use `config('app.name')`, not `env('APP_NAME')`. - -## Testing - -- When creating models for tests, use the factories for the models. Check if the factory has custom states that can be used before manually setting up the model. -- Faker: Use methods such as `$this->faker->word()` or `fake()->randomDigit()`. Follow existing conventions whether to use `$this->faker` or `fake()`. -- When creating tests, make use of `php artisan make:test [options] {name}` to create a feature test, and pass `--unit` to create a unit test. Most tests should be feature tests. - -## Vite Error - -- If you receive an "Illuminate\Foundation\ViteException: Unable to locate file in Vite manifest" error, you can run `npm run build` or ask the user to run `npm run dev` or `composer run dev`. - -=== laravel/v12 rules === - -# Laravel 12 - -- CRITICAL: ALWAYS use `search-docs` tool for version-specific Laravel documentation and updated code examples. -- Since Laravel 11, Laravel has a new streamlined file structure which this project uses. - -## Laravel 12 Structure - -- In Laravel 12, middleware are no longer registered in `app/Http/Kernel.php`. -- Middleware are configured declaratively in `bootstrap/app.php` using `Application::configure()->withMiddleware()`. -- `bootstrap/app.php` is the file to register middleware, exceptions, and routing files. -- `bootstrap/providers.php` contains application specific service providers. -- The `app\Console\Kernel.php` file no longer exists; use `bootstrap/app.php` or `routes/console.php` for console configuration. -- Console commands in `app/Console/Commands/` are automatically available and do not require manual registration. - -## Database - -- When modifying a column, the migration must include all of the attributes that were previously defined on the column. Otherwise, they will be dropped and lost. -- Laravel 12 allows limiting eagerly loaded records natively, without external packages: `$query->latest()->limit(10);`. - -### Models - -- Casts can and likely should be set in a `casts()` method on a model rather than the `$casts` property. Follow existing conventions from other models. - -=== wayfinder/core rules === - -# Laravel Wayfinder - -Wayfinder generates TypeScript functions for Laravel routes. Import from `@/actions/` (controllers) or `@/routes/` (named routes). - -- IMPORTANT: Activate `wayfinder-development` skill whenever referencing backend routes in frontend components. -- Invokable Controllers: `import StorePost from '@/actions/.../StorePostController'; StorePost()`. -- Parameter Binding: Detects route keys (`{post:slug}`) — `show({ slug: "my-post" })`. -- Query Merging: `show(1, { mergeQuery: { page: 2, sort: null } })` merges with current URL, `null` removes params. -- Inertia: Use `.form()` with `
` component or `form.submit(store())` with useForm. - -=== pint/core rules === - -# Laravel Pint Code Formatter - -- You must run `vendor/bin/pint --dirty --format agent` before finalizing changes to ensure your code matches the project's expected style. -- Do not run `vendor/bin/pint --test --format agent`, simply run `vendor/bin/pint --format agent` to fix any formatting issues. - -=== phpunit/core rules === - -# PHPUnit - -- This application uses PHPUnit for testing. All tests must be written as PHPUnit classes. Use `php artisan make:test --phpunit {name}` to create a new test. -- If you see a test using "Pest", convert it to PHPUnit. -- Every time a test has been updated, run that singular test. -- When the tests relating to your feature are passing, ask the user if they would like to also run the entire test suite to make sure everything is still passing. -- Tests should cover all happy paths, failure paths, and edge cases. -- You must not remove any tests or test files from the tests directory without approval. These are not temporary or helper files; these are core to the application. - -## Running Tests - -- Run the minimal number of tests, using an appropriate filter, before finalizing. -- To run all tests: `php artisan test --compact`. -- To run all tests in a file: `php artisan test --compact tests/Feature/ExampleTest.php`. -- To filter on a particular test name: `php artisan test --compact --filter=testName` (recommended after making a change to a related file). - -=== inertia-react/core rules === - -# Inertia + React - -- IMPORTANT: Activate `inertia-react-development` when working with Inertia React client-side patterns. - -=== tailwindcss/core rules === - -# Tailwind CSS - -- Always use existing Tailwind conventions; check project patterns before adding new ones. -- IMPORTANT: Always use `search-docs` tool for version-specific Tailwind CSS documentation and updated code examples. Never rely on training data. -- IMPORTANT: Activate `tailwindcss-development` every time you're working with a Tailwind CSS or styling-related task. - diff --git a/database-schema.md b/database-schema.md deleted file mode 100644 index 03ff950..0000000 --- a/database-schema.md +++ /dev/null @@ -1,344 +0,0 @@ -# Schema de Base de Donnees - Roxane - -## Diagramme des relations - -```mermaid -erDiagram - users ||--o{ members : "a des membres" - users ||--o{ memberships : "cree (admin)" - users ||--o{ sessions : "a des sessions" - - members }o--o| users : "lie a" - members }o--o| member_groups : "dans le groupe" - members ||--o{ memberships : "a des adhesions" - members ||--o{ ispconfigs_members : "comptes ISPConfig" - members ||--o{ nextclouds_members : "comptes Nextcloud" - - memberships }o--|| members : "pour le membre" - memberships }o--|| packages : "formule choisie" - memberships }o--o| users : "cree par (admin)" - memberships ||--o{ services_memberships : "services inclus" - - services ||--o{ services_memberships : "utilise dans" - - member_groups ||--o{ members : "contient" - packages ||--o{ memberships : "souscrite via" - - roles ||--o{ role_has_permissions : "a des permissions" - permissions ||--o{ role_has_permissions : "attribuee a" - roles ||--o{ model_has_roles : "attribue a" - permissions ||--o{ model_has_permissions : "attribuee a" - - users { - bigint id PK - string name "NOT NULL" - string email UK "NOT NULL" - timestamp email_verified_at "nullable" - string password "NOT NULL" - text two_factor_secret "nullable (Fortify)" - text two_factor_recovery_codes "nullable (Fortify)" - timestamp two_factor_confirmed_at "nullable (Fortify)" - string remember_token "nullable" - timestamp created_at - timestamp updated_at - } - - password_reset_tokens { - string email PK - string token "NOT NULL" - timestamp created_at "nullable" - } - - sessions { - string id PK - bigint user_id FK "nullable, indexed" - string ip_address "nullable, max 45" - text user_agent "nullable" - longtext payload "NOT NULL" - integer last_activity "indexed" - } - - contacts { - bigint id PK - string lastname "nullable" - string firstname "nullable" - string email "nullable" - string address "nullable" - string subject "nullable" - text message "nullable" - timestamp created_at - timestamp updated_at - } - - member_groups { - bigint id PK - string identifier UK "NOT NULL" - string name "NOT NULL" - string description "nullable" - timestamp created_at - timestamp updated_at - timestamp deleted_at "soft delete" - } - - member_types { - bigint id PK - string identifier UK "NOT NULL" - string name "NOT NULL" - string description "nullable" - timestamp created_at - timestamp updated_at - timestamp deleted_at "soft delete" - } - - packages { - bigint id PK - string identifier UK "NOT NULL" - string name "NOT NULL" - string description "nullable" - decimal price "precision 10, default 0" - boolean is_active "default true" - timestamp created_at - timestamp updated_at - timestamp deleted_at "soft delete" - } - - services { - bigint id PK - string identifier UK "NOT NULL" - string name "NOT NULL" - string description "nullable" - string url "NOT NULL" - string icon "nullable" - timestamp created_at - timestamp updated_at - timestamp deleted_at "soft delete" - } - - members { - bigint id PK - bigint user_id FK "nullable, ON DELETE SET NULL" - string dolibarr_id "nullable" - string keycloak_id "nullable" - enum status "draft|valid|pending|cancelled|excluded, default draft" - enum nature "physical|legal, default physical" - bigint type_id "nullable" - bigint group_id "nullable" - string lastname "nullable" - string firstname "nullable" - string email "NOT NULL" - string retzien_email "nullable" - string company "nullable" - date date_of_birth "nullable" - string address "nullable" - string zipcode "nullable" - string city "nullable" - string country "nullable" - string phone1 "nullable" - string phone2 "nullable" - boolean public_membership "default false" - string website_url "nullable" - timestamp created_at - timestamp updated_at - timestamp deleted_at "soft delete" - } - - memberships { - bigint id PK - bigint member_id FK "NOT NULL, ON DELETE CASCADE" - bigint admin_id FK "nullable, ON DELETE SET NULL" - bigint package_id FK "NOT NULL, ON DELETE CASCADE" - date start_date "nullable" - date end_date "nullable" - enum status "active|expired|pending, default pending" - date validation_date "nullable" - string payment_method "nullable" - decimal amount "precision 10-2, default 0" - enum payment_status "paid|unpaid|partial, default unpaid" - longtext note_public "nullable" - longtext note_private "nullable" - string dolibarr_id "nullable" - string dolibarr_user_id "nullable" - timestamp created_at - timestamp updated_at - timestamp deleted_at "soft delete" - } - - services_memberships { - bigint id PK - bigint service_id FK "NOT NULL, ON DELETE CASCADE" - bigint membership_id FK "NOT NULL, ON DELETE CASCADE" - timestamp created_at - timestamp updated_at - } - - ispconfigs_members { - bigint id PK - bigint member_id FK "NOT NULL, ON DELETE NO ACTION" - string ispconfig_client_id "nullable" - string ispconfig_service_user_id "nullable" - string email "nullable" - enum type "mail|web|other, NOT NULL" - json data "nullable" - timestamp created_at - timestamp updated_at - } - - nextclouds_members { - bigint id PK - bigint member_id FK "NOT NULL, ON DELETE NO ACTION" - string nextcloud_user_id "nullable" - json data "nullable" - timestamp created_at - timestamp updated_at - } - - webdomains_members { - bigint id PK - timestamp created_at - timestamp updated_at - } - - permissions { - bigint id PK - string name "NOT NULL" - string guard_name "NOT NULL" - timestamp created_at - timestamp updated_at - } - - roles { - bigint id PK - string name "NOT NULL" - string guard_name "NOT NULL" - timestamp created_at - timestamp updated_at - } - - model_has_permissions { - bigint permission_id FK "NOT NULL" - string model_type "NOT NULL" - bigint model_id "NOT NULL" - } - - model_has_roles { - bigint role_id FK "NOT NULL" - string model_type "NOT NULL" - bigint model_id "NOT NULL" - } - - role_has_permissions { - bigint permission_id FK "NOT NULL" - bigint role_id FK "NOT NULL" - } - - cache { - string key PK - mediumtext value "NOT NULL" - integer expiration "NOT NULL" - } - - cache_locks { - string key PK - string owner "NOT NULL" - integer expiration "NOT NULL" - } - - jobs { - bigint id PK - string queue "indexed" - longtext payload "NOT NULL" - tinyint attempts "NOT NULL" - integer reserved_at "nullable" - integer available_at "NOT NULL" - integer created_at "NOT NULL" - } - - job_batches { - string id PK - string name "NOT NULL" - integer total_jobs "NOT NULL" - integer pending_jobs "NOT NULL" - integer failed_jobs "NOT NULL" - longtext failed_job_ids "NOT NULL" - mediumtext options "nullable" - integer cancelled_at "nullable" - integer created_at "NOT NULL" - integer finished_at "nullable" - } - - failed_jobs { - bigint id PK - string uuid UK "NOT NULL" - text connection "NOT NULL" - text queue "NOT NULL" - longtext payload "NOT NULL" - longtext exception "NOT NULL" - timestamp failed_at "default CURRENT_TIMESTAMP" - } -``` - -## Detail des tables - -### Tables metier - -| Table | Description | Soft Delete | FK | -|-------|-------------|:-----------:|-----| -| `members` | Adherents de l'association | oui | `user_id` → users, `group_id` → member_groups | -| `memberships` | Cotisations / periodes d'adhesion | oui | `member_id` → members, `admin_id` → users, `package_id` → packages | -| `services_memberships` | Pivot services <-> cotisations | non | `service_id` → services, `membership_id` → memberships | -| `packages` | Formules d'adhesion (custom, 1 an, 2 ans) | oui | - | -| `services` | Services numeriques (mail, nextcloud, etc.) | oui | - | -| `member_groups` | Groupes de membres (admin, website) | oui | - | -| `member_types` | Types de membres | oui | - | -| `contacts` | Soumissions du formulaire de contact | non | - | - -### Tables d'integration externe - -| Table | Service externe | Description | -|-------|----------------|-------------| -| `ispconfigs_members` | ISPConfig | Lie un membre a ses comptes mail/web ISPConfig | -| `nextclouds_members` | Nextcloud | Lie un membre a son compte Nextcloud | -| `webdomains_members` | ISPConfig Web | Table preparee (vide) | - -### Tables systeme - -| Table | Origine | Description | -|-------|---------|-------------| -| `users` | Laravel + Fortify | Comptes utilisateurs avec 2FA | -| `password_reset_tokens` | Laravel | Tokens de reinitialisation de mot de passe | -| `sessions` | Laravel | Sessions utilisateur | -| `cache` / `cache_locks` | Laravel | Cache applicatif | -| `jobs` / `job_batches` / `failed_jobs` | Laravel | File d'attente de jobs | -| `permissions` | Spatie | Permissions individuelles | -| `roles` | Spatie | Roles (super_admin, panel_user) | -| `model_has_permissions` | Spatie | Pivot polymorphe modele <-> permissions | -| `model_has_roles` | Spatie | Pivot polymorphe modele <-> roles | -| `role_has_permissions` | Spatie | Pivot roles <-> permissions | - -### Enums en base - -| Table | Colonne | Valeurs | -|-------|---------|---------| -| `members` | `status` | `draft`, `valid`, `pending`, `cancelled`, `excluded` | -| `members` | `nature` | `physical`, `legal` | -| `memberships` | `status` | `active`, `expired`, `pending` | -| `memberships` | `payment_status` | `paid`, `unpaid`, `partial` | -| `ispconfigs_members` | `type` | `mail`, `web`, `other` | - -### Cles etrangeres - -| Table source | Colonne | Table cible | ON DELETE | -|-------------|---------|-------------|-----------| -| `members` | `user_id` | `users` | SET NULL | -| `memberships` | `member_id` | `members` | CASCADE | -| `memberships` | `admin_id` | `users` | SET NULL | -| `memberships` | `package_id` | `packages` | CASCADE | -| `services_memberships` | `service_id` | `services` | CASCADE | -| `services_memberships` | `membership_id` | `memberships` | CASCADE | -| `ispconfigs_members` | `member_id` | `members` | NO ACTION | -| `nextclouds_members` | `member_id` | `members` | NO ACTION | -| `sessions` | `user_id` | `users` | - | -| `model_has_permissions` | `permission_id` | `permissions` | CASCADE | -| `model_has_roles` | `role_id` | `roles` | CASCADE | -| `role_has_permissions` | `permission_id` | `permissions` | CASCADE | -| `role_has_permissions` | `role_id` | `roles` | CASCADE | \ No newline at end of file