Help users integrate Databuddy into their own products. Use when the user wants to install or use Databuddy's SDK, React or Vue component, tracker helpers, Node SDK, server-side feature flags, REST API, event tracking endpoint, or LLM observability package.
Use this skill for people adopting Databuddy in their own app or backend. Optimize for the public integration surface, not the internal monorepo.
@databuddy/sdk/react@databuddy/sdk/vuehttps://cdn.databuddy.cc/databuddy.js@databuddy/sdk@databuddy/sdk/nodecreateServerFlagsManager from @databuddy/sdk/node@databuddy/aiRead public-surfaces.md when you need framework-specific routing, env vars, or endpoint details. Read event-design.md when the user asks what custom events to add, which properties are useful, how to keep events actionable, or how to avoid noisy/high-cardinality tracking.
@databuddy/ai before custom /llm instrumentationclientId for browser tracking and flagsDATABUDDY_API_KEY for server-side tracking, API access, and LLM observabilityhttps://basket.databuddy.cchttps://basket.databuddy.cc/llmhttps://api.databuddy.cc/v1https://api.databuddy.cchttps://cdn.databuddy.cc/databuddy.jsclientIdNEXT_PUBLIC_DATABUDDY_CLIENT_IDVITE_DATABUDDY_CLIENT_IDDATABUDDY_API_KEYDATABUDDY_WEBSITE_ID or a per-event websiteId@databuddy/sdk/react<Databuddy /> near the app root@databuddy/sdk for custom events@databuddy/sdk/vuedata-* attributes@databuddy/sdk/nodeapiKey authflush() before exit in serverless or short-lived runtimescreateServerFlagsManager from @databuddy/sdk/node with clientId (commonly DATABUDDY_CLIENT_ID)/public/v1/flags (default base https://api.databuddy.cc), not from basketclientId, not API key-only authx-api-key: dbdy_... (preferred), or Authorization: Bearer dbdy_...https://api.databuddy.cc/v1https://basket.databuddy.cc@databuddy/ai for OpenAI, Anthropic, or Vercel AI SDK integrationsDATABUDDY_API_KEYsnake_case for event names and property keysbasket.databuddy.ccclientId is configuredflush() if batching is enabled