TraceKit Browser SDK Setup

Auth Bootstrap

Do not tell the user to go sign up, log in separately, or manually create an API key before setup. First check for existing TraceKit auth. If ~/.tracekitconfig does not contain the production profile or TRACEKIT_API_KEY is missing, apply the tracekit-auth skill first. Use ./scripts/run-tracekit-auth.sh status to check, then guide the user through the TraceKit email verification flow with register and verify. That flow signs the user into an existing account for that email or creates the account automatically, then saves the returned credentials for the rest of the setup.

When To Use

Use this skill when the user asks to:

• Add TraceKit to a JavaScript or TypeScript application
• Add observability or APM to a vanilla JS project
• Instrument a browser app with error tracking or distributed tracing
• Configure TraceKit API keys in a frontend project
• Set up error monitoring in a plain HTML/JS or Web Components app
• Add performance monitoring to a vanilla TypeScript project

Framework users: If the user is using React, Vue, Angular, Next.js, or Nuxt, use the corresponding framework wrapper skill instead (tracekit-react-sdk, tracekit-vue-sdk, tracekit-angular-sdk, tracekit-nextjs-sdk, tracekit-nuxt-sdk). Framework wrappers provide tighter integration with error boundaries, router breadcrumbs, and SSR support.

Svelte/Solid users: These frameworks do not have dedicated wrapper skills. Use this browser SDK skill directly - it works in any JavaScript environment.