「trace」の検索結果

"Apply Kuhn's paradigm theory to analyze scientific progress through the cycle of normal science, anomalies, crisis, and revolution. Use this skill when the user needs to understand why a field resists change, trace paradigm shifts in a discipline, analyze incommensurability between competing frameworks, or when they ask 'why do scientists ignore contradictory evidence', 'how do scientific revolutions happen', or 'why can't proponents of different paradigms agree'.".

日本語の概要は準備中です。原文の説明を表示しています。

Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

日本語の概要は準備中です。原文の説明を表示しています。

Fix bugs and technical debt with minimal ceremony. Issue GitHub optional — provide one for traceability or work free-form. Replaces /issue-fix.

日本語の概要は準備中です。原文の説明を表示しています。

Performs a hallucination check on machine_readable sections by verifying every element traces back to the original legal text. Use this skill proactively when: machine_readable sections have been generated or modified, after /law-generate completes, when reviewing corpus YAML files for legal accuracy, or when user mentions "validate", "verify", or "hallucination check" for law YAML files. Activate automatically after editing machine_readable sections in corpus regulation YAML files.

日本語の概要は準備中です。原文の説明を表示しています。

Bouwt de audit- en workshop-producten waarmee juridische experts een machine-leesbare (regelrecht-YAML) vertaling van wet- en regelgeving valideren in een live sessie. Gebruik dit bij het voorbereiden van een expert-workshop of validatie-sessie over een dossier, het maken van een scope-/stelselanalyse, per-artikel audit-checklists, facilitator-materiaal, testcase-scenario's, of sessie-verslagen (intern + extern). Dossier-agnostisch; de regelrecht-methode (YAML, formules, untranslatables, source/override, legal_basis, engine-trace) is de vaste taal. Voor analytische desk-review van een corpus zonder live sessie (wetgevings-/stelselfouten, coverage, multi-agent review): zie de zusterskill regelrecht-stelselanalyse.

日本語の概要は準備中です。原文の説明を表示しています。

Detects weak reverse engineering and tampering protections in mobile apps (Android/iOS). Trigger on: root detection bypass, jailbreak detection bypass, Frida detection, debugger detection, anti-debugging, ptrace, sysctl, emulator detection, code obfuscation absent, debug symbols present, get-task-allow, ProGuard disabled, R8 disabled, string encryption, integrity check, file tampering, repackaging, dynamic instrumentation, runtime hook, Magisk hide, Magisk, frida-server, objection bypass, signing verification, apk resign. Covers MASVS-RESILIENCE-1/2/3/4.

日本語の概要は準備中です。原文の説明を表示しています。

Identify and exploit misconfigured Linux Capabilities. This skill covers how attackers escalate privileges to root without relying on SUID binaries or kernel exploits by abusing excessive capabilities like cap_dac_read_search, cap_sys_ptrace, or cap_setuid assigned to ordinary files.

日本語の概要は準備中です。原文の説明を表示しています。

Anti-debugging detection and bypass playbook. Use when reversing protected binaries that detect debuggers via ptrace, PEB flags, timing checks, or signal/exception handlers on Linux and Windows.

日本語の概要は準備中です。原文の説明を表示しています。

Triages an Aikido security findings CSV against a local codebase. For each finding, reads the flagged file, traces the code path, and verdicts it as KEEP OPEN or CLOSE with a specific reason. Outputs a reviewed CSV and a self-contained HTML evidence report. Run this at the end of a pentest when an Aikido CSV is available.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes CVE vulnerabilities in project dependencies with code path tracing and PoC generation for Burp Suite. Traces vulnerable code from user input to sink, assesses exploitability, and generates HTTP requests for testing.

日本語の概要は準備中です。原文の説明を表示しています。

Detects sandbox and analysis evasion techniques in a sample by scanning static strings, imports, and API traces for VM artifact checks, timing/sleep stalls, anti-debug calls, and environment fingerprinting. Activates for requests to detect sandbox evasion, find anti-VM or anti-debug checks, or explain why a sample did not detonate.

日本語の概要は準備中です。原文の説明を表示しています。

Debug or validate Pulp animations / transitions / scroll behavior using in-process motion fixtures and offline visual analysis. TRIGGER on phrases like "animation is wrong", "transition timing off", "fade too late", "card slides too far", "scroll jumps on restore", "scroll offset wrong on restore", "frame jump in the timeline", "easing looks wonky", "imported Figma motion doesn't match source", "settle time / overshoot / drift / monotonic", "what value does the knob reach at frame N", "record this animation so I can replay it", "this animation is expensive — which one and why", "reduced-motion broken", "scrub a captured fixture". Captures fixtures (.motion.jsonl), and ships assertion helpers (is_monotonic / settling_time_seconds / overshoot / start_delay_seconds / final_value / local_step_outlier_ratio) and the `scroll_geometry` trace for `ScrollView` content-offset / visible-rect / content-size observability. Off by default in prod.

日本語の概要は準備中です。原文の説明を表示しています。

Convert an existing prose, flat, or loosely organized mathematical proof into a source-mapped Lamport-style hierarchy without repairing or completing its mathematics. Use when a submitted proof needs a traceable hierarchical rendering before a forward Lamport audit or for clearer presentation. Do not use to invent a proof, certify validity, or restructure an already hierarchical proof merely to audit it.

日本語の概要は準備中です。原文の説明を表示しています。

When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.

日本語の概要は準備中です。原文の説明を表示しています。

Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

日本語の概要は準備中です。原文の説明を表示しています。

Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.

日本語の概要は準備中です。原文の説明を表示しています。

用于创建、维护、调试或审查真实浏览器端到端测试，包括 Playwright/Cypress、Page Object、CI 产物、trace、不稳定用例、跨页面视觉回归以及登录、支付、权限或 CRUD 等关键用户旅程。若是测试层规划或靠近 UI 组件的测试，先选择对应测试工作流；中文触发词包括 E2E、端到端测试、Playwright、Cypress。

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating, maintaining, debugging, or reviewing real-browser end-to-end tests with Playwright or Cypress, including Page Object models, CI artifacts, traces, flaky tests, cross-page visual regression, and critical user journeys such as login, payment, permissions, or CRUD. For layer planning or tests close to UI components, choose the matching testing workflow first; Chinese triggers include E2E, end-to-end testing, Playwright, Cypress.

日本語の概要は準備中です。原文の説明を表示しています。

Design and analyze engineering experiments or simulations using baseline cases, hypothesis-driven DOE, traceable data processing, defensible plots, uncertainty, and validation. Use for CFD, laboratory data, ML workflows, parameter studies, or research code.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Electrical and Electronics Drafter — sizing a conductor and conduit for a panel or feeder circuit against NEC ampacity and fill tables, building a schematic/elementary diagram or one-line diagram on IEEE 315/ANSI Y32.2 symbols, cross-referencing wire numbers between a schematic and a panel wiring diagram, sizing a PCB trace against IPC-2221 current tables, or QC-checking an electrical drawing set before issuance.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Drilling and Boring Machine Tool Setter, Operator, or Tender — deciding whether a hole's depth-to-diameter ratio requires peck drilling, establishing a straight hole start before wander compounds, reducing cutting parameters for a long-reach boring setup versus a short-reach one, or diagnosing whether a dimensional drift traces to tool wear rather than assuming the tool still looks sharp.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs senior database-administrator judgment — diagnosing replication lag or a stalled query, sizing a connection pool or index, planning a schema migration on a live table, running backup/restore and failover drills, or triaging a production incident traced to the database.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a CNC Tool Operator — diagnosing a dimension trending toward its tolerance limit across consecutive parts before it actually crosses, deciding whether to apply a tool wear offset or flag the tool for replacement, evaluating whether a failed part traces to work-holding repeatability versus a program or tool issue, or verifying a setup change with a first-article inspection before running production quantity.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Continuous Mining Machine Operator in underground coal — reading a methane monitor trend and deciding whether to de-energize, judging whether cumulative unbolted advance has hit the roof control plan's cut-depth limit, deciding whether a permissibility defect requires immediate shutdown in a gassy heading, diagnosing whether a shift's production shortfall traces to cutting rate or shuttle-car haulage, or deciding whether a "drummy" roof sound stops the cut.

日本語の概要は準備中です。原文の説明を表示しています。