Depuració
Detecció i correcció de problemes i anàlisi d’errors
skill-debug
nyldn
Systematic debugging workflow. Use when: AUTOMATICALLY ACTIVATE when encountering bugs or failures:. "fix this bug" or "debug Y" or "troubleshoot X". "why is X failing" or "why isn't X working" or "why doesn't X work"
skill-issues
nyldn
Track and manage project issues across sessions. Use when: AUTOMATICALLY ACTIVATE when user mentions:. "issue" or "issues" or "problem". "track this" or "remember this blocker"
skill-decision-support
nyldn
Present options with trade-offs for informed decision-making. Use when: AUTOMATICALLY ACTIVATE when user requests options or choices:. "fix or provide options" or "fix them or provide me options". "give me options" or "what are my options"
skill-visual-feedback
nyldn
Process screenshot-based UI/UX feedback to fix visual issues. Use when: AUTOMATICALLY ACTIVATE when user provides visual feedback:. "[Image X] The /settings should be Y". "[Image X] these button styles need to be fixed"
skill-tdd
nyldn
Test-driven development workflow. Use when: Use when implementing any feature, bugfix, or behavior change.. Auto-invoke when user says "implement X", "add feature Y", "fix bug Z".
skill-iterative-loop
nyldn
Execute tasks in loops with conditions until goals are met. Use when: AUTOMATICALLY ACTIVATE when user requests iterative execution:. "loop X times" or "loop around N times". "loop around 5 times auditing, enhancing, testing"
dyad:pr-fix
dyad-sh
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
single-or-array-pattern
EpicenterHQ
Pattern for functions that accept either a single item or an array. Use when creating CRUD operations, batch processing APIs, or factory functions that should flexibly handle one or many inputs.
Observability Testing Patterns
proffesor-for-testing
Agentic QE Fleet is an open-source AI-powered quality engineering platform designed for use with Claude Code, featuring specialized agents and skills to support testing activities for a product at any stage of the SDLC. Free to use, fork, build, and contribute. Based on the Agentic QE Framework created by Dragan Spiridonov.
positron-issue-creator
posit-dev
This skill should be used when drafting GitHub issues for the Positron repository. It provides workflows for searching duplicates, selecting appropriate labels, gathering complete context through questioning, and writing terse, fluff-free issues that precisely describe what is needed or wrong. The skill prepares issues for manual submission by the user. Use this skill when the user asks to draft or prepare an issue for Positron.
amiberry-jit-fix
BlitterStudio
ARM64 JIT compiler fixes for Amiberry (GitHub issue #1766). This skill captures the complete technical knowledge from 20+ debugging sessions that identified and fixed: (a) a page 0 DMA corruption crash during A1200 Kickstart boot, (b) visual corruption (black gadgets, garbled text) caused by incorrect inter-block flag optimization, (c) SIGSEGV crashes on unmapped natmem gaps (e.g., 0x00F10000) in complex configs with hardfiles/RTG, and (d) BSR.L/Bcc.L backward branch crashes from 32-bit displacement zero-extension on 64-bit platforms. Use this skill when working on: (1) the JIT_DEBUG_MEM_CORRUPTION code in compemu_support_arm.cpp or newcpu.cpp, (2) the page 0 DMA guard mechanism (mprotect/SIGSEGV/BRK single-step), (3) any ARM64 JIT register width bugs (64-bit vs 32-bit instruction selection), (4) any crash or exception cascade during A1200 boot with JIT enabled, (5) 68040 JIT mode issues on ARM64, (6) the inter-block flag optimization bug and its fix (dont_care_flags at block boundaries), (7) natmem gap crashes and the commit_natmem_gaps() fix in amiberry_mem.cpp. MANDATORY TRIGGERS: JIT crash, page 0, DMA guard, vec2, exception vector corruption, blitter DMA, mprotect, SIGSEGV handler, BRK single-step, ARM64 JIT, Kickstart boot, visual corruption, black gadgets, garbled ROM version, compemu_support_arm, JIT_DEBUG_MEM_CORRUPTION, inter-block flag, dont_care_flags, 68040 JIT, natmem gap, unmapped region, commit_natmem_gaps, 0x00F10000, canbang, PROT_NONE, BSR, Bcc, branch displacement, sign extension, comp_pc_p, comp_get_ilong, 64-bit pointer, zero-extend, backward branch, gencomp_arm.
better-result-adopt
dmmulroy
Migrate codebase from try/catch or Promise-based error handling to better-result. Use when adopting Result types, converting thrown exceptions to typed errors, or refactoring existing error handling to railway-oriented programming.
sounds-on-the-web
raphaelsalaja
Audit UI code for audio feedback best practices. Use when reviewing sound implementation, checking audio UX decisions, or auditing accessibility. Outputs file:line findings.
principle-minimize-reader-load
cursor
"Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope."
principle-encode-lessons-in-structure
cursor
"Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text."
tdd
cursor
"Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested."
principle-fix-root-causes
cursor
"Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes."
principle-never-block-on-the-human
cursor
"Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions."
physics-3d-collision
Unity-Technologies
3D PhysX collision and trigger diagnostics for MonoBehaviour-based Unity projects. Primary scope: OnCollisionEnter / OnTriggerEnter not firing, objects passing through each other, Physics.Raycast missing, ragdoll explosion, AddForce stops working after settling, MeshCollider rules, and similar 3D PhysX symptoms. Adjacent topics (2D physics, OTS / Unity Physics package): provides a brief best-effort answer with a scope disclaimer and a documentation link, rather than refusing outright. When dedicated specialist skills (physics-2d, physics-dots) are installed, those should handle their respective domains and this skill defers to them.
ponytail
diegosouzapw
"External agent skill (MIT, github.com/DietrichGebert/ponytail). Forces the laziest solution that actually works: question whether the task needs to exist at all (YAGNI), reuse what is already in the codebase, reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Climb the ladder on every coding task — writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Supports intensity levels: lite, full (default), ultra. Never cut validation, error handling, security, or accessibility."
stac-troubleshooter
StacDev
Diagnose Stac build, deploy, rendering, caching, and navigation issues using repeatable checks. Use when users report stac build finding no screens, deploy mismatches, runtime unknown widget/action errors, cache staleness, or migration regressions.
Testing Patterns
Dicklesworthstone
Common testing patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
recall
cursor
"Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work."
debug
whawkinsiv
"Use this skill when features break, users report errors, deployments fail, or tests don't pass. Guides systematic debugging: reproducing bugs, gathering diagnostic info, reading error messages, and working with AI tools to fix issues efficiently."