Critique UI layouts and provide specific, actionable fixes. Use when something feels off but you can't articulate why, before finalizing designs, or after adding new components. Outputs diagnosis of visual hierarchy, spacing, alignment, color balance issues with exact CSS/Tailwind fixes.
View session and context metrics for dogfooding optimization. Use when analyzing whether knowledge injection is helping, understanding context usage patterns, or optimizing the knowledge system.
This skill should be used when the user asks to "debug this issue", "find the root cause", "investigate the bug", "systematic debugging", "troubleshoot the problem", or needs help with systematic problem-solving and root cause analysis.
Audit web applications for performance issues and optimize for speed, especially on Cloudflare Workers edge runtime. Use when diagnosing slow pages, optimizing load times, reducing bundle size, improving Core Web Vitals, or optimizing for edge deployment. Triggers on requests like "audit performance", "optimize speed", "improve load time", "reduce bundle size", "Core Web Vitals", or "edge optimization".
Go language consultant providing guidance on best practices, testing with testify, concurrency patterns, error handling, and technology stack recommendations. Use when answering Go questions, reviewing Go code, or advising on Go implementation approaches.
Four-phase systematic debugging methodology for efficient problem resolution. Use when investigating bugs, errors, or unexpected behavior.
Find and fix performance bottlenecks in ANY language or framework
Performs in-depth codebase exploration at the start of a coding session. Builds comprehensive understanding of project structure, architecture, key components, and patterns. Use when starting a new session, when asked to understand or explore the codebase, when asked "what does this project do", when exploring unfamiliar code, or when the user asks about project structure or architecture.
Generate comprehensive health report for Leavn codebase - metrics, technical debt, bugs found/fixed, recommendations for next session
Performance and scalability guidelines for RawDrive. Use when optimizing code, implementing features at scale, or reviewing performance-critical code.
Performance testing specialist for load testing, stress testing, and performance optimization across applications and infrastructure
Automatically analyze test coverage when user asks which code is tested, mentions coverage gaps, or shows code asking about testing. Identifies untested code paths and suggests test additions. Invoke when user asks "what's not tested?", "coverage", "untested code", or "which tests are missing?".
Guidelines and best practices for reviewing React and Next.js code within the scoreboard project.
Comprehensive systematic debugging agent for hunting down complex bugs, root causes, and error propagation across full stack (frontend, backend, APIs, databases). Use when diagnosing errors, troubleshooting issues, analyzing stack traces, investigating bugs, examining logs, debugging performance problems, or tracking down error causes. Also use when users mention debugging, errors, bugs, failures, crashes, exceptions, or unexpected behavior.
Analyze web interfaces for UX issues, accessibility compliance (WCAG 2.1), color contrast, typography hierarchy, responsive design, and Core Web Vitals. Returns actionable improvements with code examples.
Use for systematic debugging and root cause analysis with Codex. Triggers on "codex debug", "codex root cause", "have codex investigate this bug", "codex find the issue".
Patterns and methods for researching a codebase to understand bug context. Use when investigating how code works, finding related files, or understanding code flow.
Use for project architecture, codebase structure, dependencies, components, tech stack. Explicit triggers: @map, map-ask, explore map, -map. Pre-computed maps faster than Glob for structural queries.
Systematically debug and fix bugs through triage, reproduction, root cause analysis, and verified fixes. Use when asked to fix a bug, debug an issue, investigate a problem, or resolve an error.
Deep analysis of project codebases - LOC, dependencies, architecture, git history. Generates comprehensive project profiles for documentation and portfolio. Triggers: "analyze project", "project stats", "codebase analysis", "/analyze"
Systematic bug debugging methodology, root cause analysis, and fix verification. Use when investigating and fixing bugs. (project)
Deep research skill for analyzing codebases systematically. Use when comprehensive codebase understanding is needed, particularly for new projects or when documenting architecture. This skill should be used when users request deep analysis, architecture documentation, or systematic codebase research starting from root-level directories.
