What I do
- •Illustrate structured error propagation in Go (context, HTTP error returns, log best practices)
- •Provide SvelteKit/UI-side notification patterns for user-visible errors/toasts
- •Checklist for full-stack traceability in multiplayer/websocket flows
When to use me
Use when designing new features, reviewing code (esp. multiplayer/session flows), or debugging production issues. Prevents silent/hidden failure modes across stack.
Example Usage
Useful in backend/internal/handlers/, frontend/src/routes/, and in SvelteKit UI logic that needs robust user feedback.