「tests」の検索結果

Generates A/B test plans and optimization checklists for your App Store product page — icon, screenshots, and app previews. Use when running Product Page Optimization tests or improving conversion rates.

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

Generates an automated App Store screenshot pipeline with UI tests for screenshot capture, device framing, localized caption overlays, and multi-size batch export. Use when user wants automated screenshots, App Store screenshot generation, or a fastlane snapshot replacement.

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

Implements a variety of methods for combining p-values in differential analyses of genome-scale datasets. Functions can combine p-values across different tests in the same analysis (e.g., genomic windows in ChIP-seq, exons in RNA-seq) or fo

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

Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.

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

Expert knowledge for Azure Business Process Tracking development including deployment. Use when creating CI/CD pipelines, automating builds, running tests, and deploying tracking solutions via DevOps tools, and other Azure Business Process Tracking related development tasks. Not for Azure Monitor (use azure-monitor), Azure Logic Apps (use azure-logic-apps), Azure Data Factory (use azure-data-factory), Azure Machine Learning (use azure-machine-learning).

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

Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.

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

Use this skill when changing service structure, Subscribers, ServiceProviders, Container wiring, bootstrapping, Context classes, or any code that may affect the core caching engine in WP Rocket. Also use it when reading constants, writing unit tests that depend on constants, or opening a pull request.

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

Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment. Standalone entry point for the qa-engineer agent.

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

Diagnose and fix tests that pass sometimes and fail other times. Use when CI is red intermittently.

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

Find the untested code paths that actually matter, not just the coverage percentage. Use after adding tests.

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

Replace arbitrary timeouts with condition polling for reliable async tests

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

Tests whether a scene is structurally worth generating before any shot is prompted — a five-element engine of Goal, Obstacle, Tactic, Reversal, and Value Shift. Use when the user has a scene, sequence, beat outline, or script and wants it audited or strengthened; when a sequence generates cleanly but lands flat and nobody can say why; when shots look good individually but the run of them does not build; or when the user asks 'is this scene working', 'what's weak here', or 'why doesn't this land'. Upstream of prompting — it decides WHICH shots deserve the credits, not how to write them. Pairs with higgsfield-character-design (who the characters are) and higgsfield-shotlist-director (turning the settled scene into shots).

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

Design, plan, and analyze A/B tests with statistical rigor. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, sample size calculation, test duration, multivariate testing, or conversion experiments. Trigger phrases include "A/B test", "split test", "experiment", "statistical significance", "sample size", "test duration", "which version wins", "conversion experiment", "hypothesis test", "variant testing".

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

Find which ChatGPT search queries mention a given brand. Tests long-tail queries against ChatGPT's web-search-enabled model and reports which ones surface the brand. Use when the user asks to "find queries for [brand]", "check GEO visibility", "which queries mention [brand]", "geo query finder", "find AI mentions", or "test ChatGPT queries for [brand]".

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

Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from `git status`, or to review a specific backlog task by id such as `task-65` or `TASK-65`. Also trigger when the user says things like "review", "review current changes", "check my changes", "look over the diff", or "review task-42".

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

Use after every code change, after writing tests, or before marking a task complete, and when the user says verify, quality gate, or audit code. Runs a 7-category mechanical check for TDZ, import, dead code, and mock leakage bugs.

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

Use when implementation is done and tests pass and the user must choose to merge locally, open a PR, keep the branch, or discard it. Presents those four options, executes the choice, and cleans up the worktree for merge and discard.

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

Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.

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

Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.

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

Use when writing, reviewing, refactoring, or planning Flutter/Dart code — screens, features, project structure, state management, folders, widgets, cubits/blocs, repositories, services, or tests.

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

Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).

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

Hire one of the eight open source AI Employees (GTM Engineer, SEO/AEO, Web Dev, Social Media, Ad Manager, Sales, Customer Satisfaction, Chief of Staff) into a local folder, prove it runs, and hand over its install prompt. Also answers which one to hire first, how a hired employee runs on a schedule, how to direct it, how it improves from corrections, and how to upgrade it. Use when the user says hire an employee, install an AI employee, set up the GTM Engineer, names one of the eight, or asks how AI Employees work. It copies files and runs self tests only. It registers no schedule and sends nothing.

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

Monthly, on the last weekday, light browser lane. Re-tests every named qualification test and every buyer segment against a month of this kit's own ledger evidence, then rewrites both files itself where the evidence disagrees with the assumption they were written on. It records every change in strategy/CHANGELOG.md with the ledger path that justified it. It sends only where you released the channel, never re-queues anyone, never edits the contacted ledger, and never writes a number it did not count out of a named file.

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

Monthly on the last weekday, light browser lane. Re-tests every theme and every severity rule against a month of real ticket evidence and rewrites strategy/themes.md wherever the evidence disagrees with the assumption. It merges two themes the evidence shows are one, splits a theme whose tickets have two different answers, retires a theme with no volume, creates a theme for a cluster that kept landing unclassified, and rewrites a severity rule wherever the outcomes contradict it. Theme ids are never reused and never renumbered. It holds every outbound action unless you released the channel, and it never touches a credential.

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