ShopOS

The Enterprise dashboard was a standalone project served inside the main product through an iframe. That meant separate auth, separate theme, separate deploy cadence, and a cross-origin wall that blocked any deeper UX integration.

• Migrated routes and components from the standalone repo into the main Next.js app.
• Unified auth so Enterprise inherits the same session and workspace context as the rest of the product.
• Re-platformed the UI on the shared design system, removing a parallel set of styles and primitives.
• Wired enterprise-aware routing so admins land on the right shell without per-feature flags.

Workflow templates power large chunks of the product, but authoring them was an engineering-only task. Canvas Builder turns that into a visual surface.

• Shipped v2: drawer-based form editor architecture, unified field schema across the form and the canvas.
• Performance pass on the canvas runtime and a theme overhaul to bring it under the shared design system.
• Reusable form-editor primitives now shared across the canvas and the admin console.

The previous chat input was a fragile contenteditable that could not express anything richer than plain text. New flows (skills, structured commands, mentions) demanded a real editor.

• Built a tiptap-based editor from the core extensions up: custom skill-tag node, slash-command extension, placeholder, serializer.
• Wired it behind a feature flag, then enabled it by default after a stabilization pass.
• Hardened keyboard handling (IME, accessibility), file validation, filename sanitization, and a toggle-race fix surfaced during code review.

Merchants review and refine AI-generated assets every day. The surface had to support comments, refinements, and shareable deep links into a specific asset.

• Built the media carousel: navigation, asset preview, refine modal, comment overlay.
• Hash-routed deep-linking so a specific asset and modal state survives a reload or a shared link.
• Wired the refine flow end-to-end with the modal lifecycle and the cleanup paths it required.

Skills extend agent capability. The product needed an authenticated surface to upload, preview, manage, and toggle skill packs in both the merchant app and the admin tooling, sharing as much as possible.

• Types, API client, React Query hooks with optimistic updates.
• Dialogs for upload, preview (with markdown + syntax highlighting), overwrite confirmation, delete.
• Settings page integration in the main app; standalone Skills Library page in the admin console.
• Hardened error handling, mobile layout, and a feature-flagged rollout.