svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should b...
发现 research debugging 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should b...
A workflow for profiling and optimizing JAX-based code performance. Use this when the goal is to improve speed or OPS (Operations Per Second), involving profiling, hypothesis formation, and benchmarking.
Instructions for writing and efficiently storing data in TraceMem.
System maintenance, memory queries, and pattern analysis. USE WHEN user mentions system, memory, patterns, history, past conversations, what did I, or meta-level system questions.
Auditing memory traces and debugging.
Dogfooding discovery agent — establish human-approved project baseline from public docs without code inspection
This skill should be used when the user asks to "test for directory traversal", "exploit path traversal vulnerabilities", "read arbitrary files through web applications", "find LFI vulnerabilities", or "access...
Instructions for reading data from TraceMem memory.
系统化调试技能,在遇到任何 Bug、测试失败或意外行为时使用。在提出修复方案之前,必须先进行根因分析。
Reference knowledge for hooks: events (PreToolUse/PostToolUse/Stop), security patterns, exit codes, configuration types. Use when understanding hooks. No execution logic.
Code review, PR analysis, and quality feedback. USE WHEN user mentions review, PR, pull request, code quality, best practices, feedback, suggestions, improvements, code smell, or asks to look at code for issues...
TypeScript strictest patterns, type guards, optional properties (exactOptionalPropertyTypes), Drizzle query safety, null checks. Use when fixing type errors, implementing complex types, or when user mentions Ty...
Document and explain existing codebases without critique or recommendations. Use when the user asks to research, investigate, or "look into" codebases (e.g., "research", "research this", "research the codebase...
Debugging, error diagnosis, and problem resolution. USE WHEN user mentions bugs, errors, crashes, exceptions, not working, broken, debugging, fix, issue, problem, stack trace, logs, or asks why something isn't...
Improving and debugging skills through metacognitive analysis. Use when needing to analyzes skill execution patterns, identifies flaws in instructions, and refines skill content to improve performance.
Provide educational insights and explanations about code. Use when the user asks questions like "how does this work", "explain", "why", "what does this do", "help me understand", or when exploring/learning abou...
Inspects what context is available
Performance tuning, profiling, and optimization. USE WHEN user mentions slow, performance, optimize, speed, latency, throughput, memory, CPU, bottleneck, profiling, caching, or asks why something is slow or how...
Review code for best practices and potential issues. Use when reviewing code, checking PRs, or analyzing code quality.
Audits code quality and patterns
Structural code search and refactoring via ast-grep (optional)
Log exploration and analysis using Quickwit search engine. Incident investigation, error pattern analysis, and observability workflows. Three index discovery modes for different performance and convenience trad...
Systematic debugging: reproduce, isolate, form hypotheses, instrument, fix, and add regression tests. Use when troubleshooting errors, failing tests, or unexpected behavior.
Auto-extract patterns from development sessions
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。