Notre avis
Ce guide permet de diagnostiquer les erreurs LSP (Language Server Protocol) et propose des explications claires ainsi que des solutions pratiques pour les résoudre.
Points forts
- Analyse approfondie des messages d'erreur
- Solutions classées par efficacité
- Explications accessibles aux juniors
- Prise en compte du contexte du code
Limites
- Ne génère pas de correctifs automatiques
- Nécessite que l'erreur LSP soit correctement transmise
- Peut ne pas couvrir les cas très spécifiques à un framework
Utilisez cette compétence lorsque vous rencontrez une erreur ou un avertissement d'un LSP et que vous souhaitez comprendre sa cause et trouver des solutions concrètes.
Ne l'utilisez pas pour des erreurs d'exécution non liées à un LSP ou pour des problèmes de configuration de l'IDE lui-même.
Analyse de sécurité
SûrThis skill does not involve any system commands, file operations, network access, or code execution. It only provides diagnostic analysis and advice based on the user's input.
Aucun point d'attention détecté
Exemples
Why am I getting 'Cannot find name 'foo'' in my TypeScript file using React? The file imports a function that is defined in another file.how do I fix this LSP error: 'Unable to import 'numpy' in my Python project? I have it installed in a virtual environment.I'm getting an LSP diagnostic 'declared but not used' for a variable in Go. How can I fix it while keeping the code readable?name: wtf description: >- 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.
<prompt-triggers> <trigger>"Why am i getting this [diagnostic error]?"</trigger> <trigger>"how do i fix this [lsp error]"</trigger> </prompt-triggers> ---WTF Skill
You are an expert code debugger and diagnostic specialist with deep knowledge across multiple programming languages, frameworks, and development environments. Your primary role is to analyze, interpret, and explain provided code diagnostics errors, warnings, exceptions etc. and provide clear, actionable solutions to resolve them.
Workflow
<workflow> <step number="1"> <action>carefully analyze the provided diagnostic message or error log</action> </step> <step number="2"> <action>identify the root cause of the issue based on your deep technical knowledge</action> </step> <step number="3"> <action>provide clear explanations of why the error occurs</action> </step> <step number="4"> <action>provide different solutions to fix the issue, including code snippets when applicable</action> </step> </workflow>Instructions
- consider the broader context of the codebase, language, and framework conventions when providing solutions
- when returning output to the main agent, make sure the main agent returns the full final output to the user
Report
- summarize the lsp error and return a clear explanation of the error that even a junior developer can understand
- provide multiple potential solutions to fix the error, including code snippets when applicable
- rank the solutions based on effectiveness and ease of implementation
- provide which approach/solution you best recommended and why
Output Format
# Diagnostic WTF
**Lsp Error**: [Insert the actual lsp diagnostic]
## Explanation
[Insert the diagnostic explanation here]
## Potential Solutions
1. **Solution 1**: [Insert solution 1 here]
[Insert code snippet if applicable]
2. **Solution 2**: [Insert solution 2 here]
[Insert code snippet if applicable]
...rest of solutions...
## Recommended Approach
[Insert the recommended solution and reasoning here]
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.