+
+
+
+
+```
+
+After regeneration, your `` stays in place while the rest of the template is updated with any new entity properties.
+
+### Example - Adding a Custom Table Column
+
+```html
+
+Custom Score
+
+
+
+{{ record.product.customScore }}
+
+```
+
+## Preserved Region Rules
+
+The `az:begin` / `az:end` markers follow these rules:
+
+| Rule | Description |
+|---|---|
+| **Comment wrapper** | Must use HTML comment syntax: `` |
+| **Region names** | Letters, digits, underscores, hyphens, and dots only |
+| **No nesting** | Regions cannot be placed inside other regions |
+| **No duplicates** | Each region name must be unique within a file |
+| **Empty regions are no-ops** | If you don't add anything between the markers, the region is ignored |
+
+## Safety Features
+
+Power Tools includes safety mechanisms to prevent code loss:
+
+- **Abort on malformed markers:** If region markers are broken (unclosed, nested, duplicated, mismatched), the entire file is left untouched. No partial merge ever occurs.
+- **Orphan rescue:** If a region name existed in the old file but not in the newly generated output (for example, if a template update removes a slot), the content is saved to a sidecar file (`.orphaned.txt`) and a warning is shown. Content is never silently dropped.
+- **Ownership guard:** When you toggle the **Generate Overridable Entity** switch on an already-generated entity, Power Tools detects whether existing files contain developer code and refuses to overwrite them.
+
+## Next
+
+[How to Create & Edit Power Tools Templates](How-To-Create-Edit-Power-Tools-Templates.md)
diff --git a/docs/en/Power-Tools-Custom-Code-Mvc.md b/docs/en/Power-Tools-Custom-Code-Mvc.md
new file mode 100644
index 00000000..5ff9fd23
--- /dev/null
+++ b/docs/en/Power-Tools-Custom-Code-Mvc.md
@@ -0,0 +1,216 @@
+# Power Tools Custom Code - MVC
+
+ASP.NET Zero Power Tools generates code that can be fully regenerated whenever you change an entity. The **Custom Code** feature lets you add your own code to the generated pages and classes so that your additions survive regeneration.
+
+This page covers how Custom Code works in **ASP.NET Core MVC** projects. For other UI frameworks.
+
+## Enabling Custom Code
+
+Open Power Tools, select your entity, and turn on the **Generate Overridable Entity** switch in the Entity Information section.
+
+
+
+When this switch is on, Power Tools generates additional extension files that you own. These files are created once and never overwritten, even when you regenerate the entity.
+
+> The switch affects both the server side and the client side.
+
+## How It Works
+
+MVC uses two complementary mechanisms to preserve your code during regeneration:
+
+| Mechanism | How It Works | Applies To |
+|---|---|---|
+| **Extension files** (SkipIfExists) | A base class is regenerated every time. A developer-owned subclass is generated once and never overwritten. | Server-side C# files and MVC Controller / ViewModel classes |
+| **Preserved region slots** (`az:begin` / `az:end`) | Named regions inside regenerated files. Power Tools preserves any code you place between the markers. | Razor views (`.cshtml`) and JavaScript files (`.js`) |
+
+> Razor views and JavaScript files cannot use the base/subclass pattern, so they rely entirely on preserved region slots.
+
+## Server Side
+
+When **Generate Overridable Entity** is enabled, the following server-side extension files are generated. These are shared across all UI frameworks.
+
+| File | Base Class | Purpose |
+|---|---|---|
+| `AppService.Extended.cs` | `AppServiceBase` | Override application service methods |
+| `AppServiceInterface.Extended.cs` | - | Extend the service interface |
+| `Entity.Extended.cs` | `EntityBase` | Add custom properties or methods to the entity |
+| `CreateOrEditDto.Extended.cs` | `CreateOrEditDtoBase` | Extend the input DTO |
+| `EntityDto.Extended.cs` | `EntityDtoBase` | Extend the list DTO |
+| `GetAllInput.Extended.cs` | `GetAllInputBase` | Add custom filter parameters |
+| `GetAllForExcelInput.Extended.cs` | `GetAllForExcelInputBase` | Add custom Excel export filter parameters |
+| `GetAllOutput.Extended.cs` | `GetAllOutputBase` | Extend the output DTO |
+| `GetForEditOutput.Extended.cs` | `GetForEditOutputBase` | Extend the edit output DTO |
+| `LookupDto.Extended.cs` | `LookupDtoBase` | Extend the lookup DTO |
+| `HostController.Extended.cs` | `HostControllerBase` | Extend the API controller |
+
+Each `.Extended.cs` file contains:
+
+```csharp
+// Write your custom code here.
+// ASP.NET Zero Power Tools will not overwrite this class
+// when you regenerate the related entity.
+```
+
+The base files (without `.Extended`) are fully regenerated on every run. New entity properties automatically flow into them. Your customizations in the extension files are preserved because Power Tools never touches them after the first generation.
+
+## MVC C# - Extension Files
+
+When you enable **Generate Overridable Entity**, the MVC Controller and ViewModel classes are split into base and extension files:
+
+| Generated File | Description |
+|---|---|
+| `*Controller.cs` (base) | Abstract base controller with all generated logic. **Regenerated every time.** |
+| `*Controller.Extended.cs` | Your controller subclass. **Generated once, never overwritten.** |
+| `*ViewModel.cs` (base) | Abstract base view model. **Regenerated every time.** |
+| `*ViewModel.Extended.cs` | Your view model subclass. **Generated once, never overwritten.** |
+
+If the entity has a view-only page enabled, a `*ViewEntityViewModel.Extended.cs` is also generated.
+
+### Example for a `Product` Entity
+
+```
+ProductsController.cs ← regenerated (abstract base)
+ProductsController.Extended.cs ← yours (extends base)
+
+ProductsViewModel.cs ← regenerated (abstract base)
+ProductsViewModel.Extended.cs ← yours (extends base)
+```
+
+Override any method in the extension file:
+
+```csharp
+public class ProductsController : ProductsControllerBase
+{
+ // Write your custom code here.
+ // ASP.NET Zero Power Tools will not overwrite this class
+ // when you regenerate the related entity.
+}
+```
+
+## MVC Razor & JavaScript - Preserved Region Slots
+
+Razor views and JavaScript files use named `az:begin` / `az:end` markers. You can place custom markup or code between these markers and it will be preserved on regeneration.
+
+### Index Page - Razor Slots
+
+```html
+
+
+
+
+
+
+
+```
+
+### Index Page Toolbar - Razor Slot
+
+```html
+
+
+
+```
+
+### Index Page - JavaScript Slot
+
+```javascript
+// az:begin(columns)
+// Add custom DataTables columnDefs entries here
+// az:end(columns)
+```
+
+### Create/Edit Modal - Razor Slot
+
+```html
+
+
+
+```
+
+### View Entity Modal - Razor Slot
+
+```html
+
+
+
+```
+
+### Slot Reference
+
+| Slot Name | File | Comment Style | Purpose |
+|---|---|---|---|
+| `filters` | Index Razor (`.cshtml`) | HTML | Custom advanced filter controls |
+| `column-headers` | Index Razor (`.cshtml`) | HTML | Custom table column headers |
+| `toolbar-actions` | Index Razor (`.cshtml`) | HTML | Custom toolbar buttons |
+| `columns` | Index JavaScript (`.js`) | JS | Custom DataTables column definitions |
+| `form-fields` | Create/edit Razor (`.cshtml`) | HTML | Custom form fields |
+| `detail-fields` | View entity Razor (`.cshtml`) | HTML | Custom detail display fields |
+
+> The `column-headers` slot in the Razor file and the `columns` slot in the JavaScript file are **paired**. Adding a custom column requires entries in both files.
+
+### Example - Adding a Custom Column
+
+In the Razor file (`.cshtml`):
+
+```html
+
+Custom Score
+
+```
+
+In the JavaScript file (`.js`):
+
+```javascript
+// az:begin(columns)
+{
+ data: "product.customScore",
+ name: "customScore",
+ render: function(data) { return data || "-"; }
+},
+// az:end(columns)
+```
+
+### Example - Adding a Custom Form Field
+
+```html
+
+.orphaned.txt`) and a warning is shown. Content is never silently dropped.
+- **Ownership guard:** When you toggle the **Generate Overridable Entity** switch on an already-generated entity, Power Tools detects whether existing files contain developer code and refuses to overwrite them.
+
+## Next
+
+[How to Create & Edit Power Tools Templates](How-To-Create-Edit-Power-Tools-Templates.md)
diff --git a/docs/en/Power-Tools-Custom-Code-React.md b/docs/en/Power-Tools-Custom-Code-React.md
new file mode 100644
index 00000000..fe99ab4d
--- /dev/null
+++ b/docs/en/Power-Tools-Custom-Code-React.md
@@ -0,0 +1,273 @@
+# Power Tools Custom Code - React
+
+ASP.NET Zero Power Tools generates code that can be fully regenerated whenever you change an entity. The **Custom Code** feature lets you add your own code to the generated pages and classes so that your additions survive regeneration.
+
+This page covers how Custom Code works in **React** projects. For other UI frameworks.
+
+## Enabling Custom Code
+
+Open Power Tools, select your entity, and turn on the **Generate Overridable Entity** switch in the Entity Information section.
+
+
+
+When this switch is on, Power Tools generates additional customization files that you own. These files are created once and never overwritten, even when you regenerate the entity.
+
+> The switch affects both the server side and the client side.
+
+## How It Works
+
+React uses a different approach than Angular and MVC. Instead of inline region markers or base/subclass patterns for UI files, React generates **separate customization files** with typed hook functions that the generated page imports and calls at fixed extension points.
+
+| Mechanism | How It Works | Applies To |
+|---|---|---|
+| **Extension files** (SkipIfExists) | A base class is regenerated every time. A developer-owned subclass is generated once and never overwritten. | Server-side C# files only |
+| **Customization files** | Separate `.tsx` files with hook functions. Never overwritten. The generated page imports and calls them. | React pages, forms, and detail views |
+| **Regenerated type definitions** | A `customizations.types.ts` file that is regenerated to keep TypeScript types in sync with the entity. | React customization contexts |
+
+## Server Side
+
+When **Generate Overridable Entity** is enabled, the following server-side extension files are generated. These are shared across all UI frameworks.
+
+| File | Base Class | Purpose |
+|---|---|---|
+| `AppService.Extended.cs` | `AppServiceBase` | Override application service methods |
+| `AppServiceInterface.Extended.cs` | - | Extend the service interface |
+| `Entity.Extended.cs` | `EntityBase` | Add custom properties or methods to the entity |
+| `CreateOrEditDto.Extended.cs` | `CreateOrEditDtoBase` | Extend the input DTO |
+| `EntityDto.Extended.cs` | `EntityDtoBase` | Extend the list DTO |
+| `GetAllInput.Extended.cs` | `GetAllInputBase` | Add custom filter parameters |
+| `GetAllForExcelInput.Extended.cs` | `GetAllForExcelInputBase` | Add custom Excel export filter parameters |
+| `GetAllOutput.Extended.cs` | `GetAllOutputBase` | Extend the output DTO |
+| `GetForEditOutput.Extended.cs` | `GetForEditOutputBase` | Extend the edit output DTO |
+| `LookupDto.Extended.cs` | `LookupDtoBase` | Extend the lookup DTO |
+| `HostController.Extended.cs` | `HostControllerBase` | Extend the API controller |
+
+Each `.Extended.cs` file contains:
+
+```csharp
+// Write your custom code here.
+// ASP.NET Zero Power Tools will not overwrite this class
+// when you regenerate the related entity.
+```
+
+The base files (without `.Extended`) are fully regenerated on every run. New entity properties automatically flow into them. Your customizations in the extension files are preserved because Power Tools never touches them after the first generation.
+
+## React Customization Files
+
+When you enable **Generate Overridable Entity**, Power Tools generates the following files alongside the main page:
+
+| Generated File | Overwritten? | Purpose |
+|---|---|---|
+| `customizations.tsx` | **Never** | Hook functions for the list page: extra columns, row actions, toolbar actions |
+| `customizations.types.ts` | **Yes** (regenerated) | TypeScript types for the customization context |
+| `CreateOrEdit*Modal.custom.tsx` | **Never** | Hook functions for the form: extra fields, before/after save |
+| `View*Modal.custom.tsx` | **Never** | Hook functions for the detail view: extra detail items |
+
+> `customizations.types.ts` is the only customization-related file that gets regenerated. This is intentional, when the entity shape changes, the type definitions update and any stale code in your customization files produces a compile error rather than breaking silently.
+
+### File Layout Example for a `Product` Entity
+
+```
+pages/admin/inventory/products/
+├── index.tsx ← regenerated (main page)
+├── customizations.tsx ← yours (list page hooks)
+├── customizations.types.ts ← regenerated (types)
+├── components/
+│ ├── CreateOrEditProductModal.tsx ← regenerated
+│ ├── CreateOrEditProductModal.custom.tsx ← yours (form hooks)
+│ ├── ViewProductModal.tsx ← regenerated
+│ └── ViewProductModal.custom.tsx ← yours (detail hooks)
+```
+
+## List Page Hooks
+
+The `customizations.tsx` file provides three hook functions for the list page:
+
+```tsx
+import type { ReactNode } from "react";
+import type {
+ ProductColumn,
+ ProductRowAction,
+ ProductsPageContext,
+} from "./customizations.types";
+
+/** Columns appended after the generated ones. */
+export const extraColumns = (ctx: ProductsPageContext): ProductColumn[] => [];
+
+/** Extra entries for a row's action menu, appended after the generated ones. */
+export const extraRowActions = (
+ ctx: ProductsPageContext,
+ record: Parameters>[1],
+): ProductRowAction[] => [];
+
+/** Extra buttons in the page header, rendered after the generated ones. */
+export const extraToolbarActions = (ctx: ProductsPageContext): ReactNode => null;
+```
+
+The generated `index.tsx` imports these functions and calls them at the right points:
+
+- `extraColumns` is spread into the Ant Design table column definitions
+- `extraRowActions` is pushed into each row's action dropdown menu
+- `extraToolbarActions` is rendered in the page header area
+
+### Example - Adding a Custom Column
+
+```tsx
+export const extraColumns = (ctx: ProductsPageContext): ProductColumn[] => [
+ {
+ title: "Custom Score",
+ dataIndex: ["product", "customScore"],
+ render: (text: any) => {text ?? "-"},
+ },
+];
+```
+
+### Example - Adding a Custom Toolbar Button
+
+```tsx
+export const extraToolbarActions = (ctx: ProductsPageContext): ReactNode => (
+
+);
+```
+
+### Example - Adding a Custom Row Action
+
+```tsx
+export const extraRowActions = (
+ ctx: ProductsPageContext,
+ record: Parameters>[1],
+): ProductRowAction[] => [
+ {
+ key: "duplicate",
+ label: "Duplicate",
+ onClick: () => {
+ // your duplication logic here
+ },
+ },
+];
+```
+
+## Form Hooks
+
+The `CreateOrEdit*Modal.custom.tsx` file provides three hook functions for the create/edit form:
+
+```tsx
+import type { ReactNode } from "react";
+import type { CreateOrEditProductFormContext } from "../customizations.types";
+import type { CreateOrEditProductDto } from "@api/generated/service-proxies";
+
+/** Form items rendered after the generated ones. */
+export const extraFormFields = (
+ ctx: CreateOrEditProductFormContext,
+): ReactNode => null;
+
+/**
+ * Runs after validation, just before the record is sent to the server.
+ * Adjust `dto` in place to add computed values.
+ * Throw to cancel the save.
+ */
+export const beforeSave = async (
+ ctx: CreateOrEditProductFormContext,
+ dto: CreateOrEditProductDto,
+): Promise => {};
+
+/** Runs after the record is saved and before the modal closes. */
+export const afterSave = async (
+ ctx: CreateOrEditProductFormContext,
+ dto: CreateOrEditProductDto,
+): Promise => {};
+```
+
+The generated `CreateOrEditProductModal.tsx` calls these hooks:
+
+- `extraFormFields` is rendered after the generated form fields inside the `
+
+When this switch is on, Power Tools generates additional extension files that you own. These files are created once and never overwritten, even when you regenerate the entity.
+
+> The switch affects both the server side and the client side.
+
+## How It Works
+
+MVC uses two complementary mechanisms to preserve your code during regeneration:
+
+| Mechanism | How It Works | Applies To |
+|---|---|---|
+| **Extension files** (SkipIfExists) | A base class is regenerated every time. A developer-owned subclass is generated once and never overwritten. | Server-side C# files and MVC Controller / ViewModel classes |
+| **Preserved region slots** (`az:begin` / `az:end`) | Named regions inside regenerated files. Power Tools preserves any code you place between the markers. | Razor views (`.cshtml`) and JavaScript files (`.js`) |
+
+> Razor views and JavaScript files cannot use the base/subclass pattern, so they rely entirely on preserved region slots.
+
+## Server Side
+
+When **Generate Overridable Entity** is enabled, the following server-side extension files are generated. These are shared across all UI frameworks.
+
+| File | Base Class | Purpose |
+|---|---|---|
+| `AppService.Extended.cs` | `AppServiceBase` | Override application service methods |
+| `AppServiceInterface.Extended.cs` | - | Extend the service interface |
+| `Entity.Extended.cs` | `EntityBase` | Add custom properties or methods to the entity |
+| `CreateOrEditDto.Extended.cs` | `CreateOrEditDtoBase` | Extend the input DTO |
+| `EntityDto.Extended.cs` | `EntityDtoBase` | Extend the list DTO |
+| `GetAllInput.Extended.cs` | `GetAllInputBase` | Add custom filter parameters |
+| `GetAllForExcelInput.Extended.cs` | `GetAllForExcelInputBase` | Add custom Excel export filter parameters |
+| `GetAllOutput.Extended.cs` | `GetAllOutputBase` | Extend the output DTO |
+| `GetForEditOutput.Extended.cs` | `GetForEditOutputBase` | Extend the edit output DTO |
+| `LookupDto.Extended.cs` | `LookupDtoBase` | Extend the lookup DTO |
+| `HostController.Extended.cs` | `HostControllerBase` | Extend the API controller |
+
+Each `.Extended.cs` file contains:
+
+```csharp
+// Write your custom code here.
+// ASP.NET Zero Power Tools will not overwrite this class
+// when you regenerate the related entity.
+```
+
+The base files (without `.Extended`) are fully regenerated on every run. New entity properties automatically flow into them. Your customizations in the extension files are preserved because Power Tools never touches them after the first generation.
+
+## MVC C# - Extension Files
+
+When you enable **Generate Overridable Entity**, the MVC Controller and ViewModel classes are split into base and extension files:
+
+| Generated File | Description |
+|---|---|
+| `*Controller.cs` (base) | Abstract base controller with all generated logic. **Regenerated every time.** |
+| `*Controller.Extended.cs` | Your controller subclass. **Generated once, never overwritten.** |
+| `*ViewModel.cs` (base) | Abstract base view model. **Regenerated every time.** |
+| `*ViewModel.Extended.cs` | Your view model subclass. **Generated once, never overwritten.** |
+
+If the entity has a view-only page enabled, a `*ViewEntityViewModel.Extended.cs` is also generated.
+
+### Example for a `Product` Entity
+
+```
+ProductsController.cs ← regenerated (abstract base)
+ProductsController.Extended.cs ← yours (extends base)
+
+ProductsViewModel.cs ← regenerated (abstract base)
+ProductsViewModel.Extended.cs ← yours (extends base)
+```
+
+Override any method in the extension file:
+
+```csharp
+public class ProductsController : ProductsControllerBase
+{
+ // Write your custom code here.
+ // ASP.NET Zero Power Tools will not overwrite this class
+ // when you regenerate the related entity.
+}
+```
+
+## MVC Razor & JavaScript - Preserved Region Slots
+
+Razor views and JavaScript files use named `az:begin` / `az:end` markers. You can place custom markup or code between these markers and it will be preserved on regeneration.
+
+### Index Page - Razor Slots
+
+```html
+
+
+
+
+
+
+
+```
+
+### Index Page Toolbar - Razor Slot
+
+```html
+
+
+
+```
+
+### Index Page - JavaScript Slot
+
+```javascript
+// az:begin(columns)
+// Add custom DataTables columnDefs entries here
+// az:end(columns)
+```
+
+### Create/Edit Modal - Razor Slot
+
+```html
+
+
+
+```
+
+### View Entity Modal - Razor Slot
+
+```html
+
+
+
+```
+
+### Slot Reference
+
+| Slot Name | File | Comment Style | Purpose |
+|---|---|---|---|
+| `filters` | Index Razor (`.cshtml`) | HTML | Custom advanced filter controls |
+| `column-headers` | Index Razor (`.cshtml`) | HTML | Custom table column headers |
+| `toolbar-actions` | Index Razor (`.cshtml`) | HTML | Custom toolbar buttons |
+| `columns` | Index JavaScript (`.js`) | JS | Custom DataTables column definitions |
+| `form-fields` | Create/edit Razor (`.cshtml`) | HTML | Custom form fields |
+| `detail-fields` | View entity Razor (`.cshtml`) | HTML | Custom detail display fields |
+
+> The `column-headers` slot in the Razor file and the `columns` slot in the JavaScript file are **paired**. Adding a custom column requires entries in both files.
+
+### Example - Adding a Custom Column
+
+In the Razor file (`.cshtml`):
+
+```html
+
+
+
+
+
+
+```
+
+### Example - Adding a Custom Toolbar Button
+
+```html
+
+
+
+```
+
+## Preserved Region Rules
+
+The `az:begin` / `az:end` markers follow these rules:
+
+| Rule | Description |
+|---|---|
+| **Comment wrapper matches the file type** | HTML: ``, JavaScript: `// az:begin(name)` |
+| **Region names** | Letters, digits, underscores, hyphens, and dots only |
+| **No nesting** | Regions cannot be placed inside other regions |
+| **No duplicates** | Each region name must be unique within a file |
+| **Empty regions are no-ops** | If you don't add anything between the markers, the region is ignored |
+
+## Safety Features
+
+Power Tools includes safety mechanisms to prevent code loss:
+
+- **Abort on malformed markers:** If region markers are broken (unclosed, nested, duplicated, mismatched), the entire file is left untouched. No partial merge ever occurs.
+- **Orphan rescue:** If a region name existed in the old file but not in the newly generated output (for example, if a template update removes a slot), the content is saved to a sidecar file (`
+
+When this switch is on, Power Tools generates additional customization files that you own. These files are created once and never overwritten, even when you regenerate the entity.
+
+> The switch affects both the server side and the client side.
+
+## How It Works
+
+React uses a different approach than Angular and MVC. Instead of inline region markers or base/subclass patterns for UI files, React generates **separate customization files** with typed hook functions that the generated page imports and calls at fixed extension points.
+
+| Mechanism | How It Works | Applies To |
+|---|---|---|
+| **Extension files** (SkipIfExists) | A base class is regenerated every time. A developer-owned subclass is generated once and never overwritten. | Server-side C# files only |
+| **Customization files** | Separate `.tsx` files with hook functions. Never overwritten. The generated page imports and calls them. | React pages, forms, and detail views |
+| **Regenerated type definitions** | A `customizations.types.ts` file that is regenerated to keep TypeScript types in sync with the entity. | React customization contexts |
+
+## Server Side
+
+When **Generate Overridable Entity** is enabled, the following server-side extension files are generated. These are shared across all UI frameworks.
+
+| File | Base Class | Purpose |
+|---|---|---|
+| `AppService.Extended.cs` | `AppServiceBase` | Override application service methods |
+| `AppServiceInterface.Extended.cs` | - | Extend the service interface |
+| `Entity.Extended.cs` | `EntityBase` | Add custom properties or methods to the entity |
+| `CreateOrEditDto.Extended.cs` | `CreateOrEditDtoBase` | Extend the input DTO |
+| `EntityDto.Extended.cs` | `EntityDtoBase` | Extend the list DTO |
+| `GetAllInput.Extended.cs` | `GetAllInputBase` | Add custom filter parameters |
+| `GetAllForExcelInput.Extended.cs` | `GetAllForExcelInputBase` | Add custom Excel export filter parameters |
+| `GetAllOutput.Extended.cs` | `GetAllOutputBase` | Extend the output DTO |
+| `GetForEditOutput.Extended.cs` | `GetForEditOutputBase` | Extend the edit output DTO |
+| `LookupDto.Extended.cs` | `LookupDtoBase` | Extend the lookup DTO |
+| `HostController.Extended.cs` | `HostControllerBase` | Extend the API controller |
+
+Each `.Extended.cs` file contains:
+
+```csharp
+// Write your custom code here.
+// ASP.NET Zero Power Tools will not overwrite this class
+// when you regenerate the related entity.
+```
+
+The base files (without `.Extended`) are fully regenerated on every run. New entity properties automatically flow into them. Your customizations in the extension files are preserved because Power Tools never touches them after the first generation.
+
+## React Customization Files
+
+When you enable **Generate Overridable Entity**, Power Tools generates the following files alongside the main page:
+
+| Generated File | Overwritten? | Purpose |
+|---|---|---|
+| `customizations.tsx` | **Never** | Hook functions for the list page: extra columns, row actions, toolbar actions |
+| `customizations.types.ts` | **Yes** (regenerated) | TypeScript types for the customization context |
+| `CreateOrEdit*Modal.custom.tsx` | **Never** | Hook functions for the form: extra fields, before/after save |
+| `View*Modal.custom.tsx` | **Never** | Hook functions for the detail view: extra detail items |
+
+> `customizations.types.ts` is the only customization-related file that gets regenerated. This is intentional, when the entity shape changes, the type definitions update and any stale code in your customization files produces a compile error rather than breaking silently.
+
+### File Layout Example for a `Product` Entity
+
+```
+pages/admin/inventory/products/
+├── index.tsx ← regenerated (main page)
+├── customizations.tsx ← yours (list page hooks)
+├── customizations.types.ts ← regenerated (types)
+├── components/
+│ ├── CreateOrEditProductModal.tsx ← regenerated
+│ ├── CreateOrEditProductModal.custom.tsx ← yours (form hooks)
+│ ├── ViewProductModal.tsx ← regenerated
+│ └── ViewProductModal.custom.tsx ← yours (detail hooks)
+```
+
+## List Page Hooks
+
+The `customizations.tsx` file provides three hook functions for the list page:
+
+```tsx
+import type { ReactNode } from "react";
+import type {
+ ProductColumn,
+ ProductRowAction,
+ ProductsPageContext,
+} from "./customizations.types";
+
+/** Columns appended after the generated ones. */
+export const extraColumns = (ctx: ProductsPageContext): ProductColumn[] => [];
+
+/** Extra entries for a row's action menu, appended after the generated ones. */
+export const extraRowActions = (
+ ctx: ProductsPageContext,
+ record: Parameters