发现 development debugging 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
Reviews panel visual appeal and layout quality for LCDPossible LCD displays. Use when: validating panel layout, checking visual quality, reviewing panel design, ensuring style compliance, auditing panel appeara...
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexp...
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or es...
Reviews code for security, performance, bugs, and architecture violations. MUST use proactively before committing changes and after implementing new features or fixing bugs. Also triggers on "review", "レビュー...
Guide for diagnosing lsp errors. This skill should be used when users wants to debug a lsp/diagnostic errors, warnings, or exceptions and get clear explanations and potential solutions. "Why am i getting thi...
Perform a comprehensive, cognitive static analysis of a specific feature or logic flow to identify logical flaws, missing connections, or design inconsistencies.
Gather threat intelligence using Shodan. Use for tracking threat actors, identifying attack infrastructure, and monitoring emerging threats. Triggers on requests for "threat intelligence", "track attackers", "C...
Identify vulnerabilities in internet-facing systems using Shodan. Use for vulnerability assessment, CVE discovery, and security auditing. Triggers on requests for "vulnerability scan", "find vulns", "CVE check"...
Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding. Integrates with artifact-tracking and meatycapture-capture....
Use when automating browsers with Playwright/Puppeteer, testing Chrome extensions, using Chrome DevTools Protocol (CDP), handling dynamic content/SPAs, or debugging automation issues
Review architecture decisions and code changes against documented architecture principles. Use this skill before implementing new features or refactoring existing code to ensure compliance with layer boundaries...
Expert Performance Monitoring and PWA optimization.
Use Playwright MCP to check UI styles and usability. Automatically used for requests like "check UI", "verify appearance", "take screenshot", "UI review", "screenshot analysis".
Analyzes Ecto queries for N+1 problems, missing preloads, and performance issues.
Performance profiling and optimization for Elixir/BEAM applications
Telemetry, metrics, tracing, and observability for Elixir/BEAM applications
Query dashboards/logs/alerts to support incident analysis and regressions. Use when troubleshooting involves observability, incidents, latency, error rates.
Use browser automation MCP (Playwright/Browser/Browser-Use) to validate UI flows, capture screenshots, and reproduce issues. Use when visual verification or web flow testing is needed.
Perform root-cause analysis for bugs/errors/regressions using logs, repro steps, and hypothesis testing. Use when the user reports “nie działa”, stack traces, failing tests, or regressions.
Systematic bug investigation and root cause analysis
Provides critical feedback and alternative architectural perspectives on code changes. Use when you want to explore different ways to implement a feature or find potential flaws in the current plan.
Optimizes React Native Expo applications for speed, responsiveness, and battery efficiency. Use when fixing lag, optimizing lists, or reducing bundle size.
Test local web applications using Playwright for UI verification, debugging, screenshot capture, and end-to-end testing. Use when testing web apps, verifying UI behavior, or capturing screenshots of running app...
Test local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。