fullstory-component-wellbeing

Standardize observability markers across React, Vue, Angular, Svelte, and React Native.

11|2|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-component-wellbeing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullstory-component-wellbeing
Source: https://github.com/fullstorydev/fs-skills/tree/main/framework/fullstory-component-wellbeing
Command: npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-component-wellbeing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-framework frontend wellbeing monitoring is difficult due to inconsistent observability signals across React, Vue, Angular, Svelte, and React Native. This skill provides a unified approach to surface component health, rendering stability, and performance issues to Fullstory, enabling faster diagnosis and healthier user experiences.

Core Features & Use Cases

  • Universal semantic attributes (data-component, data-state, data-testid) to anchor components in dashboards and searches across all frameworks.
  • Framework-specific error boundary patterns: capture and report errors with component context via FS('setVars') and FS('event').
  • Hydration and render health monitoring: detect hydration failures and long renders to triage performance regressions.
  • Compatibility with multiple ecosystems: React, Vue, Angular, Svelte, React Native recipes and examples.

Quick Start

  1. Add data-component attributes to key UI components and toggle data-state between loading, ready, and error.
  2. Implement framework-specific error boundaries and log health events using FS('setVars') and FS('event').
  3. Reference the Examples in SKILL.md to extend to hydration checks and long-run performance monitoring.

Frequently Asked Questions about fullstory-component-wellbeing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor frontend wellbeing across multiple frameworks?

Cross-framework frontend wellbeing monitoring standardizes observability markers across React, Vue, Angular, Svelte, and React Native. It detects errors, slow renders, and hydration issues, surfacing component health and stability signals to production dashboards and analytics pipelines.

What semantic attributes should I use to track component health in production?

To track component health, apply universal semantic attributes like data-component, data-state, and data-testid to key UI elements. These standardized markers anchor components in dashboards and searches, allowing you to toggle states like loading, ready, and error across all frameworks.

How do I report hydration failures and rendering errors to Fullstory?

You can report hydration failures and rendering errors by implementing framework-specific error boundaries. Capture component context and log health events directly to Fullstory using the FS('setVars') and FS('event') reporting methods.

Can I use the same observability patterns for React Native and Svelte?

Yes, this approach applies to UI apps across frameworks including React Native and Svelte. It provides compatible recipes and examples that standardize error-handling patterns and semantic attributes for consistent observability.

Why are inconsistent observability signals a problem for frontend performance monitoring?

Inconsistent observability signals across frameworks make cross-framework frontend monitoring difficult. Standardizing semantic attributes and error-handling patterns solves this by enabling unified component health tracking, which leads to faster diagnosis and healthier user experiences.

How do I detect slow renders and performance regressions in a cross-framework UI app?

To detect slow renders and performance regressions, implement health monitoring checks that track hydration and render health. By logging these stability signals via FS('event'), you can triage performance regressions directly in your analytics pipelines.