本文へ移動
cccskills
無料GitHub で公開

browser-qa

Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.

Rosetears520/aili-workflows
インストール方法を見る

含まれるファイル（1）

  • SKILL.md2.2 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Browser QA

Use this skill only for the delegated browser path. Direct browser inspection is owned by browser-testing-with-devtools; the two paths are mutually exclusive for one current intent.

Trigger

  • The user explicitly requests independent/delegated browser QA.
  • One concrete browser evidence gap requires browser-qa-runner rather than direct browser tools.
  • Durable browser/E2E artifact evidence is explicitly required and placement is resolved.

Required Safety Gate

  • Resolve the target URL/environment from current user/project evidence. Ask only when target identity is materially ambiguous or the action could cross an external/production gate.
  • Avoid production mutation: no real purchases, messages, account changes, destructive forms, or production data writes without the exact operation-specific approval.
  • Before saving screenshots, traces, videos, reports, console logs, or network logs, obtain a repository-local artifact placement. If no placement exists, keep evidence inline/ephemeral and report no durable artifact.

Near Misses

  • Persistent E2E packaging, direct local browser inspection, or backend-only verification are different primary intents. Return the exact mismatch to ROSE; do not select another skill here or combine the direct/delegated browser paths.
  • Creating Playwright config or test directories: requires explicit implementation scope and placement decision.

Required Routing

  • Canonical owner: ROSE/aili-delivery-flow.
  • Optional agent: one fresh, terminal browser-qa-runner assignment after a new benefit decision.

ROSE/aili-delivery-flow owns mode, exact external/production approvals, artifact placement decisions, and final verification. This skill may return one bounded delegation need but does not invoke another skill or create a retry/review chain. One fresh QA assignment is terminal; report complete, need-user, need-evidence, material-delta, blocked, or Unverified. Canonical claim-matched verification wins.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

academic-paper-review

無料

Review a single academic paper, preprint, DOI, arXiv link, or user-provided PDF/text with source-grounded critique. Use for paper summaries, methodology review, novelty checks, reproducibility concerns, or "review this paper" requests; do not use for multi-paper surveys, systematic literature reviews, citation management, or implementation from a paper.

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

Rosetears520/aili-workflows22026年9月27日 更新

ai-regression-scout

無料

AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.

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

Rosetears520/aili-workflows22026年9月27日 更新

aili-delivery-flow

無料

Run the AILI delivery lifecycle from natural-language IDEATE, DEFINE, BUILD, and SHIP intent or the equivalent slash shortcuts; use for idea shaping, spec/test definition, bounded BUILD package queues, review-repair closeout, or adapter routing without exposing internal stage commands.

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

Rosetears520/aili-workflows22026年9月27日 更新

android-native-dev

無料

Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.

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

Rosetears520/aili-workflows22026年9月27日 更新

api-and-interface-design

無料

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

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

Rosetears520/aili-workflows22026年9月27日 更新

browser-testing-with-devtools

無料

Perform direct, bounded browser inspection through the `browser.qa` capability when the user requests runtime UI evidence or one browser-specific claim needs DOM/accessibility/console/network/visual verification; do not trigger for every UI change, backend work, delegated QA, or durable E2E artifact routing.

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

Rosetears520/aili-workflows22026年9月27日 更新

Rosetears520 のスキルをすべて見る

このスキルの問題を報告する