Files
temetro/.agents/skills/coss/references/primitives/separator.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

1.3 KiB

coss Separator

When to use

  • Visual/semantic separation between related blocks.
  • Section dividers in menus, cards, and grouped controls.

Install

npx shadcn@latest add @coss/separator

Manual deps from docs:

npm install @base-ui/react

Canonical imports

import { Separator } from "@/components/ui/separator"

Minimal pattern

<div className="flex flex-col gap-2">
  <span className="text-sm">Section A</span>
  <Separator />
  <span className="text-sm">Section B</span>
</div>

Patterns from coss particles

Key patterns

Horizontal separator (default):

<Separator />

Vertical separator inline:

<div className="flex items-center gap-4">
  <span>Home</span>
  <Separator orientation="vertical" className="h-4" />
  <span>Settings</span>
</div>

More examples

See p-separator-1 for the core pattern. Also used within p-menu-1, p-group-1, and p-input-group-7.

Common pitfalls

  • Adding separators between every small element, creating visual clutter.
  • Using separators where spacing alone communicates grouping better.
  • Forgetting orientation/context in dense vertical command layouts.

Useful particle references

  • core patterns: p-separator-1
  • cross-primitive dividers: p-menu-1, p-group-1, p-input-group-7