Files
temetro/.agents/skills/coss/references/primitives/sheet.md
T
Khalid Abdi 929bec8f31 feat: AI-added records save with placeholders + "Added by AI" provenance
Stop blocking AI imports/proposals on missing non-critical fields. Records
the chat agent drafts now save with safe placeholders, auto-generated file
numbers, and a source="ai" marker that surfaces an "Added by AI" badge so a
clinician can review/edit them later.

Backend:
- add `source` (manual|ai) column to patients/appointments/prescriptions
  (migration 0014) + canonical types, services, validation schemas
- relax patient/appointment validation: empty file number allowed, demographic
  + type/provider/initials fall back to placeholders (initials derived from name)
- patients.generateFileNumber() auto-assigns an MRN when one is missing
- proposeAppointment accepts a name when no file number resolves; AI commits +
  /api/ai/import stamp source="ai"

Frontend:
- `source` on Appointment/Patient/Prescription types; AI commits send source="ai"
- reusable <AiBadge> shown on the Patients table/detail and prescriptions list

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 19:27:17 +03:00

2.6 KiB

coss Sheet

When to use

  • Side-panel overlays for settings/details/workflows.
  • Persistent context panels opened from main content area.

When NOT to use

  • If the overlay should be centered and focused -> use Dialog instead.
  • If the overlay is a mobile-only bottom panel -> use Drawer instead.
  • If the flow is a destructive confirmation -> use AlertDialog instead.

Install

npx shadcn@latest add @coss/sheet

Manual deps from docs:

npm install @base-ui/react

Canonical imports

import {
  Sheet,
  SheetContent,
  SheetDescription,
  SheetFooter,
  SheetHeader,
  SheetPanel,
  SheetPopup,
  SheetTitle,
  SheetTrigger,
} from "@/components/ui/sheet"

Minimal pattern

<Sheet>
  <SheetTrigger>Open</SheetTrigger>
  <SheetPopup>
    <SheetHeader>
      <SheetTitle>Are you absolutely sure?</SheetTitle>
      <SheetDescription>
        This action cannot be undone. This will permanently delete your account
        and remove your data from our servers.
      </SheetDescription>
    </SheetHeader>
    <SheetPanel>Content</SheetPanel>
    <SheetFooter>
      <SheetClose>Close</SheetClose>
    </SheetFooter>
  </SheetPopup>
</Sheet>

Patterns from coss particles

  • Portal forwarding: optional portalProps on SheetPopup → Base UI Dialog.Portal (keepMounted, container, …). See portal-props.md.

Key patterns

Sheet from the right side with form:

<Sheet>
  <SheetTrigger render={<Button variant="outline" />}>Edit Profile</SheetTrigger>
  <SheetPopup side="right">
    <SheetHeader>
      <SheetTitle>Edit Profile</SheetTitle>
      <SheetDescription>Make changes to your profile here.</SheetDescription>
    </SheetHeader>
    <SheetPanel className="flex flex-col gap-4">
      <Field name="name">
        <FieldLabel>Name</FieldLabel>
        <Input type="text" />
      </Field>
    </SheetPanel>
    <SheetFooter>
      <SheetClose render={<Button variant="ghost" />}>Cancel</SheetClose>
      <Button>Save</Button>
    </SheetFooter>
  </SheetPopup>
</Sheet>

Side options: top, right, bottom, left.

More examples

See p-sheet-1 through p-sheet-3 for inset and side sheet patterns.

Common pitfalls

  • Using sheet for simple tooltip/popover hints that do not need panel behavior.
  • Missing close actions and focus-return verification on open/close cycle.
  • Overloading sheet with multi-step form logic better handled by dedicated route/modal flow.

Useful particle references

  • sheet with inset: p-sheet-2
  • side sheets: p-sheet-3
  • cross-overlay references: p-dialog-1, p-popover-1, p-menu-2