How packages fit together

Understand the Tulip package map: foundation, UI, data surfaces, actions, files, content, and AI.

Tulip is organized as focused packages that compose into a full business application system.

Each package solves one layer. You can adopt them one by one, but they are designed to feel consistent when used together.

Package map

Area	Packages	Purpose
Foundation	`@tulip-systems/core`, `@tulip-systems/app`, `@tulip-systems/auth`	App configuration, shell components, layouts, auth-aware flows, and shared infrastructure.
UI	`@tulip-systems/ui`	Shared components and styling primitives used across Tulip apps and packages.
Data surfaces	`@tulip-systems/query`, `@tulip-systems/data-tables`, `@tulip-systems/inline`	Filtering, sorting, pagination, tables, loading strategies, and inline editing.
Actions	`@tulip-systems/commands`	Typed, reusable, permission-aware actions rendered through menus and command primitives.
Files	`@tulip-systems/storage`, `@tulip-systems/drive`, `@tulip-systems/drive-local`, `@tulip-systems/drive-google`	Uploads, asset serving, file manager UI, provider contracts, local storage, and Google Drive-backed trees.
Content	`@tulip-systems/editor`, `@tulip-systems/editor-storage`	Rich-text editing and storage helpers.
AI	`@tulip-systems/ai`	Agents, tools, streaming chat, MCP helpers, and AI UI primitives.
Scaffolding	`create-tulip-app`	Start a new Tulip application from maintained templates.

A typical Tulip screen combines several packages:

Core and App provide the app foundation and layout.
UI provides the shared component language.
Query defines filters, sorting, pagination, and URL-backed state.
Data Tables renders records using the resolved query controllers.
Commands attaches typed actions to rows, toolbars, context menus, or bulk selections.
Inline lets users update values in place when a full form would slow them down.
Storage or Drive handles files when records need attachments, folders, media, or documents.
AI can expose the same domain actions as tools for assistants and agents.

Use Query for query input state, not Data Tables.
Use Data Tables for table rendering and loading strategies, not filter definitions.
Use Commands for actions that need reuse, permissions, disabled state, or menu rendering.
Use Storage for flat uploaded assets tied to domain records.
Use Drive for file manager workflows, folders, selection, provider-backed trees, and document surfaces.
Use AI when assistants need application-aware tools, not just chat UI.

If you are building a record list, start with Query and Data Tables.

If you are building row actions, start with Commands.

If you are adding file uploads to a form, start with Storage.

If you are building a file manager, start with Drive.

If you are building a workspace assistant, start with AI.