Agent skill · software engineering · aiskillstore
rn-observability
Logging, error messages, and debugging patterns for React Native. Use when adding logging, designing error messages, debugging production issues, or improving code observability.
Why this skill is useful
Provides structured logging patterns and error message templates specific to React Native that enhance observability and debugging capabilities.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
React Native Observability Problem Statement Silent failures are debugging nightmares. Code that returns early without logging, error messages that lack context, and missing observability make production issues impossible to diagnose. Write code as if you'll debug it at 3am with only logs. --- Pattern: No Silent Early Returns Problem: Early returns without logging create invisible failure paths. Example (from retake bug): Rule: Every early return should log why it's returning, with enough context to diagnose. --- Pattern: Error Message Design Problem: Error messages that don't help diagnose the issue. Error message template: What to include: Element Why --------- ----- Function/location Where the error occurred What failed The specific condition that wasn't met Relevant state Values that help diagnose Possible cause Your best guess for the fix --- Pattern: Structured Logging Problem: Console.log statements that are hard to parse and search. Logging levels: Level Use for ------- --------- error Exceptions, failures that need immediate attention warn Unexpected conditions that didn't fail but might indicate problems info Important business events (user actions, flow milestones) debug Detailed diagnostic info (state dumps, timing) Wrapper for consistent logging: --- Pattern: Sensitive Data Handling Problem: Logging sensitive data to console or crash reporting. --- Pattern: Flow Tracing Problem: Multi-step operations where it's unclear how far execution got. Benefits: Can search logs by flowId to see entire flow Know exactly which step failed Timing visible via timestamps --- Pattern: State Snapshots for Debugging Problem: Need to understand state at specific points in complex flows. --- Pattern: Assertion Helpers Problem: Conditions that "should never happen" but need visibility when they do. --- Pattern: Production Error Reporting Problem: Errors in production with no visibility. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/rn-observability