원클릭으로 Manus에서 모든 스킬 실행

workleap-telemetry

스타8

포크2

업데이트2026년 3월 1일 06:21

Guide for @workleap/telemetry, Workleap's unified telemetry connecting Honeycomb, LogRocket, and Mixpanel with automatic correlation IDs. Use this skill when: (1) Initializing wl-telemetry in a frontend application (2) Correlation values (Telemetry Id, Device Id) and cross-tool data correlation (3) Honeycomb tracing, OpenTelemetry spans, and performance monitoring (4) LogRocket session replay, user identification, and privacy controls (5) Mixpanel analytics, event tracking, and cross-product tracking (6) Configuring wl-telemetry diagnostic loggers (LogRocketLogger) (7) Storybook/test setup with Noop telemetry clients (8) Reviewing or troubleshooting telemetry instrumentation

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

workleap

workleap/wl-squide

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Workleap Telemetry (wl-telemetry)

@workleap/telemetry is an umbrella package that integrates Honeycomb, LogRocket, and Mixpanel with consistent correlation IDs for unified debugging and analysis.

Critical Rules

Use umbrella package — Always use @workleap/telemetry, not standalone packages
Do not invent APIs — Only use documented APIs from references
Correlation is automatic — Never manually set Telemetry Id or Device Id; never create your own TelemetryContext instances
Noop for non-production — Use NoopTelemetryClient in Storybook/tests
Privacy matters — Never log PII to LogRocket; use data-public/data-private attributes
productFamily is required — initializeTelemetry requires "wlp" or "sg" as the first argument

Reference Guide

For detailed documentation beyond the rules above, consult:

references/api.md — Initialization options, TelemetryClient properties, Honeycomb/LogRocket/Mixpanel client APIs, React hooks, Noop clients, LogRocketLogger
references/integrations.md — Platform-specific configuration, Honeycomb tracing patterns, LogRocket privacy and user identification, Mixpanel event tracking, cross-platform correlation workflows
references/examples.md — Full application setup, Storybook/test configuration, user identification, custom Honeycomb traces, Mixpanel tracking patterns, logging configuration, troubleshooting

이 저장소의 다른 Skills

같은 저장소

workleap-squide

workleap/wl-squide

Squide (@squide/firefly) — Workleap's React modular application shell. Use when: (1) Working with FireflyRuntime, initializeFirefly, AppRouter, or FireflyProvider (2) Creating or modifying Squide host applications or modules (3) Registering routes, navigation items, or MSW request handlers (4) Squide integrations with TanStack Query, i18next, LaunchDarkly, Honeycomb, MSW, or Storybook (5) Deferred registrations or conditional navigation items (6) Global data fetching: usePublicDataQueries, useProtectedDataQueries (7) Squide hooks for event bus, environment variables, feature flags, logging, or bootstrapping state (8) Error boundaries or modular architecture in Squide applications

2026-06-108

turborepo

workleap/wl-squide

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

2026-03-028

workleap-logging

workleap/wl-squide

Guide for @workleap/logging, a structured logging library for Workleap frontend TypeScript applications. Use this skill when: (1) Setting up or configuring @workleap/logging loggers (BrowserConsoleLogger, CompositeLogger) (2) Using @workleap/logging API: log levels, chained segments, scopes, styled output (3) Composing or filtering @workleap/logging loggers for multi-destination logging (4) Integrating @workleap/logging with LogRocket via CompositeLogger (5) Reviewing PRs or troubleshooting @workleap/logging usage

2026-03-018

workleap-react-best-practices

workleap/wl-squide

React performance optimization guidelines for Single Page Applications (SPA) at Workleap. Use when writing, reviewing, or refactoring React SPA code to ensure optimal performance patterns. Triggers on tasks involving React components, state management, bundle optimization, re-render prevention, rendering performance, or JavaScript performance improvements. Covers async waterfall elimination, bundle size reduction, re-render optimization, rendering efficiency, JS micro-optimizations, and advanced React patterns. Does NOT cover server-side rendering (SSR), Next.js, or server components.

2026-03-018

workleap-web-configs

workleap/wl-squide

Workleap's shared web configuration packages (@workleap/eslint-configs, typescript-configs, rsbuild-configs, rslib-configs, stylelint-configs, browserslist-config). Use when: (1) Setting up or customizing shared web tooling configs in a Workleap project (2) Configuring ESLint by project type (web app, React library, TS library, monorepo) (3) Configuring TypeScript by project type (web-application, library, monorepo-workspace) (4) Configuring Rsbuild or Rslib bundling (dev, build, Storybook) (5) Configuring Stylelint, Browserslist, or monorepo (Turborepo) vs polyrepo strategies (6) Extending or customizing shared configs, troubleshooting ESM/ESNext constraints

2026-03-018

name	workleap-telemetry
description	Guide for @workleap/telemetry, Workleap's unified telemetry connecting Honeycomb, LogRocket, and Mixpanel with automatic correlation IDs. Use this skill when: (1) Initializing wl-telemetry in a frontend application (2) Correlation values (Telemetry Id, Device Id) and cross-tool data correlation (3) Honeycomb tracing, OpenTelemetry spans, and performance monitoring (4) LogRocket session replay, user identification, and privacy controls (5) Mixpanel analytics, event tracking, and cross-product tracking (6) Configuring wl-telemetry diagnostic loggers (LogRocketLogger) (7) Storybook/test setup with Noop telemetry clients (8) Reviewing or troubleshooting telemetry instrumentation
metadata	{"version":3.2}

Workleap Telemetry (wl-telemetry)

@workleap/telemetry is an umbrella package that integrates Honeycomb, LogRocket, and Mixpanel with consistent correlation IDs for unified debugging and analysis.

Critical Rules

Use umbrella package — Always use @workleap/telemetry, not standalone packages
Do not invent APIs — Only use documented APIs from references
Correlation is automatic — Never manually set Telemetry Id or Device Id; never create your own TelemetryContext instances
Noop for non-production — Use NoopTelemetryClient in Storybook/tests
Privacy matters — Never log PII to LogRocket; use data-public/data-private attributes
productFamily is required — initializeTelemetry requires "wlp" or "sg" as the first argument

Reference Guide

For detailed documentation beyond the rules above, consult:

references/api.md — Initialization options, TelemetryClient properties, Honeycomb/LogRocket/Mixpanel client APIs, React hooks, Noop clients, LogRocketLogger
references/integrations.md — Platform-specific configuration, Honeycomb tracing patterns, LogRocket privacy and user identification, Mixpanel event tracking, cross-platform correlation workflows
references/examples.md — Full application setup, Storybook/test configuration, user identification, custom Honeycomb traces, Mixpanel tracking patterns, logging configuration, troubleshooting