「flow」の検索結果

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.

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

Configure or modify concrete CI/CD pipelines, jobs, quality gates, test runners, or deployment automation; do not trigger merely because an existing CI gate failed or ordinary source code needs repair.

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

Design, critique, or specify honest charts and data visualizations from known data and audience needs. Use for chart selection, misleading-chart audits, accessibility, dashboard visuals, or "make this data easier to understand"; do not use for raw data analysis, PPT deck generation, spreadsheet surgery, or fabricated chart data.

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

Perform a bounded security design/hardening pass for explicit security or threat-model intent, or a concrete auth/authorization/secret/untrusted-input/file-upload/sensitive-data risk; do not trigger for every input, data store, third-party call, implementation, review, or release.

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

Repair one concrete reproducible build, typecheck, lint, test, packaging, or CI failure with a bounded root-cause-first loop; do not trigger for runtime bugs without a failing gate, broad test strategy, dependency/toolchain migration, or generic implementation.

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

Optional focused post-implementation review routing. Use only when the user requests review or the changed surface has a clear specialist evidence need that direct diff inspection and the smallest relevant check cannot cover. Never creates an automatic review swarm.

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

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.

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

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.

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

Build rich marketing/media frontend experiences with cinematic motion, AI assets, copy, and generative art.

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

Create, fill, or reformat print-ready PDFs with strong visual page fidelity.

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

Build Flutter/Dart cross-platform apps with widgets, state management, navigation, tests, and performance patterns.

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

Create, edit, analyze, format, or validate Excel/XLSX/CSV spreadsheets with managed OfficeCLI first and pandas/XML preservation-aware fallbacks.

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

Explain a complex concept through a short allegory, story, analogy, metaphor, or intuitive teaching example, then map it back to formal concepts and limits; do not use as the primary skill for implementation, specs, source-cited API guidance, or fiction-only writing.

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

Performs read-only GitHub issue or PR triage with evidence links. Use when analyzing public or repository GitHub issues/PRs without mutating labels, comments, branches, reviews, merges, or issue state.

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

Research one bounded mature-project/prior-art question when the user explicitly asks how established projects handle it or ROSE names a decision-shaping prior-art gap; do not trigger automatically for IDEATE, DEFINE, BUILD, implementation, local review, or every design choice.

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

Generate or edit a source-grounded newsletter issue, digest, or briefing from provided or researched sources. Use for weekly/monthly updates, curated links, executive digests, community newsletters, or "turn these sources into a newsletter"; do not use for UI landing pages, marketing campaign design, unsourced news claims, or long-form research reports.

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

Build native iOS apps with SwiftUI, UIKit, SnapKit, Apple HIG, accessibility, and platform UI patterns.

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

Run a non-destructive open-source, npm, or public release readiness checklist covering package metadata, provenance, license, internal artifact exposure, and dry-run evidence; complements security, shipping, and sanitizer reviews, and must not publish, delete, rewrite history, or mutate release state.

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

Prefer a fresh matching specialist for a clear bounded non-trivial package when current capabilities and permissions permit it; use direct ROSE work only for accepted direct-work exceptions or a concrete block.

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

Create or update source-grounded documentation when the user explicitly asks for docs/ADR/onboarding material, a public contract change requires docs, or an accepted hard-to-reverse decision meets the ADR gate; do not trigger for every feature, architecture discussion, implementation, review, or SHIP request.

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

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

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

Optimize a measured performance problem when the user names a latency/load/Core Web Vitals/resource target or current profiling evidence identifies a bottleneck; do not trigger from generic implementation, review, or an unsupported suspicion that code may be slow.

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

Analyze source data, tables, CSV/XLSX extracts, metrics, or experiment results with explicit data-authenticity checks. Use for profiling, cleaning assumptions, statistical summaries, segmentation, trend analysis, or "analyze this data"; do not use for spreadsheet file surgery, chart design only, database migrations, or claims without data provenance.

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

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.

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