ADB-based RIPDPI device/emulator debugging: build/install/launch, logcat filtering, fixture port-forwarding, instrumented tests, crash/ANR triage. Use when debugging on a real device or emulator.
日本語の概要は準備中です。原文の説明を表示しています。
3,042 件 ・ 関連度順
概要と使いどころ
ADB-based RIPDPI device/emulator debugging: build/install/launch, logcat filtering, fixture port-forwarding, instrumented tests, crash/ANR triage. Use when debugging on a real device or emulator.
日本語の概要は準備中です。原文の説明を表示しています。
RIPDPI Appium failure triage: flaky tests, locator/session/wait issues, screenshot and element-tree debugging. Use when an Appium test fails or is flaky.
日本語の概要は準備中です。原文の説明を表示しています。
Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js frontend development standards for Retail-Agentic-Commerce. Use when creating or modifying UI pages, components, hooks, styling, tests, or Apps SDK widget browser behavior in src/ui or related frontend surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Python backend development standards for FastAPI, SQLModel, pytest, Ruff, and Pyright. Use when writing or modifying backend code in src/merchant, src/payment, src/apps_sdk, agents, tests, API routes, services, models, or protocol logic.
日本語の概要は準備中です。原文の説明を表示しています。
Discoverability shim for the Retail-Agentic-Commerce UI Codex skill. Use when creating or modifying frontend pages, components, hooks, styling, tests, or browser behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Discoverability shim for the Retail-Agentic-Commerce backend feature Codex skill. Use when writing or modifying Python backend code, routes, services, models, tests, or protocol logic.
日本語の概要は準備中です。原文の説明を表示しています。
Kundenforschung datensparsam und einwilligungsorientiert planen, durchführen und auswerten. Nutze diesen Skill für Interviewleitfäden, Umfragen, Usability-Tests, die Auswertung vorhandener Gespräche, Support-Tickets oder Bewertungen, und für Personas, Segmente und Jobs-to-be-Done. Klärt vorab Zweck, Rechtsgrundlage, Einwilligung, Aufzeichnung, Pseudonymisierung und Aufbewahrung, wertet nur innerhalb des Stichprobenrahmens aus und trennt Befund von Entscheidung. Beachtet DSGVO, BDSG und Beschäftigtendaten; Österreich und Schweiz werden getrennt behandelt.
日本語の概要は準備中です。原文の説明を表示しています。
Codify project review rules as deterministic guards — ast-grep structural rules (with TDD-style rule tests) for mechanical checks, REVIEW_GUIDELINES.md for qualitative ones, wired into the project gate / wf verify. Use when the user wants to define review rules, turn a repeated review finding into a lint/guard, or set up ast-grep in a project.
日本語の概要は準備中です。原文の説明を表示しています。
Entity-aware code change analysis using the pi-sem tools. Use when the user asks what changed, wants blast radius or affected tests, needs focused context for a function/class, wants review help on a commit/branch/PR, or asks to compare semantic diff with raw git diff. Prefer sem_context and sem_impact; use sem_diff selectively for summaries and reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Act as an end-to-end data scientist: turn business questions into defensible analysis, validated models, and decision-ready reports. Use whenever the user asks to analyze, explore, or profile a dataset or CSV/Parquet/Excel file; asks what drives a metric or why a number changed ("why did churn go up?"); wants to test whether a difference is real (A/B tests, experiments, "is this significant?", "how many samples do I need?"); wants a predictive model (churn, forecast, scoring, segmentation, classification, regression); asks to review an existing analysis, notebook, or model for flaws; or needs results written up for decision-makers. Triggers in any language ("phân tích dữ liệu", "xây model dự đoán", "kiểm định A/B"), even when they never say "data science" or "statistics".
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to say a fix works, tests are green, a bug is resolved, a task is done, or a branch is ready for review or submit.
日本語の概要は準備中です。原文の説明を表示しています。
Configures integration tests with WebApplicationFactory and Testcontainers. Provides test database setup, authentication helpers, and utilities for testing API endpoints with real dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Generates unit tests for command and query handlers using xUnit and NSubstitute. Implements Arrange-Act-Assert pattern with comprehensive test coverage for success and failure scenarios.
日本語の概要は準備中です。原文の説明を表示しています。
Translate hand-written Playwright specs (or any existing UI tests) into Gherkin features on @datagrok-libraries/bdd, then prove the features test what they claim by backward-matching them against the originals with independent reviewers, and fix the gaps in the core, the library and the features
日本語の概要は準備中です。原文の説明を表示しています。
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Calculus, series, numerical methods, and optimization for computational mathematics. Covers limits (epsilon-delta, L'Hopital, squeeze theorem), derivatives (rules, optimization, related rates), integrals (Riemann sums, Fundamental Theorem of Calculus, integration techniques), series (convergence tests, Taylor and Maclaurin expansions), differential equations (separable, linear, exact), numerical methods (Newton-Raphson, Euler method, Simpson's rule), and computational pitfalls (floating-point arithmetic, catastrophic cancellation, numerical stability). Use when computing derivatives, integrals, limits, series, solving differential equations, or analyzing numerical accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
CAD fundamentals, 3D printing (FDM/SLA/SLS), CNC machining, workshop skills, rapid prototyping methodology, and testing of physical prototypes. Covers fidelity levels, material selection for prototypes, dimensional tolerancing, assembly planning, and the iterate-test loop. Use when building prototypes, selecting fabrication methods, planning physical tests, or choosing between prototyping technologies.
日本語の概要は準備中です。原文の説明を表示しています。
A/B testing, randomization, sample size calculation, confounding control, and causal inference for data science. Covers the full experimental lifecycle from hypothesis formulation through power analysis, randomization strategies, blocking, factorial designs, sequential testing, and the potential outcomes framework for causal claims. Use when designing experiments, planning A/B tests, calculating sample sizes, or reasoning about causation from data.
日本語の概要は準備中です。原文の説明を表示しています。
Generates test cases for functions and components. Use when writing tests or creating test suites.
日本語の概要は準備中です。原文の説明を表示しています。
Invoke the rubber duck reviewer for a second opinion. Use after planning, after complex multi-file implementations, or after writing tests. Produces a focused CRITICAL/WARN/INFO list and a APPROVE/REQUEST_CHANGES verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Drive development with a red-green-refactor TDD cycle, ensuring tests are written before implementation. Use when implementing any new functionality.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a complete component file tree wired to design tokens with tests and Gherkin spec. Use when scaffolding a new UI component.
日本語の概要は準備中です。原文の説明を表示しています。
Use Playwright CLI for interactive browser exploration and snapshot-based interaction. Use when writing or running browser automation tests.
日本語の概要は準備中です。原文の説明を表示しています。