Skeptical analysis and critique of claims, plans, and code without taking anyone at face value. Use when the user says "don't trust me", wants adversarial review, red-teaming, assumption checking, or verification that generated or proposed code is actually correct. Triggers on skepticism, critique everything, verify claims, challenge assumptions, red team, devil's advocate, prove it, smell test.

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

Find failing PR checks, inspect logs or external check links, and apply focused fixes

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

Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

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

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.

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

Implements a new planned feature

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

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

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