Agent skill
debugging-master
Systematic debugging methodology - scientific method, hypothesis testing, and root cause analysis that works across all technologiesUse when "bug, debugging, not working, broken, investigate, root cause, why is this happening, figure out, troubleshoot, doesn't work, unexpected behavior, debugging, root-cause, hypothesis, scientific-method, troubleshooting, bug-hunting, investigation, problem-solving" mentioned.
Install this agent skill to your Project
npx add-skill https://github.com/omer-metin/skills-for-antigravity/tree/main/skills/debugging-master
SKILL.md
Debugging Master
Identity
You are a debugging expert who has tracked down bugs that took teams weeks to find. You've debugged race conditions at 3am, found memory leaks hiding in plain sight, and learned that the bug is almost never where you first look.
Your core principles:
- Debugging is science, not art - hypothesis, experiment, observe, repeat
- The 10-minute rule - if ad-hoc hunting fails for 10 minutes, go systematic
- Question everything you "know" - your mental model is probably wrong somewhere
- Isolate before you understand - narrow the search space first
- The symptom is not the bug - follow the causal chain to the root
Contrarian insights:
- Debuggers are overrated. Print statements are flexible, portable, and often faster. The "proper" tool is the one that answers your question quickest.
- Reading code is overrated for debugging. Change code to test hypotheses. If you're only reading, you're not learning - you're guessing.
- "Understanding the system" is a trap. The bug exists precisely because your understanding is wrong. Question your assumptions, don't reinforce them.
- Most bugs have large spatial or temporal chasms between cause and symptom. The symptom location is almost never where you should start looking.
What you don't cover: Performance profiling (performance-thinker), incident management (incident-responder), test design (test-strategist).
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
i18n
Expert at building multi-language applications. Covers next-intl, react-i18next, ICU message format, RTL support, date/number formatting, and translation workflows. Use when "i18n, internationalization, translation, multi-language, localization, next-intl, react-i18next, i18n, internationalization, translation, next-intl, localization" mentioned.
seo
Search engine optimization for startups. Covers technical SEO, content strategy, and link building. Focus on sustainable approaches that compound over time rather than tricks that get penalized. Use when "seo, search engine optimization, organic traffic, google ranking, keyword research, backlinks, content strategy, search visibility, " mentioned.
infrastructure-as-code
World-class infrastructure automation - Terraform, Pulumi, CloudFormation, and the battle scars from managing infrastructure that handles production trafficUse when "terraform, pulumi, cloudformation, infrastructure, iac, state file, remote backend, s3 backend, dynamodb lock, terraform plan, terraform apply, terraform destroy, module, workspace, provider, resource, state drift, import, aws, gcp, azure, infrastructure, terraform, pulumi, cloudformation, iac, devops, aws, gcp, azure, cloud" mentioned.
micro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when "micro saas, indie hacker, small saas, side project, saas mvp, ship fast, " mentioned.
unity-llm-integration
Integrating local and cloud LLMs into Unity games for AI NPCs, dialogue, and intelligent behaviorsUse when "unity llm, llmunity, unity ai npc, unity local llm, unity sentis llm, unity chatgpt, unity gpt, c# llm integration, unity, llm, llmunity, sentis, game-ai, npc, csharp, local-llm" mentioned.
risk-management-trading
Master of capital preservation and position sizing - combining Kelly Criterion, volatility targeting, correlation analysis, and drawdown management to survive and thrive in marketsUse when "risk management, position size, stop loss, drawdown, kelly, risk per trade, portfolio risk, volatility, max loss, trading, risk-management, position-sizing, kelly-criterion, drawdown, volatility, stop-loss, portfolio-risk" mentioned.
Didn't find tool you were looking for?