dev-execution
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....
发现 research debugging 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
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....
Token-efficient codebase navigation through intelligent symbol loading and querying. Use this skill when implementing new features (find existing patterns), exploring codebase structure, searching for component...
Testing UI and automating browsers via Chrome DevTools MCP. Use when taking screenshots, checking console errors, testing UI interactions, or verifying visual changes.
Capture screenshots of aiandi.dev for visual verification. Puppeteer-based, outputs to /tmp. Foundation for the design-loop skill.
Patterns and methods for researching a codebase to understand bug context. Use when investigating how code works, finding related files, or understanding code flow.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Systematically trace bugs backward through call stack to find original trigger
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.
Query the code graph for callers, dependencies, and blast radius. Use when you need to understand code relationships, find what calls a function, determine impact of changes, or explore the codebase structure.
Security audit for vulnerabilities, compliance issues, and sensitive data exposure. Use before production deployments or when reviewing security-sensitive code.
Clean exit with session context capture. Writes detailed resume log to docs/sessions/, updates CLAUDE.md with pointer. Use when ending a session.
Patterns for debugging and understanding the root cause of code problems
Performance optimization, caching strategies, API integration testing, load testing, and production deployment best practices for Cloudflare Workers.
Comprehensive error handling, structured logging patterns, API error response standards, and debugging strategies for Cloudflare Workers applications.
Use this skill when performing QA reviews of the EVOLEA website (Astro frontend at localhost:4321), Admin Dashboard V2 (localhost:5175), or production sites (planted.com, admin.planted.com). Orchestrates visual...
Implement, refactor, or review worker-based multithreading in TypeScript/JavaScript apps (browser or Node). Use when offloading CPU-heavy loops to Web Workers, setting up a worker pool, moving data across threa...
A robust troubleshooting framework. Use this skill anytime the user reports something isn't working, is buggy, or is throwing errors.
React performance patterns for this D3+SVG visualization project. Apply when writing React components, hooks, state management, or reviewing code for performance issues.
Patterns frontend Next.js/React/shadcn/ui, complète DEV_AGENT avec best practices frontend
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 encountering bugs, test failures, or unexpected behavior. Hypothesis-driven debugging.
Use when debugging frontend issues in the browser. Covers DevTools usage, network debugging, performance profiling, and console patterns.
Intelligent work tracking. Automatically classifies issues, gathers codebase context, and creates well-formed Linear tickets. Triggers - linear, issue, track, bug, todo, fix, question, debt.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。