@lminii/material-react-table-mcp 4.0.1

package/data/skills/filtering/SKILL.md

@@ -0,0 +1,213 @@
+---
+name: filtering
+description: >
+  Configure column and global filtering in Material React Table V4: filterVariant (text, select, multi-select, autocomplete, range, range-slider, checkbox, date, datetime, time and their ranges), enableFacetedValues, filterFn and filterFns, enableColumnFilterModes with columnFilterModeOptions, columnFilterDisplayMode, globalFilterFn and ranked results, filter match highlighting, and the muiFilter*Props. Load for dropdown or date filters, custom filter logic, filter mode menus, or search that matches the wrong rows.
+metadata:
+  type: framework
+  library: '@lminii/material-react-table'
+  library_version: '4.0.0'
+  framework: react
+requires:
+  - getting-started
+  - '@tanstack/table-core#column-filtering'
+  - '@tanstack/table-core#global-filtering'
+sources:
+  - 'lminii/material-react-table:apps/material-react-table-docs/pages/docs/guides/column-filtering.mdx'
+  - 'lminii/material-react-table:apps/material-react-table-docs/pages/docs/guides/global-filtering.mdx'
+  - 'lminii/material-react-table:apps/material-react-table-docs/examples/customize-filter-variants/sandbox/src/TS.tsx'
+  - 'lminii/material-react-table:packages/material-react-table/src/fns/filterFns.ts'
+  - 'lminii/material-react-table:packages/material-react-table/src/utils/column.utils.ts'
+  - 'lminii/material-react-table:packages/material-react-table/src/types.ts'
+---
+
+This skill builds on `getting-started`, `@tanstack/table-core#column-filtering`, and `@tanstack/table-core#global-filtering`. Client-side column filters and the global search are on by default. MRT adds filter inputs, filter variants, fuzzy matching, and filter mode menus on top of the TanStack filtering model; server-side filtering is covered by `state-and-server-data`.
+
+## Setup
+
+```tsx
+const columns: MRT_ColumnDef<Person>[] = [
+  { accessorKey: 'name', header: 'Name' }, // text filter, fuzzy
+  { accessorKey: 'city', header: 'City', filterVariant: 'select' },
+  { accessorKey: 'state', header: 'State', filterVariant: 'multi-select' },
+  { accessorKey: 'salary', header: 'Salary', filterVariant: 'range-slider' },
+  {
+    accessorFn: (row) => new Date(row.hireDate), // filter and sort on a Date
+    id: 'hireDate',
+    header: 'Hired',
+    filterVariant: 'date-range',
+    Cell: ({ cell }) => cell.getValue<Date>().toLocaleDateString(),
+  },
+]
+
+const table = useMaterialReactTable({
+  columns,
+  data,
+  enableFacetedValues: true, // options and min/max come from the data
+  initialState: { showColumnFilters: true },
+})
+```
+
+`enableColumnFilters` (table) and `enableColumnFilter` (column) turn column filters off; `enableGlobalFilter` does the same for search; `enableFilters: false` removes both. `showColumnFilters` and `showGlobalFilter` are state slices, so seed them in `initialState` to show the inputs immediately.
+
+## Core Patterns
+
+### Pick the variant and let it pick the filter function
+
+```tsx
+{ accessorKey: 'isActive', accessorFn: (row) => (row.isActive ? 'true' : 'false'), id: 'isActive', header: 'Active', filterVariant: 'checkbox' },
+{ accessorKey: 'age', header: 'Age', filterVariant: 'range', filterFn: 'between' },
+{ accessorKey: 'team', header: 'Team', filterVariant: 'autocomplete', filterSelectOptions: teams },
+```
+
+Variants: `text` (default), `autocomplete`, `select`, `multi-select`, `range`, `range-slider`, `checkbox`, `date`, `date-range`, `datetime`, `datetime-range`, `time`, `time-range`. The default `filterFn` follows the variant: `multi-select` uses `arrIncludesSome`, any `range` variant uses `betweenInclusive`, `select` and `checkbox` use `equals`, everything else uses `fuzzy`. `filterSelectOptions` takes strings or `{ label, value }` objects; with `enableFacetedValues` the select, multi-select, autocomplete, and range-slider inputs fill themselves from the column's unique values or min and max. The checkbox variant compares against the strings `'true'` and `'false'`, so its accessor must return strings.
+
+### Date, datetime, and time variants need the pickers provider
+
+```tsx
+import { LocalizationProvider } from '@mui/x-date-pickers/LocalizationProvider'
+import { AdapterDayjs } from '@mui/x-date-pickers/AdapterDayjs'
+
+<LocalizationProvider dateAdapter={AdapterDayjs}>
+  <MaterialReactTable table={table} />
+</LocalizationProvider>
+```
+
+MRT renders `@mui/x-date-pickers` V9 components for these variants and expects one `LocalizationProvider` above the table. The accessor should return a `Date` so comparisons and sorting work. `muiFilterDatePickerProps`, `muiFilterDateTimePickerProps`, and `muiFilterTimePickerProps` forward props to the picker; for range variants the callback form receives `rangeFilterIndex` (0 for the start input, 1 for the end).
+
+### Custom filter functions
+
+```tsx
+const table = useMaterialReactTable({
+  columns: [
+    { accessorKey: 'name', header: 'Name', filterFn: 'startsWith' }, // MRT built-in
+    { accessorKey: 'code', header: 'Code', filterFn: 'includesStringSensitive' }, // TanStack built-in
+    { accessorKey: 'tags', header: 'Tags', filterFn: 'hasAllTags' }, // registered below
+  ],
+  data,
+  filterFns: {
+    hasAllTags: (row, columnId, filterValue: string) =>
+      filterValue.split(',').every((tag) => row.getValue<string[]>(columnId).includes(tag.trim())),
+  },
+  globalFilterFn: 'contains', // default is 'fuzzy'
+})
+```
+
+MRT built-ins: `between`, `betweenInclusive`, `contains`, `empty`, `endsWith`, `equals`, `fuzzy`, `greaterThan`, `greaterThanOrEqualTo`, `lessThan`, `lessThanOrEqualTo`, `notEmpty`, `notEquals`, `startsWith`. TanStack built-ins such as `includesString`, `equalsString`, `arrIncludes`, `arrIncludesAll`, `arrIncludesSome`, `weakEquals`, and `inNumberRange` also work by name. A function passed to `filterFn` receives `(row, columnId, filterValue)` and returns a boolean; functions registered in `filterFns` become names usable in `filterFn`, `globalFilterFn`, and the filter mode menus. The `fuzzy` global filter ranks rows by match quality unless `enableGlobalFilterRankedResults` is false, a sort is active, rows are expanded, or a `manual*` option is set.
+
+### Let users switch filter modes
+
+```tsx
+const table = useMaterialReactTable({
+  columns: [
+    { accessorKey: 'name', header: 'Name', columnFilterModeOptions: ['fuzzy', 'contains', 'startsWith'] },
+    { accessorKey: 'age', header: 'Age', columnFilterModeOptions: ['between', 'lessThan', 'greaterThan'] },
+  ],
+  data,
+  enableColumnFilterModes: true,
+  enableGlobalFilterModes: true,
+  globalFilterModeOptions: ['fuzzy', 'startsWith'],
+  columnFilterDisplayMode: 'popover', // 'subheader' (default), 'popover', or 'custom'
+})
+```
+
+The chosen modes live in the `columnFilterFns` and `globalFilterFn` state slices, controllable through `onColumnFilterFnsChange` and `onGlobalFilterFnChange`. `renderColumnFilterModeMenuItems` and `renderGlobalFilterModeMenuItems` replace the menu; each receives `onSelectFilterMode(name)` and `internalFilterOptions`. `columnFilterDisplayMode: 'custom'` keeps the filtering logic while you render inputs elsewhere with `column.setFilterValue`. Filter values arrive after a short debounce (200 ms client-side, 400 ms with `manualFiltering`).
+
+### Keep match highlighting in custom cells
+
+```tsx
+{
+  accessorKey: 'name',
+  header: 'Name',
+  Cell: ({ renderedCellValue }) => <strong>{renderedCellValue}</strong>,
+}
+```
+
+Text filters and the global search highlight matches inside cells. A custom `Cell` keeps that only when it renders `renderedCellValue` instead of `cell.getValue()`. `enableFilterMatchHighlighting: false` turns it off per table or per column.
+
+## Common Mistakes
+
+### HIGH Filter variant does not match the accessor value type
+
+Wrong:
+
+```tsx
+{ accessorKey: 'hireDate', header: 'Hired', filterVariant: 'date-range' } // hireDate is an ISO string
+```
+
+Correct:
+
+```tsx
+{
+  accessorFn: (row) => new Date(row.hireDate),
+  id: 'hireDate',
+  header: 'Hired',
+  filterVariant: 'date-range',
+  Cell: ({ cell }) => cell.getValue<Date>().toLocaleDateString(),
+}
+```
+
+The `betweenInclusive` comparison the date variants use works on `Date` objects and numbers, not on date strings, so string columns silently match everything or nothing.
+
+Source: `docs/examples/customize-filter-variants`
+
+### HIGH Reading the filter value with the wrong shape
+
+Wrong:
+
+```tsx
+filterFn: (row, id, filterValue) => row.getValue<number>(id) >= filterValue, // range variant
+```
+
+Correct:
+
+```tsx
+filterFn: (row, id, [min, max]: [number, number]) => {
+  const value = row.getValue<number>(id)
+  return (min === '' || value >= min) && (max === '' || value <= max)
+}
+```
+
+Range variants store `[min, max]` and multi-select stores an array; text, select, and checkbox store a single value. Match the shape or the custom function throws or filters everything out.
+
+Source: `packages/material-react-table/src/fns/filterFns.ts`
+
+### MEDIUM Passing removed Material UI text field props to filters
+
+Wrong:
+
+```tsx
+muiFilterTextFieldProps: { InputProps: { startAdornment: <SearchIcon /> } }
+```
+
+Correct:
+
+```tsx
+muiFilterTextFieldProps: { slotProps: { input: { startAdornment: <SearchIcon /> } } }
+```
+
+Material UI V9 removed `InputProps` and `inputProps`; MRT merges `slotProps.input`, `slotProps.htmlInput`, and `slotProps.select` into its own.
+
+Source: `MIGRATION.md`
+
+### MEDIUM Mode menu offers a function that is not registered
+
+Wrong:
+
+```tsx
+columnFilterModeOptions: ['fuzzy', 'isPrime'], // isPrime only exists in the column's filterFn
+```
+
+Correct:
+
+```tsx
+filterFns: { isPrime: (row, id) => isPrime(row.getValue<number>(id)) },
+columnFilterModeOptions: ['fuzzy', 'isPrime'],
+```
+
+Filter mode names resolve through the table `filterFns` map. A name that is not there falls back to the default and the menu label shows the raw key.
+
+Source: `docs/guides/column-filtering.mdx`
+
+## API Discovery
+
+Search `node_modules/@lminii/material-react-table/dist/index.d.ts` for `filterVariant`, `MRT_FilterOption`, `filterFns`, and `muiFilter` for the exact unions and callback props. `MRT_FilterFns` is exported for reuse. The Column Filtering and Global Filtering guides at `/docs/guides/column-filtering` and `/docs/guides/global-filtering` list the related table, column, and state options, and `/docs/examples/customize-filter-variants`, `customize-filter-modes`, `enable-filter-facet-values`, and `alternate-column-filtering` are runnable examples.

package/data/skills/getting-started/SKILL.md

@@ -0,0 +1,213 @@
+---
+name: getting-started
+description: >
+  Build a Material React Table V4 with useMaterialReactTable and the MaterialReactTable table prop: install @lminii/material-react-table with Material UI V9 peers, define stable data and MRT_ColumnDef columns, toggle features with enable* options, and read the instance. Load for a first MRT table, a Material UI data grid on TanStack Table V9, or when a TanStack useTable or upstream material-react-table example is producing the wrong setup.
+metadata:
+  type: framework
+  library: '@lminii/material-react-table'
+  library_version: '4.0.0'
+  framework: react
+requires:
+  - '@tanstack/table-core#core'
+sources:
+  - 'lminii/material-react-table:apps/material-react-table-docs/pages/docs/getting-started/install.mdx'
+  - 'lminii/material-react-table:apps/material-react-table-docs/pages/docs/getting-started/usage.mdx'
+  - 'lminii/material-react-table:apps/material-react-table-docs/pages/docs/guides/best-practices.mdx'
+  - 'lminii/material-react-table:packages/material-react-table/src/hooks/useMaterialReactTable.ts'
+  - 'lminii/material-react-table:packages/material-react-table/src/types.ts'
+---
+
+This skill builds on `@tanstack/table-core#core` for the headless model and stable inputs. Material React Table (MRT) owns the TanStack Table instance, feature registration, and all Material UI rendering. Application code never calls `useTable` or `tableFeatures`; it configures MRT options and renders MRT components.
+
+## Setup
+
+```bash
+npm install @lminii/material-react-table @mui/material@^9 @mui/icons-material@^9 @mui/x-date-pickers@^9 @emotion/react @emotion/styled
+```
+
+Do not install `@tanstack/react-table`; MRT pins its own exact version. Node 22.12 or newer is required for the CommonJS build because TanStack Table V9 is ESM-only.
+
+```tsx
+import { useMemo } from 'react'
+import {
+  MaterialReactTable,
+  useMaterialReactTable,
+  type MRT_ColumnDef,
+} from '@lminii/material-react-table'
+
+type Person = { name: string; age: number }
+
+const data: Person[] = [
+  { name: 'Ada', age: 36 },
+  { name: 'Grace', age: 45 },
+]
+
+export function PeopleTable() {
+  const columns = useMemo<MRT_ColumnDef<Person>[]>(
+    () => [
+      { accessorKey: 'name', header: 'Name' },
+      { accessorKey: 'age', header: 'Age' },
+    ],
+    [],
+  )
+
+  const table = useMaterialReactTable({
+    columns,
+    data,
+    enableRowSelection: true,
+  })
+
+  return <MaterialReactTable table={table} />
+}
+```
+
+`useMaterialReactTable(options)` returns an `MRT_TableInstance<TData>`. Every MRT component takes that instance through a `table` prop; nothing is passed through React context.
+
+## Core Patterns
+
+### Accessors return primitives, renders return markup
+
+```tsx
+const columns: MRT_ColumnDef<Person>[] = [
+  {
+    accessorFn: (row) => `${row.firstName} ${row.lastName}`,
+    id: 'fullName',
+    header: 'Name',
+    Cell: ({ cell, row }) => (
+      <a href={row.original.profileUrl}>{cell.getValue<string>()}</a>
+    ),
+  },
+]
+```
+
+`accessorKey` or `accessorFn` feeds sorting, filtering, grouping, and search, so it must return a string, number, boolean, or Date. `Cell`, `Header`, `Footer`, `Edit`, `Filter`, `AggregatedCell`, and `GroupedCell` are the render slots. An `accessorFn` column needs an explicit `id`.
+
+### Infer column types with createMRTColumnHelper
+
+```tsx
+import { createMRTColumnHelper } from '@lminii/material-react-table'
+
+const helper = createMRTColumnHelper<Person>()
+const columns = [
+  helper.accessor('name', { header: 'Name' }),
+  helper.accessor((row) => row.age, {
+    id: 'age',
+    header: 'Age',
+    Cell: ({ cell }) => cell.getValue().toLocaleString(), // typed number
+  }),
+  helper.display({ id: 'actions', header: 'Actions' }),
+]
+```
+
+### Toggle features with enable* options
+
+Table-level `enable*` options switch a feature on for every column; the same option on a column definition overrides it for that column. `enableColumnFilters`, `enableSorting`, `enablePagination`, `enableGlobalFilter`, `enableColumnActions`, `enableDensityToggle`, `enableFullScreenToggle`, `enableHiding`, and `enableTopToolbar` are on by default. Row selection, editing, grouping, pinning, ordering, expanding, virtualization, and row actions are off until enabled.
+
+```tsx
+const table = useMaterialReactTable({
+  columns,
+  data,
+  enableColumnOrdering: true,
+  enableColumnPinning: true,
+  enableGrouping: true,
+  enablePagination: false,
+  renderDetailPanel: ({ row }) => <pre>{JSON.stringify(row.original)}</pre>,
+})
+```
+
+### Read the instance where you need it
+
+```tsx
+const selectedRows = table.getSelectedRowModel().rows
+const { pagination, sorting } = table.getState()
+table.resetRowSelection()
+```
+
+`table.getState()` returns the full MRT state, including MRT-only slices such as `density`, `isFullScreen`, and `showColumnFilters`. Inside render code `table.state` is the reactive equivalent.
+
+## Common Mistakes
+
+### HIGH Building the table with TanStack hooks
+
+Wrong:
+
+```tsx
+const table = useTable({ features, columns, data })
+return <MaterialReactTable table={table} />
+```
+
+Correct:
+
+```tsx
+const table = useMaterialReactTable({ columns, data })
+return <MaterialReactTable table={table} />
+```
+
+`MaterialReactTable` needs the MRT instance, which registers MRT's features, display columns, localization, icons, and Material UI props. A bare TanStack instance lacks all of them.
+
+Source: `packages/material-react-table/src/hooks/useMaterialReactTable.ts`
+
+### HIGH Unstable data or columns
+
+Wrong:
+
+```tsx
+const table = useMaterialReactTable({
+  columns: [{ accessorKey: 'name', header: 'Name' }],
+  data: response.data ?? [],
+})
+```
+
+Correct:
+
+```tsx
+const columns = useMemo<MRT_ColumnDef<Person>[]>(() => [...], [])
+const EMPTY: Person[] = []
+const table = useMaterialReactTable({ columns, data: response.data ?? EMPTY })
+```
+
+A new array each render invalidates every row model and can loop forever. Keep `columns` and `data` in `useMemo`, `useState`, module scope, or a query cache.
+
+Source: `docs/getting-started/usage.mdx`
+
+### MEDIUM Mixing the upstream and fork package names
+
+Wrong:
+
+```tsx
+import { MaterialReactTable } from 'material-react-table'
+import { MRT_Localization_DE } from '@lminii/material-react-table/locales/de'
+```
+
+Correct:
+
+```tsx
+import { MaterialReactTable } from '@lminii/material-react-table'
+import { MRT_Localization_DE } from '@lminii/material-react-table/locales/de'
+```
+
+Two copies of MRT produce two `MRT_TableInstance` types and duplicate Emotion styles. Pick the fork everywhere, or alias `material-react-table` to it in `package.json`.
+
+Source: `MIGRATION.md`
+
+### MEDIUM Returning JSX from an accessor
+
+Wrong:
+
+```tsx
+{ accessorFn: (row) => <b>{row.name}</b>, id: 'name', header: 'Name' }
+```
+
+Correct:
+
+```tsx
+{ accessorKey: 'name', header: 'Name', Cell: ({ cell }) => <b>{cell.getValue<string>()}</b> }
+```
+
+Sorting, filtering, and global search compare accessor values, so JSX breaks all three.
+
+Source: `docs/getting-started/usage.mdx`
+
+## API Discovery
+
+Read `node_modules/@lminii/material-react-table/dist/index.d.ts` for `MRT_TableOptions`, `MRT_ColumnDef`, `MRT_TableInstance`, and `MRT_TableState`; the `mui*Props`, `render*`, `enable*`, and `on*Change` option families are all declared there with JSDoc. The docs prop tables at `/docs/api/table-options`, `/docs/api/column-options`, and `/docs/api/state-options` list every option with its default and source library.

package/data/skills/localization/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: localization
+description: >
+  Translate Material React Table V4 with the localization option: import a built-in locale from @lminii/material-react-table/locales/<code>, override individual MRT_Localization strings, write a full custom locale with the language BCP 47 tag, keep {column} placeholders, and pair it with Material UI theme locales and the date pickers adapterLocale. Load for i18n, translating toolbar and menu text, number formatting in pagination, or a locale import that fails to resolve.
+metadata:
+  type: framework
+  library: '@lminii/material-react-table'
+  library_version: '4.0.0'
+  framework: react
+requires:
+  - getting-started
+sources:
+  - 'lminii/material-react-table:apps/material-react-table-docs/pages/docs/guides/localization.mdx'
+  - 'lminii/material-react-table:apps/material-react-table-docs/examples/localization-i18n-de/sandbox/src/TS.tsx'
+  - 'lminii/material-react-table:packages/material-react-table/src/locales/en.ts'
+  - 'lminii/material-react-table:packages/material-react-table/src/hooks/useMRT_TableOptions.ts'
+  - 'lminii/material-react-table:packages/material-react-table/src/types.ts'
+---
+
+This skill builds on `getting-started`. Every user-facing string MRT renders comes from one `MRT_Localization` object. The `localization` option takes a partial object that is merged over the English defaults, so a locale file or a handful of overrides both work.
+
+## Setup
+
+```tsx
+import { MRT_Localization_DE } from '@lminii/material-react-table/locales/de'
+
+const table = useMaterialReactTable({
+  columns,
+  data,
+  localization: MRT_Localization_DE,
+})
+```
+
+Built-in locales, imported from `@lminii/material-react-table/locales/<code>`: `ar`, `az`, `bg`, `cs`, `da`, `de`, `el`, `en`, `es`, `et`, `fa`, `fi`, `fr`, `he`, `hr`, `hu`, `hy`, `id`, `it`, `ja`, `ko`, `mk`, `nl`, `no`, `np`, `pl`, `pt`, `pt-BR`, `ro`, `ru`, `sk`, `sr-Cyrl-RS`, `sr-Latn-RS`, `sv`, `tr`, `uk`, `vi`, `zh-Hans`, `zh-Hant`. Each exports `MRT_Localization_<CODE>` with hyphens replaced by underscores, for example `MRT_Localization_PT_BR` and `MRT_Localization_ZH_HANS`. Column headers, cell content, and your own toolbar buttons are not translated by MRT; those come from your column definitions and render slots.
+
+## Core Patterns
+
+### Override a few strings
+
+```tsx
+const table = useMaterialReactTable({
+  columns,
+  data,
+  localization: {
+    ...MRT_Localization_DE,
+    noRecordsToDisplay: 'Keine Personen gefunden',
+    rowsPerPage: 'Personen pro Seite',
+  },
+})
+```
+
+Partial objects are merged over English, so an override object without a base locale still renders every other string. Keep the `localization` object stable (module scope or `useMemo`); MRT memoizes the merge on its identity.
+
+### Write a custom locale
+
+```tsx
+import { type MRT_Localization } from '@lminii/material-react-table'
+
+export const MRT_Localization_GA: MRT_Localization = {
+  ...MRT_Localization_EN, // start from English so nothing is missing
+  language: 'ga', // BCP 47 tag used for number formatting
+  actions: 'Gníomhartha',
+  filterByColumn: 'Scag de réir {column}',
+  sortByColumnAsc: 'Sórtáil de réir {column} in ord ardaitheach',
+  noRecordsToDisplay: 'Níl aon taifid le taispeáint',
+}
+```
+
+`MRT_Localization` has around 90 keys; `language` is required on the type and feeds `toLocaleString` for the row counts in pagination and the selection banner. Strings such as `filterByColumn`, `sortByColumnAsc`, `dropToGroupBy`, and `filteringByColumn` contain `{column}` placeholders that MRT replaces with the column header, so keep the token verbatim. Fully translated locales are welcome as pull requests to `packages/material-react-table/src/locales`.
+
+### Pair with Material UI and the date pickers
+
+```tsx
+import { createTheme, ThemeProvider, useTheme } from '@mui/material'
+import { deDE } from '@mui/material/locale'
+import { LocalizationProvider } from '@mui/x-date-pickers/LocalizationProvider'
+import { AdapterDayjs } from '@mui/x-date-pickers/AdapterDayjs'
+import { deDE as pickersDeDE } from '@mui/x-date-pickers/locales'
+import 'dayjs/locale/de'
+
+const theme = useTheme()
+
+<ThemeProvider theme={createTheme(theme, deDE, pickersDeDE)}>
+  <LocalizationProvider dateAdapter={AdapterDayjs} adapterLocale="de">
+    <MaterialReactTable table={table} />
+  </LocalizationProvider>
+</ThemeProvider>
+```
+
+MRT's `localization` covers MRT strings only. Material UI's own component text (pagination select labels, accessibility labels) comes from the theme locale, and the date and time filter pickers take their month names and formats from the pickers locale and `adapterLocale`.
+
+### Switch locales at runtime
+
+```tsx
+const locales = { en: MRT_Localization_EN, de: MRT_Localization_DE, ja: MRT_Localization_JA }
+
+const table = useMaterialReactTable({
+  columns,
+  data,
+  localization: locales[currentLanguage],
+})
+```
+
+The table re-renders with the new strings; no state is reset.
+
+## Common Mistakes
+
+### HIGH Importing a locale from the upstream package name
+
+Wrong:
+
+```tsx
+import { MRT_Localization_ES } from 'material-react-table/locales/es'
+```
+
+Correct:
+
+```tsx
+import { MRT_Localization_ES } from '@lminii/material-react-table/locales/es'
+```
+
+The fork publishes locales under its own `exports` map. The upstream path resolves only if the upstream package is also installed, which produces two copies of MRT.
+
+Source: `MIGRATION.md`
+
+### MEDIUM Custom locale without the language tag
+
+Wrong:
+
+```tsx
+localization: { actions: 'Ações', cancel: 'Cancelar', rowsPerPage: 'Linhas por página' }
+```
+
+Correct:
+
+```tsx
+localization: { language: 'pt', actions: 'Ações', cancel: 'Cancelar', rowsPerPage: 'Linhas por página' }
+```
+
+Without `language`, the English `en` tag from the merged defaults formats row counts, so `1.234` renders as `1,234`.
+
+Source: `packages/material-react-table/src/locales/en.ts`
+
+### MEDIUM Dropping the {column} placeholder
+
+Wrong:
+
+```tsx
+localization: { filterByColumn: 'Filtrer' }
+```
+
+Correct:
+
+```tsx
+localization: { filterByColumn: 'Filtrer par {column}' }
+```
+
+MRT substitutes the header into `{column}`; without it the tooltip and placeholder no longer say which column they apply to.
+
+Source: `packages/material-react-table/src/locales/en.ts`
+
+### LOW Passing an unstable localization object
+
+Wrong:
+
+```tsx
+localization: { ...MRT_Localization_FR, noRecordsToDisplay: t('empty') }, // new object each render
+```
+
+Correct:
+
+```tsx
+const localization = useMemo(() => ({ ...MRT_Localization_FR, noRecordsToDisplay: t('empty') }), [t])
+```
+
+A fresh object every render re-runs the merge and invalidates the memoized table options.
+
+Source: `packages/material-react-table/src/hooks/useMRT_TableOptions.ts`
+
+## API Discovery
+
+`MRT_Localization` in `node_modules/@lminii/material-react-table/dist/index.d.ts` lists every key; `en.ts` in `packages/material-react-table/src/locales` is the reference translation. `ls node_modules/@lminii/material-react-table/locales` shows the shipped locale folders. The Localization guide at `/docs/guides/localization` renders an example per locale.