Logging And Observability

Read this file when the change requires runtime observability to validate correctness. This skill ensures you have enough runtime visibility to prove your changes work.

Changes That Typically Need Observability

• Data writes or sync operations.
• State transitions.
• User-facing flows.
• Silently failing error handling paths.
• Integration points between layers.

When Adding Logging

• Use the project's existing logging approach.
• If no logging approach exists, flag this in the plan.
• Log the action, relevant identifiers, and outcome.
• Include enough context to trace a problem without a debugger.
• Do not add logging for trivial operations.
• Do not add logging that would expose sensitive user data.
• Do not log full data payloads unless explicitly needed.
• If a change affects writes, sync behaviour, state transitions, or reactive screens, decide whether temporary diagnostic logging is needed to verify the runtime path.
• Prefer logs or probes that confirm which code path executed.