Mockgen Shadcn

--- name: mockgen-shadcn model: claude-opus-4-8 effort: high description: > Generate React + shadcn/ui mockup screens from PRD.md files for UI/UX human designer review. Creates a Vite + React 19 + TypeScript + shadcn/ui mockup application with admin dashboard layout (collapsible sidebar navigation, header with logo/notifications/locale/user menu, footer with copyright/version) using React Router v7 for client-side navigation, organized by user role in a mockup/ folder. The app is BUILT (npm run build) and its dist/ output is served by the SINGLE shared Mockup Hub at /mockup — a zero-dependency Node.js server with a landing page listing every application and role (unclickable when not ready) and a configurable port (PORT env / mockup.config.json). The Vite dev server remains available for design iteration only. Input: application name (mandatory), version (mandatory), module (optional). Output: mockup/ folder in the application's context folder containing MOCKUP.html index page, mockup-manifest.json, Vite + React project files, layout components, shadcn/ui components, role-specific page components, and the built dist/ folder; plus the shared hub at /mockup if not already present. Trigger on keywords: "generate mockup shadcn", "generate shadcn mockup", "create shadcn mockup screens", "shadcn UI mockup", "React mockup from user stories", "mockup from PRD.md shadcn", "generate shadcn screens", "create shadcn UI screens". Accepts application name and version as input (e.g., /mockgen-shadcn hub_middleware v1.0.3). Optionally accepts a module name to limit generation to screens for that module only (e.g., /mockgen-shadcn hub_middleware v1.0.3 module:Location Information). When module is specified, only page components for that module are generated/updated; layout components, sidebars, config files, and other module pages are left untouched (the manifest is updated and the app is rebuilt). Automatically excludes strikethrough (deprecated/removed) items.

Mockgen shadcn/ui

Generate a Vite + React 19 + TypeScript + shadcn/ui mockup application from PRD.md for UI/UX designer review. Layout uses React components (header, sidebar, footer) composed in a shared layout route. Pages are React Router routes rendered inside the layout. All navigation is client-side via React Router <Link> and useNavigate.

The mockup is generated with base/basename set to /{app_slug}/, built with npm run build, and served from its dist/ folder by the shared Mockup Hub — a single zero-dependency Node.js server at <root>/mockup/ that serves ALL applications' mockups (see references/mockup-hub-template.md). The hub renders a landing page listing every application and role (roles are unclickable until the app is generated AND built) and listens on a configurable port (PORT env var → mockup.config.json → 3000). The Vite dev server (npm run dev) remains available for design iteration only.

Stack

Input

This skill uses standardized input resolution. Provide:

Application Folder Resolution

The application name is matched against root-level application folders:

1. Strip any leading <number>_ prefix from folder names (e.g., 1_hub_middleware → hub_middleware)
2. Match case-insensitively against the provided application name
3. Accept snake_case, kebab-case, or title-case input (all match the same folder)
4. If no match found, list available applications and stop

Auto-Resolved Paths

App slug (used as the URL base path): the application folder name with the leading <number>_ prefix stripped (e.g., 1_hub_middleware → hub_middleware). Record it during input resolution — it is baked into vite.config.ts (base), main.tsx (BrowserRouter basename), and all MOCKUP.html links.

Example Invocations

• /mockgen-shadcn hub_middleware v1.0.3 (all modules, up to v1.0.3)
• /mockgen-shadcn hub_middleware v1.0.3 module:Location Information (one module, specific version)
• /mockgen-shadcn "Hub Middleware" v1.0.3 module:Employer (title-case app name)

Version and Module Filtering

• Only include user stories, NFRs, constraints, and references from sections whose version tag is less than or equal to the target version
• If a module is provided (e.g., module:Location Information), only generate/update pages for that specific module. All other modules are skipped. Common pages (home, profile, account, notifications), layout components (header, footer, sidebars), and config files are NOT regenerated when a module filter is active — only the module's own page components are written (and MOCKUP.html is updated for only that module's cards).
• If no module is provided, process all modules (default behavior)

Argument parsing: The module: prefix is the canonical form. Also accept:

• module:"Location Information" (quoted, with space)
• module:location_information (snake_case — convert to title-case for matching)
• Natural language: for Location Information module, only Location Information

Version Gate

Before starting any work, resolve the application folder first (see Input Resolution below), then check CHANGELOG.md in the application folder (<app_folder>/CHANGELOG.md):

1. If <app_folder>/CHANGELOG.md does not exist, skip this check (first-ever execution for this application).
2. If <app_folder>/CHANGELOG.md exists, scan all ## vX.Y.Z headings and determine the highest version using semantic versioning comparison.
3. Compare the requested version against the highest version:
   • If requested version >= highest version: proceed normally.
   • If requested version < highest version: STOP immediately. Print: "Version {requested} is lower than the current application version {highest} recorded in <app_folder>/CHANGELOG.md. Execution rejected." Do NOT proceed with any work.

Workflow

Step 1: Parse PRD.md

Read the auto-resolved PRD.md file and extract:

1. Application name: Derive from the parent folder name containing PRD.md. Strip leading number and underscore prefix, then title-case. Example: 1_hub_middleware -> "Hub Middleware"

2. Application initials: First letter of each word, uppercase. Example: 1_hub_middleware -> "HM"

3. Modules: Each ## Module Name section under a # Module Category heading. Record the module name and its description (the line after the heading).

4. User stories per module: Lines matching - [USxx#####] As a {Role} user, I want to... Extract: tag, role, action summary.

5. Unique roles: Collect all distinct roles from user stories. Example: "Hub Administrator", "Hub Operation Support"

6. Target version (from input argument): If a version was provided, record it for filtering in the next sub-step.

1a: Version Filtering and Strikethrough Exclusion (MANDATORY)

PRD.md is a version-controlled document. Each section (User Story, Non Functional Requirement, Constraint, Reference) has a version tag in square brackets, e.g., [v1.0.1]. Items may also be marked with strikethrough (~~) to indicate they are deprecated/removed.

Strikethrough exclusion (always applied, regardless of version parameter):

• Any line wrapped in ~~strikethrough~~ markup MUST be excluded from processing
• This includes user stories, NFRs, constraints, and references
• Example: ~~[USHM00006] As a Hub Administrator user, I want to...~~ → SKIP
• Partially strikethrough lines (where only part is struck) should still be excluded if the tag identifier is within the strikethrough

Version filtering (applied only when a target version is provided):

• Each section under a module has one or more version tags like [v1.0.0] or [v1.0.1]
• Items listed under a version tag belong to that version
• When a target version is specified (e.g., v1.0.1):
  • Include items from sections whose version tag is <= target version
  • Exclude items from sections whose version tag is > target version
• Version comparison uses semantic versioning: compare major, then minor, then patch
• When no target version is specified, include all items from all versions (but still exclude strikethrough items)

Version tracking per section: Record which version tag each item belongs to, as this will be used for traceability in the generated pages.

Example parsing of a section with multiple versions:

### User Story
[v1.0.0]
- ~~[USHM00006] As a Hub Administrator user, I want to manage...~~
- [USHM00009] As a Hub Administrator user, I want to map...
[v1.0.1]
- [USHM00012] As a Hub Administrator user, I want to manage the list...

With target version v1.0.0:

• USHM00006 → EXCLUDED (strikethrough)
• USHM00009 → INCLUDED (v1.0.0 <= v1.0.0, not strikethrough)
• USHM00012 → EXCLUDED (v1.0.1 > v1.0.0)

With target version v1.0.1 (or no version specified):

• USHM00006 → EXCLUDED (strikethrough)
• USHM00009 → INCLUDED
• USHM00012 → INCLUDED

1c: Module Filtering (applied only when a module argument is provided)

When a module argument is present, apply module filtering after version filtering:

1. Match the specified module against the list of parsed modules (case-insensitive, ignoring leading/trailing whitespace). Also accept snake_case input by converting it to title-case for comparison (e.g., location_information → match "Location Information").
2. Record the matched module name for use in Step 3 and beyond.
3. If no module matches, stop and report the available module names to the user before proceeding.
4. Module filter scope: the filter only affects page component generation (Step 6e). All other steps complete normally (parsing, design system, planning) but output is restricted to the filtered module's pages.

Module-filtered generation mode differs from full generation in these ways:

MOCKUP.html partial update (module-filtered mode):

• Read the existing MOCKUP.html
• Locate the screen cards section for the target module (search by module name heading or existing card tags)
• Replace only those cards with freshly generated ones reflecting the new pages
• Update the total screen count per role (add net new pages)
• Update the version badge if it changed
• Update the "N new screens added in vX.Y.Z" banner text
• Leave all other role sections and cards unchanged

Step 1b: Discover and Load Module Models

After parsing PRD.md, look for module models at the auto-resolved model path: <app_folder>/context/model/

For each module extracted in Step 1:

1. Convert the module name to kebab-case to derive the model folder name:

   • Lowercase the module name and replace spaces with hyphens
   • Examples: "Location Information" → location-information, "Industrial Classification" → industrial-classification, "Employer" → employer

2. Check for {model_dir}/{kebab-module}/model.md

3. If the file exists, parse it and extract the following sections:

   • Section 2 – Collection Catalog: collection names and types (Root Collection, Audit Collection, etc.)
   • Section 5 – Field Detail per Collection: for each collection — field name, type, required, nullable, constraints/notes
   • Section 6 – Embedded Document Definitions: embedded type name and its sub-fields
   • Section 7 – Enum Definitions: enum name and all allowed values with descriptions
   • Section 9 – Index Recommendations: indexed fields (used to identify search/filter parameters)

4. Store this as the module model for the module, keyed by module name

Field classification (used during page generation in Step 6e):

Fallback: If no model.md exists for a module, infer fields from user story text (original behavior).

Step 2: Load Design System

Load the design system using a two-tier resolution strategy:

2a: PRD.md Design System Reference (Primary Source)

Check if PRD.md contains a # Design System section. If it does:

1. Extract the referenced file path (e.g., from [DESIGN_SYSTEM.md](reference/DESIGN_SYSTEM.md))
2. Resolve the path relative to PRD.md's location
3. If the referenced file exists, read it and extract:
   • Color palettes (primary, secondary, accent, neutral — hex values)
   • Typography (font families, font sizes, weight scale)
   • Spacing scale (if overriding Tailwind defaults)
   • Component patterns (button styles, card styles, form input styles, table styles, badge/chip styles, modal patterns)
   • Layout grid rules
4. Apply extracted tokens to the Tailwind config (tailwind.config.js) custom colors/fonts, shadcn/ui CSS variables in src/index.css, and all generated components

2b: Context Design Folder (Fallback)

If PRD.md does not have a # Design System section, or the referenced file does not exist, fall back to the application's <app_folder>/context/design/ folder. This folder contains pre-defined design tokens and Tailwind component guidelines maintained externally by the UI/UX team.

Read all files in {app_name}/context/design/ (where {app_name} is the resolved application folder name from Step 1). Apply the design tokens and guidelines found there to all generated mockup pages.

Expected files (any or all may be present):

• design-system.md — Colors, typography, spacing, and visual style definitions
• components.md — Reusable component patterns and Tailwind class conventions
• guidelines.md — Layout rules, accessibility standards, and stack-specific guidelines

2c: Default Fallback

If neither the PRD reference nor the {app_name}/context/design/ folder provides design tokens, use the default shadcn/ui "New York" style: zinc/neutral color palette, Inter/Geist font stack, and default shadcn/ui component styling with CSS variables.

2d: Process Flow Status States

If PRD.md contains a # High Level Process Flow section, scan it for entity status lifecycle descriptions (e.g., "Received → Validated → Enriched → Active"). For each status lifecycle found:

• Ensure list pages for the corresponding module include a status column with colored <Badge> variants for each state
• Use design system color tokens for badge variants (e.g., default for active/completed, secondary for pending, destructive for failed/rejected)

Step 3: Plan Screen Files

For each role, determine ALL pages to generate. Every clickable link, tab, or action in any generated page MUST have a corresponding page component. No link may be a dead end.

Module filter applied here: If a module argument was provided (Step 1c), plan only the pages for that module across all roles. Skip common pages (home, profile, account, notifications) and skip all other modules entirely. The screen plan table should list only the filtered module's pages.

3a: Core Pages (React components)

1. home.tsx: Default home/dashboard page with welcome message and summary widgets
2. profile.tsx: User profile page (linked from header user dropdown)
3. account.tsx: Account settings page (linked from header user dropdown)
4. notifications.tsx: Notifications page (linked from header notification bell)
5. One page per module that has user stories for this role

3b: Sub-Pages (Detail / Edit / Create)

For each module page, analyze the user stories and identify sub-pages needed:

3f: Report Layout Pages (conditional — if PRD.md contains report-related content)

Scan PRD.md for report-related content:

• NFRs mentioning "report", "Report interface", "generate report", "report generation"
• User stories describing generating/downloading PDF, Excel, or CSV reports
• A "Report" module or report-related NFRs defining specific report types

If report requirements are found, generate HTML report layout mockups for each identified report. These layouts serve as draft previews for human designers/stakeholders to verify the report structure before the AI coding agent implements the actual report generation code.

For each identified report, create a standalone HTML file in a public/reports/ subfolder:

Report layout file conventions:

• Each report layout is a standalone self-contained HTML document (not a React component) with its own <html>, <head>, <body> tags and Tailwind CDN <script> in the head
• Layout simulates a print-ready A4 page with appropriate margins and sizing:

  <body class="bg-gray-100">
    <div class="mx-auto bg-white shadow" style="width: 210mm; min-height: 297mm; padding: 15mm;">
      <!-- Report content -->
    </div>
  </body>
  

• Report header: Report title (centered, bold), generation date, filter parameters used
• Report body: Data table or summary layout using actual fields from the module model (if model/{module}/model.md exists, use its field definitions for column headers)
• Report footer: Page indicator text ("Page 1 of 1"), generation timestamp
• Use sample data rows (5-10 rows) with realistic placeholder values matching model constraints
• Apply the design system colors from Step 2 for header background, borders, and accents
• For landscape reports (wide tables with many columns), use style="width: 297mm; min-height: 210mm;"

Report parameter section: Above the report data, include a gray-shaded "Parameters" box showing the filter criteria used to generate the report (e.g., Date Range: 2025-01-01 to 2025-12-31, Department: All, Status: Active).

Add to MOCKUP.html: Include a "Reports" section at the bottom of each role's screen cards (after all module cards) listing the report layout links. Report links open in new tabs pointing to the hub's static route /{app_slug}/reports/{report_file}.html. Also list the report file names in the manifest's reports array.

Add to sidebar: If reports are present, add a "Reports" navigation group in each role's sidebar with links opening report layouts in new tabs.

3c: Tabbed Pages

If a module page contains tabs (e.g., a detail page with Overview, Documents, History tabs), use shadcn/ui <Tabs> component within the same page component. Only create separate page component files for tabs if the tab content is substantial (more than ~100 lines). Use the naming convention for separate files: {module}-tab-{tab_name}.tsx

Example: employer-tab-overview.tsx, employer-tab-documents.tsx, employer-tab-history.tsx

3d: Page File Naming Convention

Convert names to kebab-case for file names, PascalCase for component names. Example: "Location Information" → file: location-information.tsx, component: LocationInformation

3e: Build Screen Plan

Build a complete screen plan. Every entry must map to a generated file:

Step 4: Create Output Folder Structure

Module filter: When a module argument is active, skip this step entirely — the folder structure already exists from a previous full generation. Only page components for the target module will be written in Step 6e.

Create the mockup folder at the auto-resolved mockup output path (full generation only):

<app_folder>/context/
  mockup/
    .gitignore
    package.json
    vite.config.ts
    tsconfig.json
    tsconfig.app.json
    tsconfig.node.json
    tailwind.config.js
    postcss.config.js
    components.json                      # shadcn/ui configuration
    index.html                           # Vite entry HTML
    MOCKUP.html                          # Per-app screen index (served by hub at /{app_slug})
    mockup-manifest.json                 # Hub discovery manifest (app, stack, roles, version)
    dist/                                # Built output served by the hub (npm run build; gitignored)
    public/
      reports/                           # Report layout files (if applicable)
    src/
      main.tsx                           # React entry point
      App.tsx                            # Router configuration
      index.css                          # Tailwind directives + shadcn/ui CSS variables
      lib/
        utils.ts                         # cn() utility
      components/
        ui/                              # shadcn/ui components
          button.tsx
          card.tsx
          table.tsx
          badge.tsx
          input.tsx
          label.tsx
          select.tsx
          dialog.tsx
          dropdown-menu.tsx
          avatar.tsx
          separator.tsx
          tabs.tsx
          switch.tsx
          tooltip.tsx
          breadcrumb.tsx
          pagination.tsx
          sheet.tsx
        layout/
          app-layout.tsx                 # Shared layout with sidebar + header + footer
          app-header.tsx                 # Top header component
          app-sidebar.tsx                # Sidebar nav component (role-aware)
          app-footer.tsx                 # Footer component
          sidebar-config.ts              # Sidebar menu items per role
      pages/
        {role-kebab-case}/
          home.tsx
          profile.tsx
          account.tsx
          notifications.tsx
          {module-kebab-case}.tsx
          {module-kebab-case}-detail.tsx
          {module-kebab-case}-create.tsx
          {module-kebab-case}-edit.tsx
          ...

Step 4b: Generate Project Config Files

Module filter: When a module argument is active, skip this step entirely.

Generate all config and entry files using the templates from references/admin-layout-template.md.

.gitignore

node_modules/
dist/
.DS_Store
*.log
*.local

Key project setup:

• package.json — Vite + React 19 + TypeScript + Tailwind CSS + shadcn/ui dependencies
• vite.config.ts — Vite config with React plugin, path aliases, and base: "/{app_slug}/" (REQUIRED so the built app is servable by the hub at /{app_slug})
• tsconfig.json / tsconfig.app.json / tsconfig.node.json — TypeScript configs with path aliases
• tailwind.config.js — Tailwind config with shadcn/ui integration and design system tokens
• postcss.config.js — PostCSS with Tailwind and autoprefixer
• components.json — shadcn/ui configuration (New York style, zinc base)
• index.html — Vite entry HTML with Google Fonts
• src/main.tsx — React root render with <BrowserRouter basename="/{app_slug}"> (REQUIRED to match the Vite base)
• src/App.tsx — React Router configuration with all role/page routes
• src/index.css — Tailwind directives + shadcn/ui CSS variables (light and dark)
• src/lib/utils.ts — cn() utility (clsx + tailwind-merge)

Step 4c: Generate shadcn/ui Component Files

Module filter: When a module argument is active, skip this step entirely.

Generate the shadcn/ui component files directly into src/components/ui/. These follow the standard shadcn/ui "New York" style patterns. The components are owned by the project — they are NOT imported from npm.

Required components (generate all of these):

Each component follows the standard shadcn/ui implementation pattern:

• Uses @radix-ui/* primitives for accessibility
• Styled with Tailwind CSS utility classes
• Supports className prop via cn() utility
• Uses cva (class-variance-authority) for variants where applicable
• Forwards refs properly

Step 4d: Write mockup-manifest.json and Ensure the Mockup Hub

Always runs (full AND module-filtered generation; in module-filtered mode UPDATE the existing manifest — version, generatedAt, per-role screen counts).

1. Write <app_folder>/context/mockup/mockup-manifest.json following the schema in references/mockup-hub-template.md:

   {
     "app": "{app_slug}",
     "appName": "{App Name}",
     "description": "{short description from PRD.md}",
     "stack": "shadcn",
     "version": "{target version}",
     "generatedAt": "{YYYY-MM-DD}",
     "roles": [
       { "name": "{Role Name}", "slug": "{role-kebab-case}", "screens": {count} }
     ],
     "reports": ["{report_file}.html"]
   }
   

   (reports only when report layouts were generated.) The hub reads this manifest to route the app and render its landing-page card; without it the app shows as "Not generated yet" and its roles are unclickable.

2. Ensure the shared hub exists at <root>/mockup/ per the Ensure-Hub rules in references/mockup-hub-template.md: create server.js, package.json, mockup.config.json, and .gitignore if missing; upgrade server.js/package.json only when the existing HUB_VERSION is lower; never overwrite an existing mockup.config.json or .gitignore. All hub artifacts (config, logs, any node_modules/) live inside <root>/mockup/ and are gitignored there.

Step 5: Generate MOCKUP.html Index

Module filter: When a module argument is active, do NOT regenerate the full MOCKUP.html. Instead, apply a partial update as described in Step 1c: update only the target module's screen cards, the version badge, and the per-role screen count. Leave all other content unchanged.

Create the index page using the template in references/mockup-index-template.md.

MOCKUP.html is this app's screen index, served by the hub at /{app_slug}. It shows:

• Hub startup banner with instructions (cd <root>/mockup && npm start — no install needed; port configurable via PORT env var or mockup.config.json) and a reminder that the app must be built (npm run build) before screens open
• Application name and description
• Target version used for generation
• Number of excluded items for transparency
• For each role: role name, list of screen cards with links
• ALL screen links use target="_blank" rel="noopener noreferrer" with root-relative URLs /{app_slug}/{role}/{page} (never hardcode http://localhost:<port> — the hub port is user-configurable) so they open in new tabs via the running hub (SPA fallback serves dist/index.html, React Router resolves the route)
• A "Open Role Dashboard" quick-launch link per role section

Step 6: Generate Layout Components and Page Components

Use templates from references/admin-layout-template.md.

Apply the design system from Step 2 (colors, typography, spacing) to all components via the CSS variables in src/index.css and the Tailwind config.

Module filter: When a module argument is active, skip steps 6a–6d (layout components). Proceed directly to 6e for the target module's page components only. Also update the footer version string in app-footer.tsx if the version changed.

6a: Generate src/components/layout/app-layout.tsx

Shared layout component using React Router <Outlet>. Contains:

• <AppHeader> at the top (fixed)
• <AppSidebar> on the left (fixed, collapsible)
• <Outlet> for page content (scrollable)
• <AppFooter> at the bottom
• ThemeProvider wrapping for dark mode support
• Sidebar state management (expanded/collapsed)

6b: Generate src/components/layout/app-header.tsx

Header component containing:

• Logo + App Name (left) — <Link> to home
• Notification bell with shadcn/ui <DropdownMenu> and <Badge> count
• Globe/locale selector with shadcn/ui <DropdownMenu>
• Dark mode toggle button using next-themes useTheme()
• User <Avatar> with <DropdownMenu> (Profile, Account, Logout)
• All Profile/Account/Notifications links use React Router <Link> / useNavigate()
• Lucide React icons throughout (Bell, Globe, Moon, Sun, User, LogOut, Settings)

6c: Generate src/components/layout/app-footer.tsx

Simple footer with copyright year and version string using <Separator> divider.

6d: Generate src/components/layout/sidebar-config.ts and app-sidebar.tsx

sidebar-config.ts: Export a configuration object mapping each role to its sidebar menu items:

export type SidebarItem = {
  title: string;
  path: string;
  icon: string; // Lucide icon name
};

export type SidebarConfig = {
  [role: string]: {
    label: string;
    items: SidebarItem[];
    reports?: { title: string; href: string }[];
  };
};

app-sidebar.tsx: Sidebar component that:

• Reads the current role from React Router useParams()
• Renders menu items from sidebar-config.ts for that role
• Highlights the active menu item using useLocation().pathname
• Uses React Router <Link> for navigation (not HTMX)
• Uses Lucide React icons dynamically based on config
• Supports collapsed state (icons only) via context/state
• Has a collapsible toggle button

6e: Generate page components (src/pages/{role-kebab-case}/{page}.tsx)

Each page component is a standard React functional component that returns JSX. Pages use shadcn/ui components for all UI elements.

All navigation within page components uses React Router <Link> or useNavigate().

Breadcrumbs: Use shadcn/ui <Breadcrumb> component. Home link is a <Link>, module link is a <Link>, current page is <BreadcrumbPage> (non-interactive).

Admin Layout: Screen Content Generation

For each module page, analyze the user stories and generate appropriate UI mockup elements:

Model-Driven Field Usage (MANDATORY when model file exists)

When a module model was loaded in Step 1b, use its actual field definitions — not generic placeholders — to populate every page. Generic field names like "Field 1" or "Description" are not acceptable when a model is available.

Field type → shadcn/ui component mapping:

List / Search pages ({module}.tsx):

• Filter section: <Card> with filter inputs only for fields in Index Recommendations (Section 9). Use the correct component per the mapping above. Enum-indexed fields use <Select>. Date-indexed fields use date range pickers.
• Results table: shadcn/ui <Table> with 5–7 most identifying non-system fields as columns. For embedded objects, show as a single column (e.g., "Company Name"). Null/optional fields shown with a dash (—).
• Table row actions: View → <Link> to {module}-detail, Edit → <Link> to {module}-edit, Delete → shadcn/ui <Dialog> confirm
• Pagination (MANDATORY): Every results table MUST include shadcn/ui <Pagination> directly below the table. Requirements:
  • Default page size: 10 items per page
  • Show "Showing X–Y of Z results" summary text on the left
  • Show page size <Select> with options 10, 25, 50 on the right (default 10)
  • Show Previous / Next and page number buttons using <Pagination> component
  • Page state managed via React useState (currentPage, pageSize, totalItems)
  • Previous/Next buttons are disabled when at first/last page
  • Use sample data: populate exactly 10 visible rows in the table (matching the default page size)

Detail pages ({module}-detail.tsx):

• Show ALL non-system fields, grouped logically:
  • Basic fields: flat primitive fields in a 2-column grid <Card>
  • Embedded objects (e.g., address, contact): each in its own labeled sub-<Card>
  • Embedded arrays (e.g., personsInCharge): rendered as a sub-<Table> with a row per item
  • Enum fields: display value wrapped in a <Badge> with appropriate variant
  • ISODate fields: formatted as DD MMM YYYY HH:mm in sample data
  • Boolean fields: show as a <Badge> ("Active" variant=default / "Inactive" variant=secondary)
• Include Edit <Button>, Delete <Dialog> confirm, and Back to List <Button> actions

Create pages ({module}-create.tsx):

• Include ALL Required: Yes non-system fields as mandatory inputs (mark with * via <Label>)
• Include Required: No fields as optional inputs where they make

…(truncated)