NeverSight

oQ's opinionated tooling and conventions for JavaScript/TypeScript projects. Based on Anthony Fu's style with personal customizations for UnoCSS, ESLint, pnpm catalog, and automated releases. Use when setting up new projects with these preferences.

Search Argentine legal databases (SAIJ, JUBA, CSJN, JUSCABA) for jurisprudence, legislation, case summaries, and doctrine using the `ley` CLI. Use when the user asks about Argentine law, court decisions, legal precedents, fallos, jurisprudencia, legislación,…

Manage TickTick tasks and projects for JMO. Use when the user asks to add, create, or capture a task or todo; list, show, or review pending tasks; complete or check off a task; update a task's priority, due date, notes, or tags; delete a task or list; create…

DEPRECATED: Use testing-best-practices instead. This skill has been retired.

Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.

Git workflow patterns for commits, branching, PRs, and history management across heterogeneous repositories. Use when creating commits, managing branches, opening pull requests, or rewriting history. Do not use for non-git implementation tasks or…

Sync a feature branch onto the latest origin base branch via git rebase, with safety rails, deliberate conflict resolution, and safe force-with-lease pushing.

Fetch latest from origin, prune remote-tracking refs, delete stale local branches and worktrees, and fast-forward important branches. Use when tidying up a worktree-based repo layout.

Continue NeverD x64 PE/COFF C-quality work: HighC structured C, LLVMC (llvm-to-C / `neverd decompile --llvm`) for obfuscated executables, Windows SEH/C++ EH readability, unnamed globals, local declarations, and Win64 ABI. Use when the user asks to improve x64…

Diagnose NeverD runtime tests that fail only or intermittently on GitHub Actions. Use for runner-specific crashes, signals, timeouts, or semantic mismatches; not ordinary local failures or workflow configuration errors.

Analyze anti-cheat architecture and detection tradeoffs across client, kernel, hypervisor, and backend layers. Use for system-level defense design; use narrower skills for PCIe DMA or Windows kernel details.

Maintain the awesome-game-security resource index. Use when adding or reclassifying links, organizing categories, or checking README format; use topic skills for security research itself.

Build compiler frontends, IR generation, optimization pipelines, or code generation with LLVM. Use for language and DSL compiler work; use narrower LLVM skills for isolated tooling or analysis tasks.

Analyze PCIe DMA threats, FPGA device behavior, and IOMMU defenses. Use for DMA-specific threat modeling or detection; use windows-kernel-security for kernel mechanisms without a DMA boundary.

Build dynamic instrumentation, runtime tracing, coverage, profiling, or monitoring with LLVM-related tooling. Use static-analysis when execution is not part of the analysis.

Research game-engine internals, source trees, SDK extraction, plugins, and engine-specific security surfaces. Use for Unreal, Unity, Source, Godot, or custom-engine structure rather than generic cheat techniques.

Design or debug machine-code lifting into LLVM IR for analysis and recompilation. Use when the lifting pipeline is the subject, not for general binary reverse engineering.

Review existing code or diffs for maintainability, design decay, and architecture risks, reporting actionable Symptom → Source → Consequence → Remedy findings. Do not use for writing code from scratch.

Build NeverC or other LLVM compilers across frontend, IR, optimization, code generation, ABI, and target support. Use when the compiler pipeline is the subject; use narrower LLVM skills for isolated tooling or analysis.

Reverse compiled, packed, obfuscated, virtualized, or anti-analysis targets for an authorized CTF challenge. Use while understanding the target; switch to an exploitation skill once the vulnerability is known.

Build dynamic instrumentation, runtime tracing, coverage, profiling, or monitoring with LLVM-related tooling. Use static-analysis when execution is not part of the analysis.

Diagnose NeverC runtime tests that fail only or intermittently in CI. Use for platform-specific crashes, signals, nondeterminism, or local/runner divergence; not ordinary build errors or workflow configuration failures.

Teach LLVM, Clang, and compiler concepts or assemble a learning path. Use for explanations and educational resources, not implementation work covered by a specialized LLVM skill.

Analyze or implement LLVM code-protection transformations such as control-flow flattening, string protection, and virtualization. Use when the obfuscation pass or pipeline is the subject.