uds-tailwind-test 0.1.2 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AI_USAGE.md CHANGED
@@ -69,9 +69,10 @@ layout.
69
69
  When using `AppShell`:
70
70
 
71
71
  - treat it as the standard product-shell wrapper for app experiences
72
- - use the theme `Sidebar` primitives inside the `sidebar` region rather than ad hoc navigation markup
72
+ - **Sidebar is mandatory and customized**: the `sidebar` slot must be built only with the **UDS theme Sidebar system** exported from `uds-tailwind-test` (`SidebarProvider` as an ancestor where needed, plus `Sidebar`, `SidebarHeader`, `SidebarContent`, `SidebarFooter`, and menu primitives such as `SidebarMenu`, `SidebarMenuItem`, `SidebarMenuButton`, `SidebarGroup`, `SidebarRail`, `SidebarTrigger`, etc.). Do **not** replace it with a plain `<aside>`, ad hoc flex columns, third-party nav, or copied shadcn sidebar markup that bypasses these exports.
73
73
  - use the optional `listview` region for master-detail, queue, inbox, or search-result flows
74
74
  - omit the `listview` or `footer` regions when the screen does not need them
75
+ - **Viewport fill**: the app must occupy the full browser width and height. Ensure `html`, `body`, and `#root` fill the viewport (e.g. zero default body margin, `min-height: 100dvh` / `height: 100%` on the root chain as appropriate) and give the outer shell `AppShell` a `className` such as `min-h-dvh w-full min-w-0` so the layout is not clipped or letterboxed.
75
76
 
76
77
  ## Styling Rules
77
78
 
package/README.md CHANGED
@@ -124,7 +124,8 @@ If you are using this package with an AI code generator, give it these rules:
124
124
  4. Treat `AppShell`, `Sidebar`, `Item`, `FileUpload`, `FileUploadCards`, and `ChartContainer` as first-party components, not stock shadcn primitives.
125
125
  5. Treat the package root exports as the source of truth for available components.
126
126
  6. For authenticated application screens, default to `AppShell` unless the user explicitly requests a different layout.
127
- 7. When using `AppShell`, prefer the theme `Sidebar` primitives for the `sidebar` region and only include the `listview` or `footer` regions when the screen needs them.
127
+ 7. When using `AppShell`, the `sidebar` region **must** use the **UDS theme Sidebar** exports from `uds-tailwind-test` (`Sidebar`, `SidebarHeader`, `SidebarContent`, `SidebarFooter`, `SidebarMenu*`, `SidebarProvider`, etc.)—not ad hoc sidebars or non-package nav. Only include the `listview` or `footer` regions when the screen needs them.
128
+ 8. The shell must **fill the viewport** (full width and height): normalize `html`/`body`/`#root` and apply `min-h-dvh w-full min-w-0` (or equivalent) on the top-level shell so the app does not sit in a short or narrow column.
128
129
 
129
130
  For a dedicated AI-oriented guide, see [AI_USAGE.md](./AI_USAGE.md).
130
131