1.3万 个 · 按相关度排序
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.
中文简介正在准备中。当前显示原文说明。
Build or modify production UI components, layouts, client state, responsive behavior, accessibility, or UX inside an app when that frontend surface is the primary deliverable; do not trigger for rich campaign/media pages, backend integration, every user-facing text change, delegated browser QA, or review alone.
中文简介正在准备中。当前显示原文说明。
Build rich marketing/media frontend experiences with cinematic motion, AI assets, copy, and generative art.
中文简介正在准备中。当前显示原文说明。
Build Flutter/Dart cross-platform apps with widgets, state management, navigation, tests, and performance patterns.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Coverage review and verification sufficiency routing. Use when test coverage, uncovered paths, coverage reports, or verification adequacy need a read-only QA review; do not use for writing tests or running browser/E2E artifacts.
中文简介正在准备中。当前显示原文说明。
Break a clear scope or accepted specification into ordered tasks/packages when the user explicitly asks for a plan, estimate, dependency order, or task breakdown; do not trigger for ordinary implementation, every multi-step task, speculative parallelism, review, or completion.
中文简介正在准备中。当前显示原文说明。
PR test analysis routing. Use for pull request or diff test impact, changed-test review, CI failure interpretation, and focused test matrix recommendations; do not use for general code review or editing tests.
中文简介正在准备中。当前显示原文说明。
Structure source-grounded consulting-style analysis for strategy, market, product, operations, or decision memos. Use for MECE problem framing, hypotheses, options, tradeoffs, executive recommendations, or "consulting analysis" requests; do not use for legal/financial advice, implementation, data computation, chart rendering, or unsourced business claims.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Review comment, JSDoc, TODO, README, and docs-to-code factual consistency, stale or low-value comments, and Chinese comment/variable appropriateness; do not use for general code review, broad documentation rewrites, or auto-editing comments without approval.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Simplify a bounded code area when the user explicitly requests behavior-preserving refactoring or a named complexity/readability problem is the accepted task; do not trigger automatically after implementation, during every review, for adjacent cleanup, or when behavior may change.
中文简介正在准备中。当前显示原文说明。
Clarify a concrete requirements decision, create one bounded static interview packet, or run an explicitly user-invoked frontier batch over a plan, decision, or idea; trigger on explicit grill/interview/refinement intent or a named material ambiguity, not on ordinary planning, implementation, research, test-plan, report-style review, or BUILD work.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。