flowstate-dojo-community-epicdm-flowstate-obs-browser

Use this skill when a task touches packages/obs-browser, imports @epicdm/flowstate-obs-browser, or needs to teach humans/agents how this package works.

Package identity:

• Package: @epicdm/flowstate-obs-browser
• Repository: epic-flowstate-community
• Version authority: package.json (1.0.7)
• Dojo course: flowstate-dojo-community-epicdm-flowstate-obs-browser

How to use the package:

• Purpose: Browser SDK for Epic Flow Observability Platform
• Start with package-local docs when present.
• Verify details against source and tests before changing behavior.
• Use the Dojo course lessons as the teaching path: setup, mental model, core workflow, integration, feature labs, maintenance.

Public surfaces discovered:

• ObservabilityConfig
• Breadcrumb
• ErrorEvent
• LogEvent
• ObservabilityClient
• FetchLogsParams
• FetchLogsResponse
• fetchLogs
• RpcRequestData
• RpcResponseData
• RpcError
• RpcHandler
• SendFn
• RpcClient
• createRpcClient
• ObsStreamConfig
• StreamFilter
• StreamConnectionState
• ObsStreamClient
• UseObsStreamOptions
• UseObsStreamResult
• useObsStream
• ConnectionState
• WebSocketClientConfig
• WebSocketClient

Composable feature skilllets:

• Connection State: use feature labs for workflow, source anchor, and regression risk.
• Create Rpc Client: use feature labs for workflow, source anchor, and regression risk.
• Fetch Logs: use feature labs for workflow, source anchor, and regression risk.
• Obs Stream Client: use feature labs for workflow, source anchor, and regression risk.
• Observability Client: use feature labs for workflow, source anchor, and regression risk.
• Use Obs Stream: use feature labs for workflow, source anchor, and regression risk.
• Web Socket Client: use feature labs for workflow, source anchor, and regression risk.

Agent operating rules:

• Treat package.json as the Dojo version authority.
• Do not turn feature inventory into user-facing lessons without workflow context.
• Update this Dojo package when package behavior, docs, examples, or feature inventory changes.
• Verify downstream packages when package use and connection metadata shows inbound dependencies or references.
• Never mark publish status passed without successful cloud publish and catalog lookup.

Use this Dojo skill with package human docs, package-local feature inventory, agent-skillset.md, and the generated course.json in this folder. Keep this manifest version aligned with package.json.