@tailor-platform/app-shell 1.14.0 → 1.16.0

package/skills/app-shell-patterns/references/components/command-palette.md

@@ -0,0 +1,413 @@
+---
+title: CommandPalette
+description: Keyboard-driven quick navigation with fuzzy search for all routes in your application
+---
+
+<!-- GENERATED by docs-kit from docs-src/components/command-palette.docs.outline.md — do not edit by hand. -->
+
+# CommandPalette
+
+`CommandPalette` provides a keyboard-driven quick navigation interface that allows users to search and navigate to any page in your application. Activated with `Cmd+K` (Mac) or `Ctrl+K` (Windows), it offers fuzzy search across all accessible routes.
+
+## Usage
+
+The CommandPalette is built into `AppShell` and rendered automatically. No explicit import or placement is needed:
+
+```tsx
+import { AppShell, SidebarLayout } from "@tailor-platform/app-shell";
+
+function App() {
+  return (
+    <AppShell modules={modules}>
+      <SidebarLayout />
+    </AppShell>
+  );
+}
+```
+
+The CommandPalette will automatically:
+
+- ✅ Index all navigatable routes from your modules
+- ✅ Provide fuzzy search functionality
+- ✅ Show breadcrumb paths for context
+- ✅ Resolve dynamic params on the current route branch into real paths
+- ✅ Display module icons
+- ✅ Respect access control (hidden routes won't appear)
+
+## Keyboard Shortcuts
+
+### Opening/Closing
+
+| Shortcut                   | Action                |
+| -------------------------- | --------------------- |
+| `Cmd + K` (Mac)            | Toggle CommandPalette |
+| `Ctrl + K` (Windows/Linux) | Toggle CommandPalette |
+| `Esc`                      | Close CommandPalette  |
+
+### Navigation
+
+| Shortcut       | Action                           |
+| -------------- | -------------------------------- |
+| `↑` / `↓`      | Navigate up/down through results |
+| `Enter`        | Navigate to selected route       |
+| Type to search | Filter routes by fuzzy search    |
+
+## Features
+
+### Fuzzy Search
+
+The CommandPalette uses intelligent fuzzy search that matches:
+
+- **Route titles** - Page names from your resource meta
+- **Paths** - URL segments
+- **Breadcrumbs** - Full navigation path
+
+Example searches:
+
+- `dash` → Matches "Dashboard"
+- `prod det` → Matches "Products > Product Details"
+- `ord` → Matches "Orders", "Order Details", etc.
+
+### Breadcrumb Display
+
+Each result shows its full navigation path for context:
+
+```
+🏠 Dashboard > Analytics > Revenue
+📦 Products > Categories > Electronics
+📋 Orders > History > 2024
+```
+
+When the current URL already fixes a dynamic segment, the palette keeps routes on that branch navigable and displays those resolved values in the path. It only substitutes params on the current route branch, not into sibling routes.
+
+For example, on `/users/42` the palette can include `/users/42` and `/users/42/profile`, and does **not** incorrectly rewrite sibling routes like `/users/new`.
+
+### Access Control Integration
+
+The CommandPalette automatically respects your route guards:
+
+- Hidden routes (via `hidden()` guard) don't appear in search
+- Protected routes are filtered based on current user permissions
+- Dynamic updates when context changes
+
+### Icon Display
+
+Module icons are displayed next to search results for visual recognition:
+
+```tsx
+const productsModule = defineModule({
+  path: "products",
+  component: ProductsPage,
+  meta: {
+    title: "Products",
+    icon: <Package />, // Shown in CommandPalette
+  },
+});
+```
+
+## Contextual Actions
+
+In addition to navigation results, the CommandPalette can surface page-level actions. Use the `useRegisterCommandPaletteActions` hook to register actions that appear in the **Actions** section of the palette. Actions are unregistered automatically when the component unmounts.
+
+```tsx
+import { useRegisterCommandPaletteActions } from "@tailor-platform/app-shell";
+
+function OrderDetailPage() {
+  useRegisterCommandPaletteActions("Order Actions", [
+    { key: "confirm", label: "Confirm order", onSelect: handleConfirm },
+    { key: "cancel", label: "Cancel order", icon: <XIcon />, onSelect: handleCancel },
+  ]);
+}
+```
+
+### Parameters
+
+| Parameter | Type                     | Description                                              |
+| --------- | ------------------------ | -------------------------------------------------------- |
+| `group`   | `string`                 | Display group name for the actions shown in the palette  |
+| `actions` | `CommandPaletteAction[]` | List of actions to register (see `CommandPaletteAction`) |
+
+### `CommandPaletteAction`
+
+| Property   | Type                          | Description                                                                   |
+| ---------- | ----------------------------- | ----------------------------------------------------------------------------- |
+| `key`      | `string`                      | Unique key for React reconciliation                                           |
+| `label`    | `string`                      | Visible label shown in the palette; also used for search matching             |
+| `icon`     | `ReactNode`                   | Optional icon rendered next to the label                                      |
+| `group`    | `string`                      | Optional group override; defaults to the `group` parameter passed to the hook |
+| `onSelect` | `() => void \| Promise<void>` | Callback invoked when the user selects the action                             |
+
+> **Note:** `icon` changes alone do not trigger re-registration. To reflect a dynamic icon update, also change the action's `key` or `label`.
+
+### ActionPanel Integration
+
+When you use the [`ActionPanel`](./action-panel.md) component, its enabled actions (not `disabled`, not `loading`, and with an `onClick` handler) are automatically registered to the CommandPalette under the panel's `title`. No additional setup is required.
+
+For more details see [`useRegisterCommandPaletteActions`](../api/use-register-command-palette-actions.md).
+
+## Async Search Sources
+
+In addition to built-in page search and contextual actions, you can wire async, prefix-activated search sources into the CommandPalette via the `searchSources` prop on `AppShell`.
+
+### How It Works
+
+1. Pass an array of `SearchSource` objects to `AppShell`'s `searchSources` prop.
+2. When the user types a source's `prefix` followed by `:` (e.g. `ORD:`), the palette switches into **search mode**: the Actions and Pages sections are hidden and only results from that source are shown.
+3. On the **empty-input** state, the palette renders a **Search Modes** section listing every registered source so users can activate a mode with a single click.
+
+### Basic Example
+
+```tsx
+import {
+  AppShell,
+  SidebarLayout,
+  DefaultSidebar,
+  type SearchSource,
+} from "@tailor-platform/app-shell";
+
+const searchSources: readonly SearchSource[] = [
+  {
+    prefix: "ORD",
+    title: "Orders",
+    search: async (query, { signal }) => {
+      const results = await api.searchOrders(query, { signal });
+      return results.map((o) => ({
+        key: o.id,
+        label: o.number,
+        description: `${o.customerName} — ${o.date}`,
+        path: `/orders/${o.id}`,
+      }));
+    },
+  },
+  {
+    prefix: "CUST",
+    title: "Customers",
+    search: async (query, { signal }) => {
+      const results = await api.searchCustomers(query, { signal });
+      return results.map((c) => ({
+        key: c.id,
+        label: c.name,
+        path: `/customers/${c.id}`,
+      }));
+    },
+  },
+];
+
+function App() {
+  return (
+    <AppShell modules={modules} searchSources={searchSources}>
+      <SidebarLayout sidebar={<DefaultSidebar />} />
+    </AppShell>
+  );
+}
+```
+
+### `SearchSource`
+
+| Property | Type                                                                                         | Required | Description                                                                                        |
+| -------- | -------------------------------------------------------------------------------------------- | -------- | -------------------------------------------------------------------------------------------------- |
+| `prefix` | `string`                                                                                     | ✅       | Mode-activating prefix (e.g. `"ORD"`). Case-sensitive, alphanumeric only.                          |
+| `title`  | `string`                                                                                     | ✅       | Heading shown above results and in the Search Modes list (e.g. `"Orders"`).                        |
+| `icon`   | `ReactNode`                                                                                  | No       | Optional icon shown next to each result that lacks its own icon.                                   |
+| `search` | `(query: string, options: { signal: AbortSignal }) => Promise<CommandPaletteSearchResult[]>` | ✅       | Async function invoked with the query text after the prefix and an `AbortSignal` for cancellation. |
+
+### `CommandPaletteSearchResult`
+
+| Property      | Type        | Required | Description                                                    |
+| ------------- | ----------- | -------- | -------------------------------------------------------------- |
+| `key`         | `string`    | ✅       | Unique key for React reconciliation.                           |
+| `label`       | `string`    | ✅       | Visible label shown in the palette (e.g. `"Order #ORD-1234"`). |
+| `description` | `string`    | No       | Optional secondary text (e.g. `"山田太郎 - 2024/01/15"`).      |
+| `icon`        | `ReactNode` | No       | Optional icon for this specific result.                        |
+| `path`        | `string`    | ✅       | Resolved navigation path (e.g. `"/orders/abc-123"`).           |
+
+### Prefix Syntax
+
+The prefix match is **case-sensitive**. When a user types `ORD:`, the string after the colon (including any space) is forwarded to `search` as the query:
+
+```
+User types: ORD:
+  → search("", { signal })  — empty query, show all or hint
+
+User types: ORD:12345
+  → search("12345", { signal })
+
+User types: ORD: alice
+  → search(" alice", { signal })  — leading space preserved
+```
+
+## Extending the built-in palette
+
+The supported extension points are:
+
+- `searchSources` on `AppShell` for async, prefix-activated search modes
+- [`useRegisterCommandPaletteActions`](../api/use-register-command-palette-actions.md) for page-level actions
+- [`ActionPanel`](./action-panel.md), whose enabled rows are registered automatically
+
+`CommandPalette` itself is built into `AppShell`; there is no separate public hook for rebuilding the palette UI from scratch.
+
+## Examples
+
+### Basic Usage
+
+The CommandPalette works automatically with your module definitions:
+
+```tsx
+const modules = [
+  defineModule({
+    path: "dashboard",
+    component: DashboardPage,
+    meta: { title: "Dashboard", icon: <Home /> },
+    resources: [
+      defineResource({
+        path: "analytics",
+        component: AnalyticsPage,
+        meta: { title: "Analytics" },
+      }),
+    ],
+  }),
+  defineModule({
+    path: "products",
+    component: ProductsPage,
+    meta: { title: "Products", icon: <Package /> },
+    resources: [
+      defineResource({
+        path: ":id",
+        component: ProductDetailPage,
+        meta: { title: "Product Details" },
+      }),
+    ],
+  }),
+];
+
+// CommandPalette will show:
+// - Dashboard
+// - Dashboard > Analytics
+// - Products
+// - Products > Product Details (when applicable)
+```
+
+### With Access Control
+
+Routes hidden by guards won't appear in search:
+
+```tsx
+const adminModule = defineModule({
+  path: "admin",
+  component: AdminPage,
+  meta: { title: "Admin Panel" },
+  guards: [
+    ({ context }) => {
+      return context.currentUser?.role === "admin" ? pass() : hidden(); // Won't show in CommandPalette for non-admins
+    },
+  ],
+});
+```
+
+### Search Behavior
+
+```
+User types: "prod"
+Results:
+  📦 Products
+  📦 Products > Product Details
+  📦 Products > Categories
+
+User types: "dash ana"
+Results:
+  🏠 Dashboard > Analytics
+
+User types: "ord 123"
+Results:
+  📋 Orders > Order #123 (if dynamic routes are indexed)
+```
+
+## Design
+
+The CommandPalette follows these design principles:
+
+### Visual Design
+
+- **Clean, focused UI** - Minimal distractions
+- **Clear hierarchy** - Module icons, titles, and breadcrumbs
+- **Active state** - Highlight selected result
+- **Empty state** - "No results found" message
+
+### UX Patterns
+
+- **Immediate feedback** - Results update as you type
+- **Keyboard-first** - All actions accessible via keyboard
+- **Contextual information** - Breadcrumbs show location
+- **Quick access** - Single shortcut to open
+
+### Performance
+
+- **Instant search** - Client-side fuzzy matching
+- **Debounced input** - Smooth typing experience
+- **Lazy loading** - Routes loaded only when needed
+
+## Best Practices
+
+### Do:
+
+- ✅ Provide clear, descriptive titles in resource meta
+- ✅ Use meaningful module icons for visual recognition
+- ✅ Structure modules logically for better discoverability
+- ✅ Keep route hierarchies shallow when possible
+
+### Don't:
+
+- ❌ Use generic titles like "Page 1", "Section A"
+- ❌ Create deeply nested resources (hard to navigate)
+- ❌ Forget to set meta.title on resources
+- ❌ Use similar titles for different routes
+
+## Accessibility
+
+- **Keyboard navigation** - Full keyboard support
+- **ARIA labels** - Proper labels for screen readers
+- **Focus management** - Focus trapped in dialog when open
+- **ESC to close** - Standard dialog behavior
+
+## Related Components
+
+- [AppShell](./app-shell.md) - Root component that provides CommandPalette
+- [SidebarLayout](./sidebar-layout.md) - Layout that includes CommandPalette
+
+## Related Concepts
+
+- [Modules and Resources](../concepts/modules-and-resources.md) - Define routes that appear in CommandPalette
+- [Routing and Navigation](../concepts/routing-navigation.md) - Navigation system
+- [Guards and Permissions](../api/guards/overview.md) - Control route visibility
+
+## Troubleshooting
+
+### Routes not appearing in search
+
+**Problem:** Some routes don't show up in CommandPalette
+
+**Solutions:**
+
+1. Check that the resource has a `meta.title` defined
+2. Verify the route isn't hidden by a guard
+3. Ensure the route is navigatable (not a redirect-only route)
+
+### Search not matching expected routes
+
+**Problem:** Typing a route name doesn't find it
+
+**Solutions:**
+
+1. Try typing the breadcrumb path: "Products Categories"
+2. Use abbreviations: "prod cat"
+3. Check spelling of the title in resource meta
+
+### CommandPalette not opening
+
+**Problem:** `Cmd+K` / `Ctrl+K` doesn't work
+
+**Solutions:**
+
+1. Check if another app is capturing the shortcut
+2. Verify you're using `SidebarLayout` (CommandPalette is included)
+3. Check browser console for JavaScript errors

package/skills/app-shell-patterns/references/components/csv-importer.md

@@ -0,0 +1,214 @@
+---
+title: CsvImporter
+description: Guided multi-step CSV import flow with drag-and-drop upload, column mapping, validation, and inline error correction
+---
+
+<!-- GENERATED by docs-kit from docs-src/components/csv-importer.docs.outline.md — do not edit by hand. -->
+
+# CsvImporter
+
+The `CsvImporter` component provides a guided, multi-step CSV import flow rendered inside a drawer. It handles drag-and-drop file upload, interactive column mapping, Standard Schema validation, inline cell editing, and async server-side validation.
+
+## Import
+
+```tsx
+import {
+  CsvImporter,
+  useCsvImporter,
+  csv,
+  type CsvSchema,
+  type CsvColumn,
+  type CsvImportEvent,
+  type CsvCellIssue,
+  type CsvCorrection,
+  type CsvColumnMapping,
+  type ParsedRow,
+  type InferCsvRow,
+} from "@tailor-platform/app-shell";
+```
+
+## Basic Usage
+
+Use the `useCsvImporter` hook to manage state, then render `<CsvImporter>` with the returned props.
+
+```tsx
+import { CsvImporter, useCsvImporter, csv } from "@tailor-platform/app-shell";
+import { Button } from "@tailor-platform/app-shell";
+
+function ProductImport() {
+  const { open, props } = useCsvImporter({
+    schema: {
+      columns: [
+        {
+          key: "name",
+          label: "Name",
+          required: true,
+          aliases: ["product_name"],
+          schema: csv.string({ min: 1 }),
+        },
+        {
+          key: "price",
+          label: "Price",
+          schema: csv.number({ min: 0 }),
+        },
+        {
+          key: "active",
+          label: "Active",
+          schema: csv.boolean(),
+        },
+      ],
+    },
+    onImport: (event) => {
+      console.log(event.summary);
+    },
+  });
+
+  return (
+    <>
+      <Button onClick={open}>Import CSV</Button>
+      <CsvImporter {...props} />
+    </>
+  );
+}
+```
+
+## `useCsvImporter`
+
+The `useCsvImporter` hook manages the open/close state and returns both an `open` function and `props` to spread onto `<CsvImporter>`.
+
+### Options
+
+| Option        | Type                                               | Default            | Description                                                                 |
+| ------------- | -------------------------------------------------- | ------------------ | --------------------------------------------------------------------------- |
+| `schema`      | `CsvSchema`                                        | —                  | Column definitions for the import (see [CsvSchema](#csvschema))             |
+| `onImport`    | `(event: CsvImportEvent) => void \| Promise<void>` | —                  | Called when the user confirms the import after resolving all errors         |
+| `onValidate`  | `(rows: ParsedRow[]) => Promise<CsvCellIssue[]>`   | —                  | Optional async callback for server-side validation after schema checks pass |
+| `maxFileSize` | `number`                                           | `10485760` (10 MB) | Maximum allowed file size in bytes                                          |
+
+### Return Value
+
+| Property | Type               | Description                                           |
+| -------- | ------------------ | ----------------------------------------------------- |
+| `open`   | `() => void`       | Function to programmatically open the importer drawer |
+| `props`  | `CsvImporterProps` | Props object to spread directly onto `<CsvImporter>`  |
+
+## `CsvImporter` Props
+
+`CsvImporter` is intended to be used with props returned from `useCsvImporter`. Spread the `props` object directly onto the component.
+
+```tsx
+<CsvImporter {...props} />
+```
+
+## Schemas
+
+### `CsvSchema`
+
+```ts
+type CsvSchema = {
+  columns: CsvColumn[];
+};
+```
+
+### `CsvColumn`
+
+| Property      | Type               | Default | Description                                                                             |
+| ------------- | ------------------ | ------- | --------------------------------------------------------------------------------------- |
+| `key`         | `string`           | —       | Internal key; becomes the object key in parsed row data                                 |
+| `label`       | `string`           | —       | Display label shown in the mapping UI                                                   |
+| `description` | `string`           | —       | Optional hint shown in the mapping UI                                                   |
+| `required`    | `boolean`          | `false` | Whether this column must be mapped before proceeding                                    |
+| `aliases`     | `string[]`         | —       | Alternative CSV header names for automatic matching                                     |
+| `schema`      | `StandardSchemaV1` | —       | Standard Schema validator for coercion and validation (see [csv helpers](#csv-helpers)) |
+
+## `csv` Helpers
+
+Built-in Standard Schema validators for common CSV column types. Each helper handles both coercion and validation in a single declaration.
+
+| Helper                                                                    | Output type        | Description                                                             |
+| ------------------------------------------------------------------------- | ------------------ | ----------------------------------------------------------------------- |
+| `csv.string(options?: { min?: number; max?: number })`                    | `string`           | Pass-through string with optional length constraints                    |
+| `csv.number(options?: { min?: number; max?: number; integer?: boolean })` | `number`           | Coerces raw CSV string to a number; rejects `NaN`                       |
+| `csv.boolean(options?: { truthy?: string[]; falsy?: string[] })`          | `boolean`          | Recognises `"true"/"1"/"yes"` and `"false"/"0"/"no"` (case-insensitive) |
+| `csv.date()`                                                              | `Date`             | Coerces raw CSV string to a `Date`; rejects unparseable values          |
+| `csv.enum(values: string[])`                                              | `T extends string` | Validates the value is one of the allowed strings (case-sensitive)      |
+
+```tsx
+// String with required check (min: 1)
+csv.string({ min: 1 });
+
+// Number with lower bound
+csv.number({ min: 0 });
+
+// Integer only
+csv.number({ integer: true });
+
+// Boolean with defaults: truthy = ["true","1","yes"], falsy = ["false","0","no"]
+csv.boolean();
+
+// Date
+csv.date();
+
+// Enum
+csv.enum(["active", "inactive", "pending"]);
+```
+
+## Server-side Validation
+
+Use `onValidate` to perform async checks (e.g. uniqueness constraints) after schema validation passes. Return an array of `CsvCellIssue` objects to mark cells with errors or warnings.
+
+```tsx
+const { open, props } = useCsvImporter({
+  schema: { columns: [...] },
+  onValidate: async (rows) => {
+    const issues = await checkUniqueness(rows);
+    return issues; // CsvCellIssue[]
+  },
+  onImport: (event) => { /* ... */ },
+});
+```
+
+### `CsvCellIssue`
+
+| Property    | Type                   | Description                                          |
+| ----------- | ---------------------- | ---------------------------------------------------- |
+| `rowIndex`  | `number`               | 0-based row index                                    |
+| `columnKey` | `string`               | The schema column key                                |
+| `level`     | `"error" \| "warning"` | `"error"` blocks import; `"warning"` allows import   |
+| `message`   | `string`               | Human-readable message displayed inline in the table |
+
+## Import Event
+
+The `onImport` callback receives a `CsvImportEvent` with the following shape:
+
+| Property      | Type                                                                | Description                                                              |
+| ------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------ |
+| `file`        | `File`                                                              | The original file selected by the user                                   |
+| `mappings`    | `CsvColumnMapping[]`                                                | The confirmed column mappings                                            |
+| `corrections` | `CsvCorrection[]`                                                   | Corrections made by the user in the review step                          |
+| `issues`      | `CsvCellIssue[]`                                                    | Any remaining issues (warnings only — errors are resolved before import) |
+| `summary`     | `{ totalRows, validRows, correctedRows, skippedRows, warningRows }` | Summary statistics                                                       |
+| `buildRows()` | `() => Promise<InferCsvRow<T>[]>`                                   | Reconstruct fully-processed rows with schema coercion and corrections    |
+
+## `event.buildRows()`
+
+A method on the import event that reconstructs the fully processed row data on the client side. The return type is inferred from the schema definition — column keys become object keys, and `StandardSchemaV1` output types are preserved.
+
+```tsx
+onImport: async (event) => {
+  const rows = await event.buildRows();
+  // rows is typed based on schema — e.g. { name: string; price: number; ... }[]
+  await saveToBackend(rows);
+},
+```
+
+> If you are sending the file, mappings, and corrections to a backend for processing, you do not need `buildRows()`.
+
+## i18n
+
+`CsvImporter` includes built-in English and Japanese labels. No additional setup is required.
+
+## Related Components
+
+- [Sheet](./sheet.md) — Slide-in panel (the drawer used internally by CsvImporter)
+- [Button](./button.md) — Use as the trigger to open the importer