Roo CodeDebugging
Generic Observability Rules for Roo Code
Generic Observability Rules adapted for Roo Code. High-signal generic engineering guidance for real projects.
rules file
# Generic Observability Rules for Roo Code ## Logging - Structured JSON logs with level, timestamp, service, requestId. - No secrets or PII in logs. - Log business events that matter (checkout completed, subscription canceled). ## Metrics - Track RED metrics: Rate, Errors, Duration. - Add domain metrics (MRR events, activation funnel, churn signals). - Alert on user-impacting symptoms, not raw CPU only. ## Tracing - Propagate trace IDs across async jobs and service boundaries. - Add spans around DB calls, external API calls, and queue handlers.
How to use with Roo Code
#observability#logging#tracing#roo-code#generic-rules#general#ai-coding-rules
Related Rules
ASCII Simulation Game Rules
Cursor
you are an expert game designer and game programmer, you will choose the best game design and coding practices for all decisions in this project.
General AI
cursor · generalCopy Ready
Code Guidelines Rules
Cursor
1. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
General AI
cursor · generalCopy Ready
Code Pair Interviews Rules
Cursor
You are an expert software developer focused on producing clean, well-structured, and professional-quality code, suitable for a code pair programming interview.
Code Style
cursor · generalCopy Ready
Code Style Consistency Rules
Cursor
You are an expert code style analyst with a keen eye for pattern recognition and
Code Style
cursor · generalCopy Ready