Desenvolvimento

Domine técnicas sistemáticas de depuração, ferramentas de perfil e análise de causa raiz para rastrear bugs eficientemente em qualquer base de código ou pilha de tecnologia. Use ao investigar bugs, problemas de desempenho ou comportamento inesperado.

Gera um roast divertido e compartilhável de desenvolvedores, baseado em sua presença online pública (GitHub, npm, etc.). Use esta skill quando o usuário pedir para roast, torrar, zoar um perfil de desenvolvedor, ou mencionar um nome de usuário do GitHub em tom de brincadeira.

Propose-then-critique structural design loop → draft to `designs/<slug>.md`. Distinct from socratic (which sharpens vague intent). Use when user wants to design a structural change, weigh tradeoffs between named alternatives, propose an architecture, or shape a subsystem before implementation. Triggers: "/sdd:design", "design the X", "shape the X subsystem", "tradeoffs between A and B", "how shoul

Radical simplifier of explanations. Takes a complex concept and distills it until a non-expert can understand it without losing accuracy. Default test: "would a curious 12-year-old follow this?" Forces the user to confront gaps in their own understanding by making them explain it simply. Triggers on: "Feynman", "explain this simply", "help me explain this to non-technical stakeholders", "I need to

When contributing to public or open-source repositories where AI attribution should be hidden. Use when the user says "stealth mode," "undercover," "no AI attribution," "hide AI," "contribute anonymously," "clean commits," "no co-authored-by," or when working on repos where AI involvement should not be visible. Strips all AI fingerprints from commits, PRs, code comments, and generated content.

Transitional standalone visual regression guard using before/after screenshot comparison. Two modes: SIT (compare staging vs local dev) or Local (compare git-stashed base vs current changes). No long-lived baselines — captures fresh screenshots each run and deletes after comparison. Config-driven from workspace-config.yaml. Use when: "跑 visual regression", "檢查畫面", "頁面有沒有壞", "visual test", "screens

Use when explaining a technical concept and adapting depth, pacing, and examples to the learner's readiness.

Use when writing libGDX Java/Kotlin code involving file I/O (FileHandle, Gdx.files, FileType) or persistent storage (Preferences). Use when debugging files not found, write failures on Android/iOS, wrong file paths across platforms, or preferences not persisting.

Baixa vídeos e áudios do Bilibili, suportando downloads individuais ou em lote de todos os vídeos de um UP. Utilize quando o usuário solicitar o download de conteúdo do Bilibili ou fornecer um link.

When the user wants to review past decisions, understand why something was built a certain way, audit decision quality, or learn from past reasoning. Use when the user says "why did we," "look back," "thinkback," "decision review," "was that the right call," "what were we thinking," "review our decisions," "decision audit," "trace back," "replay thinking," or when revisiting old code and needing t

Use when writing libGDX Java/Kotlin code involving ShaderProgram, GLSL shaders, custom SpriteBatch shaders, Mesh rendering, or uniform/attribute setup. Use when debugging black screen, white screen, shader compilation errors, or "works on desktop but broken on phone" issues.

Flips constraints and beliefs to expose false walls and test plan robustness against inverted worldviews.