Make every incident searchable by one ID
Ensure logs, traces, and error reports share correlation IDs so debugging doesn't require "grep archaeology." Adds a baseline instrumentation and logging contract.
Create a skill called "Trace/Log Correlation Baseline". Inputs: - Service architecture (monolith vs microservices) - Current logging/tracing tools Output: - A correlation contract and propagation plan - Logging middleware plan (structured fields) - Verification steps (smoke tests and expected outputs)
This recipe standardizes correlation: every request/job emits an ID, and that ID appears in
logs, traces, and errors consistently.
Find missing spans and broken propagation in microservice flows
Debug microservices by enforcing end-to-end correlation (trace IDs, request IDs) and systematically locating propagation breaks or sampling gaps.
Catch perf regressions before users do
Introduce performance budgets and regression detection using benchmarks and/or production telemetry so regressions become reviewable events, not customer complaints.
Auto-generate proxies the moment footage lands
Choppy playback, laggy scrubbing, and unusable timelines — even on strong machines — often comes down to editing long-GOP or heavy codecs at high resolution without proxies. This recipe generates proxies automatically whenever new camera originals appear, so every project starts edit-ready instead of debug-ready.
Keep media caches from eating your SSD and slowing your apps
Media cache and disk caches balloon over time, causing storage emergencies and performance regressions. This recipe turns cache cleanup from a panic action into a controlled, scheduled maintenance job — for Adobe Premiere Pro, After Effects, and similar tools.