What problem does it solve?
This Skill helps maintain a Flutter monitoring workspace where documentation, event models, SDK runtime collection, native enhancements, and Workbench consumption stay consistent instead of drifting into separate incompatible schemas.
Core Features & Use Cases
- Change-ordered workflow: Updates move from docs to core, then SDK or native, and finally to platform views so schema and behavior changes remain aligned.
- Workspace boundary enforcement: Keeps a single canonical EventEnvelope model for session, trace, span, breadcrumb, context, resource, attributes, and payload across all components.
- Operational guidance: Useful when analyzing or modifying monitoring features such as startup, page, network, behavior, lifecycle, jank, memory, native signals, self-monitoring, and Workbench presentation.
- Use case: A developer changes a field path or signal meaning and uses this Skill to determine which documents, core constants, SDK collectors, and Workbench views must be updated in order.
Quick Start
Ask me to inspect the Flutter Monitor repository, identify any valid skill unit rooted by SKILL.md, and generate its metadata from the repository’s frontmatter and workflow instructions.
