Where your
mockups live.

Not a taste dispute. The prototype wrote 577 lines of MockupsLibraryView.tsx and imported four things from the design system: Button, Dialog, Typography, Menu. It never touched Tabs, never touched EmptyState, never touched LayoutHeaderTabs. Every problem below follows from that one fact.

Projects has no designed empty state at all — it renders a dashed New tile into the grid and lets that carry the meaning. That is the precedent worth copying, and it is why option A's library root can never be blank.

Two populations, one folder

A mockup on the dashboard is one of two completely different things, and this is the fact the whole model turns on.

Schema

Conventions copied verbatim from UploadFolder: cuid id, workspace FK authoritative, creator recorded, soft delete, denormalized children timestamp, unique name per workspace.

// apps/api/prisma/schema/editor/mockup.prisma  (new file)

model MockupFolder {
  /// @zod.cuid()
  id               String              @id @default(cuid())
  name             String
  user             User                @relation(fields: [userId], references: [id], onDelete: Cascade)
  userId           String
  workspaceId      String
  workspace        Workspace           @relation(fields: [workspaceId], references: [id], onDelete: Cascade)
  entries          MockupFolderEntry[]
  createdAt        DateTime            @default(now())
  deletedAt        DateTime?
  entriesUpdatedAt DateTime            @default(now())
  sortOrder        Int                 @default(0)

  @@unique([workspaceId, name], name: "workspaceIdMockupFolderName")
  @@index([workspaceId])
}

model MockupFolderEntry {
  /// @zod.cuid()
  id          String       @id @default(cuid())
  folder      MockupFolder @relation(fields: [folderId], references: [id], onDelete: Cascade)
  folderId    String
  source      MockupSource                // the load-bearing column
  referenceId String                      // CMS numeric id as string, or Upload cuid
  sortOrder   Int          @default(0)
  placement   Json?                       // normalized intent, nullable, P5
  createdAt   DateTime     @default(now())

  @@unique([folderId, source, referenceId], name: "folderSourceReference")
  @@index([folderId])
}

enum MockupSource { CATALOG  UPLOAD }

• source ships in the first migration or never. Mockup identity is a bare number in 154 occurrences across 43 files today. Adding the discriminator later means a migration over every row plus a second pass through every card, lane and selection call site.
• referenceId is a String, matching Bookmark.referenceId, which already stores mixed-type references this way.
• placement stores intent, not a rect. MockupDesignRect is {x,y,width,height} and gets cleared whenever the design changes, because it is aspect-dependent. Store normalized centre, scale and rotation instead — or leave it null until P5.

Endpoints

Express router → controller → service, mounted beside /folders, following folders.router.ts exactly. Typed client regenerated with pnpm generate:api-client; hooks land in @repo/resources/src/queries/mockupFolders/.

Likes stay where they are

Liking is Bookmark with BookmarkType.MOCKUP, per user, already shipped server-side. It does not move into folders and it is not a folder — it is the flat list you collect from. One catch: createBookmark validates the id against the CMS and throws 404 otherwise, with an integration test asserting exactly that. Liking your own uploaded photo therefore needs a server change.

Order of work