<!-- source-hash: 2dec9acc6154e0160c391613c83b192e -->
Centralized barrel export file for all type definitions in the `@flamingo/ui-kit` package, providing a single import entry point for platform, application, and domain types.

## Key Components

| Export Group | Modules |
|---|---|
| **Core Platform** | `announcement`, `categories`, `category`, `media`, `platform` |
| **Database & API** | `supabase` |
| **Authentication** | `auth` |
| **Content** | `blog`, `case-study`, `customer-interview`, `luma`, `product-release`, `delivery`, `vendor`, `video-processing` |
| **User & Profile** | `employee`, `profile`, `team`, `user` |
| **Communication** | `slack`, `waitlist` |
| **Business Logic** | `faq`, `report`, `stack` |
| **Navigation** | `navigation` |
| **Tools & Shell** | `tool.types`, `shell.types`, `os.types` |
| **Marketing & Access** | `marketing`, `access-code-cohorts`, `icons`, `permissions`, `tmcg` |

> **Note:** `platform` uses named re-exports (`export type { ... }`) to avoid conflicts with internal types, exposing only `LegacyPlatform`, `PlatformFilter`, `PlatformName`, `PlatformOption`, `PlatformRecord`, `PlatformSettings`, and `PlatformStats`.

## Usage Example

```typescript
// Import any type directly from the package root
import type {
  PlatformSettings,
  Category,
  BlogPost,
  UserProfile,
  NavigationItem,
} from '@flamingo/ui-kit'

// No need to reach into individual type files
const config: PlatformSettings = { /* ... */ }
const nav: NavigationItem[] = []
```

## Notes

- Prefer importing from `@flamingo/ui-kit` directly rather than deep-importing individual type modules (e.g., `@flamingo/ui-kit/types/platform`).
- `categories` also uses named exports to selectively expose `Category`, `CategoryCardProps`, and `RealCategoryCardProps`.