Liteverge Browser OpenTelemetry

This skill has two modes. Choose based on what the user is asking for.

Initialize tracing on a new project

If the user wants to set up OpenTelemetry / Liteverge tracing on a frontend project that doesn't have it yet (install packages, create instrumentation file, wire entrypoint), follow:

→ init.md

Add custom instrumentation to an existing project

If the project already has Liteverge OTel initialized (has an instrumentation file and @opentelemetry/api installed) and the user wants to add custom spans, attributes, or tracing to specific user flows, follow:

→ instrument.md

How to decide

• User says "add tracing", "add observability", "instrument this app" → init.md
• User says "trace this action", "add a span", "measure this user flow" → instrument.md
• If unsure whether OTel is already set up, check for @opentelemetry/api in package.json dependencies. If present, use instrument.md. If not, use init.md.

About Logs and Metrics

OTel Logs and Metrics SDKs for the browser are currently immature and not included in this skill. For error reporting from the browser, use span.recordException() or span.addEvent() on an active span. For performance metrics, use the Web Vitals library or PerformanceObserver with custom spans.