diff --git a/.agents/skills/react-admin/SKILL.md b/.agents/skills/react-admin/SKILL.md
new file mode 100644
index 00000000000..bb76b33d9c5
--- /dev/null
+++ b/.agents/skills/react-admin/SKILL.md
@@ -0,0 +1,227 @@
+---
+name: react-admin
+description: This skill should be used when building, modifying, or debugging a react-admin application — including creating resources, lists, forms, data fetching, authentication, relationships between entities, custom pages, or any CRUD admin interface built with react-admin.
+---
+
+# React-Admin Development Guide
+
+React-admin is a framework for building single-page applications on top of REST/GraphQL APIs. It builds on top of React Query, react-hook-form, react-router, and Material UI. It provides 150+ components and dozens of hooks. Before writing custom code, always check if react-admin already provides a component or hook for the task. Full documentation: https://marmelab.com/react-admin/doc/
+
+## Providers (Backend Abstraction)
+
+React-admin never calls APIs directly. All communication goes through **providers** — adapters that translate react-admin's standardized calls into API-specific requests. The three main providers are:
+
+- **dataProvider**: All CRUD operations (`getList`, `getOne`, `create`, `update`, `delete`, `getMany`, `getManyReference`, `updateMany`, `deleteMany`). See [DataProviders](https://marmelab.com/react-admin/DataProviders.html) and [50+ existing adapters](https://marmelab.com/react-admin/DataProviderList.html).
+- **authProvider**: Authentication and authorization. See [Authentication](https://marmelab.com/react-admin/Authentication.html).
+- **i18nProvider**: Translations (`translate`, `changeLocale`, `getLocale`).
+
+**Critical rule**: Never use `fetch`, `axios`, or direct HTTP calls in components. Always use data provider hooks. This ensures proper caching, loading states, error handling, authentication, and optimistic rendering.
+
+## Composition (Not God Components)
+
+React-admin uses composition over configuration. Override behavior by passing child components, not by setting dozens of props:
+
+```jsx
+}>
+
+
+
+
+```
+
+To customize the layout, pass a custom layout component to ``. To customize the menu, pass it to ``. This chaining is by design — see [Architecture](https://marmelab.com/react-admin/Architecture.html).
+
+## Context: Pull, Don't Push
+
+React-admin components expose data to descendants via React contexts. Access data using hooks rather than passing props down:
+
+- `useRecordContext()` — current record in Show/Edit/Create views. See [useRecordContext](https://marmelab.com/react-admin/useRecordContext.html).
+- `useListContext()` — list data, filters, pagination, sort in List views. See [useListContext](https://marmelab.com/react-admin/useListContext.html).
+- `useShowContext()`, `useEditContext()`, `useCreateContext()` — page-level state for detail views.
+- `useTranslate()` — translation function from i18nProvider.
+- `useGetIdentity()` — current user from authProvider.
+
+## Hooks Over Custom Components
+
+When a react-admin component's UI doesn't fit, use the underlying hook instead of building from scratch. Controller hooks (named `use*Controller`) provide all the logic without the UI:
+
+- `useListController()` — list fetching, filtering, pagination logic
+- `useEditController()` — edit form fetching and submission logic
+- `useShowController()` — show page data fetching logic
+
+## Routing
+
+`` declares CRUD routes automatically (`/posts`, `/posts/create`, `/posts/:id/edit`, `/posts/:id/show`). Use `` for non-CRUD pages. Use `useCreatePath()` to build resource URLs and `` from react-admin for navigation. Default router is react-router (HashRouter), but TanStack Router is also supported via `routerProvider`. See [Routing](https://marmelab.com/react-admin/Routing.html).
+
+## Data Fetching
+
+### Query Hooks (Reading Data)
+
+```jsx
+const { data, total, isPending, error } = useGetList('posts', {
+ pagination: { page: 1, perPage: 25 },
+ sort: { field: 'created_at', order: 'DESC' },
+ filter: { status: 'published' },
+});
+
+const { data: record, isPending } = useGetOne('posts', { id: 123 });
+const { data: records } = useGetMany('posts', { ids: [1, 2, 3] });
+const { data, total } = useGetManyReference('comments', {
+ target: 'post_id', id: 123,
+ pagination: { page: 1, perPage: 25 },
+});
+```
+
+See [useGetList](https://marmelab.com/react-admin/useGetList.html), [useGetOne](https://marmelab.com/react-admin/useGetOne.html).
+
+### Mutation Hooks (Writing Data)
+
+All mutations return `[mutate, state]`. They support three **mutation modes**:
+
+- **pessimistic** (default): Wait for server response, then update UI.
+- **optimistic**: Update UI immediately, revert on server error.
+- **undoable**: Update UI, show undo notification, commit after delay.
+
+```jsx
+const [create, { isPending }] = useCreate();
+const [update] = useUpdate();
+const [deleteOne] = useDelete();
+
+// Call with resource and params
+create('posts', { data: { title: 'Hello' } });
+update('posts', { id: 1, data: { title: 'Updated' }, previousData: record });
+deleteOne('posts', { id: 1, previousData: record });
+```
+
+Pass `mutationMode: 'optimistic'` or `'undoable'` for instant UI feedback. See [useCreate](https://marmelab.com/react-admin/useCreate.html), [useUpdate](https://marmelab.com/react-admin/useUpdate.html).
+
+## Authentication & Authorization
+
+```typescript
+const authProvider = {
+ login: ({ username, password }) => Promise,
+ logout: () => Promise,
+ checkAuth: () => Promise, // Verify credentials are valid
+ checkError: (error) => Promise, // Detect auth errors from API responses
+ getIdentity: () => Promise<{ id, fullName, avatar }>,
+ getPermissions: () => Promise,
+ canAccess: ({ resource, action, record }) => Promise, // RBAC
+};
+```
+
+Each auth provider method has a corresponding hook (e.g. `useGetIdentity()`, `useCanAccess()`).
+
+- **Custom routes are public by default.** Wrap them with `` or call `useAuthenticated()` to require login. See [Authenticated](https://marmelab.com/react-admin/Authenticated.html).
+- Centralize authorization in `authProvider.canAccess()`, not in individual components. Use `useCanAccess()` to check permissions. See [useCanAccess](https://marmelab.com/react-admin/useCanAccess.html) and [AuthRBAC](https://marmelab.com/react-admin/AuthRBAC.html).
+- The dataProvider must include credentials (Bearer token, cookies) in requests — authProvider handles login, but dataProvider handles API calls. Configure `httpClient` in data provider setup.
+
+## Relationships Between Entities
+
+Fetching all the data (including relationships) upfront for a given page is an anti-pattern. Instead, fetch related records on demand using reference fields and inputs.
+
+### Displaying Related Records (Fields)
+
+```jsx
+{/* Show a the company of the current record based on its company_id */}
+
+
+{/* Show a list of related records (reverse FK) */}
+
+
+
+
+
+
+
+{/* Show multiple referenced records (array of IDs) */}
+
+
+
+
+
+```
+
+See [ReferenceField](https://marmelab.com/react-admin/ReferenceField.html), [ReferenceManyField](https://marmelab.com/react-admin/ReferenceManyField.html), [ReferenceArrayField](https://marmelab.com/react-admin/ReferenceArrayField.html).
+
+### Editing Related Records (Inputs)
+
+```jsx
+{/* Select from another resource (FK) */}
+
+
+{/* Multi-select from another resource (array of IDs) */}
+
+```
+
+See [ReferenceInput](https://marmelab.com/react-admin/ReferenceInput.html), [ReferenceArrayInput](https://marmelab.com/react-admin/ReferenceArrayInput.html).
+
+## Forms
+
+React-admin forms are built on react-hook-form. Use `` for single-column layouts and `` for multi-tab layouts. See [SimpleForm](https://marmelab.com/react-admin/SimpleForm.html), [TabbedForm](https://marmelab.com/react-admin/TabbedForm.html).
+
+Pass validators to input components: `required()`, `minLength(min)`, `maxLength(max)`, `minValue(min)`, `maxValue(max)`, `number()`, `email()`, `regex(pattern, message)`, or a custom function returning an error string.
+
+```jsx
+
+```
+
+Use RHF's `useWatch()` to create dynamic forms that react to field values:
+
+## Resource Definition
+
+Encapsulate resource components in index files for clean imports:
+
+```jsx
+// posts/index.ts
+export default {
+ list: PostList,
+ create: PostCreate,
+ edit: PostEdit,
+ icon: PostIcon,
+ recordRepresentation: (record) => record.title, // How records appear in references
+};
+```
+
+See [Resource](https://marmelab.com/react-admin/Resource.html), [RecordRepresentation](https://marmelab.com/react-admin/RecordRepresentation.html).
+
+## Custom Data Provider Methods
+
+Extend the dataProvider with domain-specific methods:
+
+```jsx
+const dataProvider = {
+ ...baseDataProvider,
+ archivePost: async (id) => { /* custom logic */ },
+};
+// Call via useDataProvider and useQuery:
+// const dp = useDataProvider();
+// const { data } = useQuery(['archivePost', id], () => dp.archivePost(id));
+```
+
+## Persistent Client State (Store)
+
+Use `useStore()` for persistent user preferences (theme, column visibility, saved filters):
+
+```jsx
+const [theme, setTheme] = useStore('theme', 'light');
+```
+
+See [Store](https://marmelab.com/react-admin/Store.html).
+
+## Notification, Redirect, Refresh
+
+```jsx
+const notify = useNotify();
+const redirect = useRedirect();
+const refresh = useRefresh();
+
+notify('Record saved', { type: 'success' });
+redirect('list', 'posts'); // Navigate to /posts
+redirect('edit', 'posts', 123); // Navigate to /posts/123
+refresh(); // Invalidate all queries
+```
+
+## Deprecations
+
+- Use DataTable instead of Datagrid
+- Prefer `` and `useCanAccess` for authorization checks
\ No newline at end of file
diff --git a/docs/CodingAgents.md b/docs/CodingAgents.md
new file mode 100644
index 00000000000..53a537ce184
--- /dev/null
+++ b/docs/CodingAgents.md
@@ -0,0 +1,41 @@
+---
+layout: default
+title: "Using Coding Agents"
+---
+
+# Using Coding Agents
+
+AI coding assistants like Claude Code, GitHub Copilot, Cursor, Gemini CLI or Codex already know react-admin—they’ve been trained on it. But if you want high‑quality react-admin code (idiomatic, maintainable, and aligned with best practices), you need to guide them.
+
+This page explains how to make your coding agent significantly better at writing react-admin applications.
+
+## React-Admin Documentation on Context7
+
+When an agent needs precise information about a hook or component API, give it direct access to the react-admin documentation via [Context7](https://github.com/upstash/context7#installation).
+
+After installing the Context7 MCP server, reference Context7 and [`/marmelab/react-admin`](https://context7.com/marmelab/react-admin) directly in your prompt. For example:
+
+```txt
+Add a form field to edit the author of the post.
+use context7 with /marmelab/react-admin
+```
+
+This ensures the agent relies on the official docs instead of guessing.
+
+## React-Admin Skill
+
+You can go one step further by adding the official react-admin [skill](https://agentskills.io/):
+
+[react-admin/SKILL.md](https://github.com/marmelab/react-admin/blob/master/.agents/skills/react-admin/SKILL.md)
+
+Follow your agent’s instructions to install the skill in your repository (for example, `.claude/skills/react-admin/SKILL.md` for Claude Code).
+
+Once installed, the agent will automatically apply react-admin best practices when generating code.
+
+For example:
+
+```
+In the company detail view, show the list of the contacts of the company.
+```
+
+With the skill enabled, the agent will correctly choose `` and `` to display the related contacts.
diff --git a/docs/navigation.html b/docs/navigation.html
index 31f9d1a4f19..49299fb5de6 100644
--- a/docs/navigation.html
+++ b/docs/navigation.html
@@ -15,8 +15,9 @@