StudyDrift

Implements the next mobile story

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Implements a new planned feature

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

Fetch and summarize review comments from the active pull request

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Use this when the next feature needs to be implemented.

中文简介正在准备中。当前显示原文说明。

Turns a feature request into a full implementation-plan requirements document matching docs/plan/_TEMPLATE.md. Use when the user asks for requirements, a spec, an implementation plan, or wants to flesh out a feature before building. Also use for /requirements or "write requirements for X".

中文简介正在准备中。当前显示原文说明。

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。