k8s-observability
VictoriaMetrics + Loki + Grafana. Light or full mode.
Découvrez les skills development debugging, comparez leurs dépôts et consultez leurs instructions.
VictoriaMetrics + Loki + Grafana. Light or full mode.
Diagnose compile errors and runtime issues using logs and headless runs
Use when the root cause is unclear. Trace the failure back through the call stack and isolate the first bad state.
This skill should be used when the user asks to "detect project type", "analyze this project", "create project profile", "what tech stack is this", "scan project structure", "what database does this use", or wh...
This skill should be used when the user asks to "optimize performance", "improve caching", "speed up my app", "reduce latency", "configure Argo", "setup tiered caching", or is working on performance improvement...
This skill should be used when the user asks to "debug a Worker", "view logs", "check analytics", "monitor performance", "trace errors", "setup logging", "wrangler tail", "check metrics", or needs to troublesho...
OpenAI Codex CLIを使用したコードレビュー、分析、コードベースへの質問を実行する。使用場面: (1) コードレビュー依頼時、(2) コードベース全体の分析、(3) 実装に関する質問、(4) バグの調査、(5) リファクタリング提案、(6...
Creates, analyzes, updates, and improves Claude Code hooks including configuration, scripts, and security validation. Use when user asks how hooks work, explaining hook concepts, understanding hook types and ev...
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
Use when generate test coverage, or when asked "generate test coverage", "generate coverage", "find coverage". Provide how to get test coverage of specific component.
This skill shoudl be used when the user ask to "behaviors", "specification", "read implementation", "analyze component", "振る舞いを分析", "振る舞いを理解". Analyze component(module, package, class, function) b...
Use when optimizing code for performance, reducing bundle size, improving load times, or fixing performance bottlenecks. Emphasizes measurement-driven optimization.
Go performance optimization guidelines for profiling, allocation, GC tuning, concurrency, PGO, and I/O. This skill should be used when writing, reviewing, or optimizing Go code for performance. Triggers on task...
Expert-level Rust performance optimization guidelines for build profiles, allocation, synchronization, async/await, and I/O. This skill should be used when writing, reviewing, or optimizing Rust code for perfor...
TypeScript performance optimization guidelines for build times, type-checking, declaration emit, and editor responsiveness. This skill should be used when writing, reviewing, or optimizing TypeScript code and t...
Analytics & Product Insight Specialist that tracks what users actually do. Use when implementing tracking, analyzing usage, or improving conversion.
QA & Edge-Case Destroyer that kills weird bugs before users see them. Use when testing, reviewing edge cases, or hunting for bugs.
Debug issues in TireOps. Use when encountering errors, bugs, or unexpected behavior.
Performance & React Optimization Engineer that makes the app feel instant. Use when optimizing load times, fixing re-renders, or reviewing component efficiency.
Provides context about the TireOps codebase architecture, database schema, and project structure. Use when starting work, asking about how things work, or needing to understand the system.
Codebase-specific context for AI agents using Upstash Redis. Indexes documentation and provides relevant context for queries. Perfect for Q&A about codebases.
Rigorous data investigation with hypotheses, YoY context, and audit trail.
Quick CI/CD failure diagnosis. Use when builds fail.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.