react-obs-demo Package Skill

Package: react-obs-demo Repository: epic-flowstate-community Path: examples/react-obs-demo Version: 1.0.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

FlowState React Obs Demo

Status: Active Purpose: Guide agents through the React observability demo. Scope: examples/react-obs-demo. Trigger: Need to run, update, debug, or teach the observability demo. Input: Local obs endpoint, Vite app, and demo scenario. Output: Demo behavior that intentionally exercises logs, errors, and browser global handlers.

Runtime Model

src/App.tsx renders buttons for:

• counter increment/decrement logs
• null/type/network/async/state/array errors
• debug/info/warn log events

src/observability.ts:

• posts errors to /api/errors
• posts logs to /api/logs
• sends X-API-Key and X-Project-ID
• installs error and unhandledrejection handlers
• generates a local session id

Change Checklist

1. Keep intentional error triggers obvious and isolated.
2. Update OBS_CONFIG when changing server URL, API key, or project id.
3. Preserve comments around missing session creation if the server still lacks that endpoint.
4. Prefer source-backed examples over generated Dojo feature lists.

Verification

yarn workspace react-obs-demo build

Run yarn workspace react-obs-demo dev only for interactive browser validation.

Created: 2026-06-29

Package Skill Inventory

react-obs-demo Skill Inventory

Review Gate

react-obs-demo Skills Review

Verdict: Pass with follow-ups.

Local skill covers demo purpose, telemetry helper behavior, intentional error buttons, server URL assumptions, and verification commands.

Verification

• ASCII and skill frontmatter checks passed.
• yarn workspace react-obs-demo build passed with the existing Vite CJS Node API deprecation warning.

Follow-Ups

• Rebuild generated .flowstate/dojo content from the reviewed local skill before publishing.
• Keep the hardcoded demo OBS URL/API key assumptions visible in docs because the demo is not a production SDK wrapper.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with examples/react-obs-demo/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.