1.3万 件 ・ 関連度順
Generate or materially revise a repository-local test plan, QA plan, acceptance matrix, or regression checklist on explicit request or when one concrete testability gap blocks formal DEFINE; do not trigger for ordinary implementation, test execution, TDD, review, or completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
Create, revise, or evaluate repository Agent Skills when the user asks to write a SKILL.md, improve triggers or information hierarchy, restructure references/scripts/assets, or diagnose skill predictability; do not use for product code, AGENTS.md initialization, general prompt editing, or automatic repository-wide cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Create or materially revise a durable specification when the user explicitly requests a spec/new feature contract or a named ambiguity requires formal DEFINE; do not trigger for ordinary bounded edits, implementation, task breakdown alone, review, or documentation of already-settled behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve one exact official/current documentation gap when the user requests source verification or a version-sensitive API/SDK/provider/framework question can materially change the current decision; do not trigger for every implementation decision, ordinary framework code, local business logic, or broad research.
日本語の概要は準備中です。原文の説明を表示しています。
Silent failure hunting routing. Use when a change might pass while skipping work, swallowing errors, losing evidence, weakening gates, or reporting false success; do not use for broad code review.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare an explicit production launch, staged rollout, launch-monitoring, or rollback plan; do not trigger from AILI SHIP, implementation completion, packaging, review, or release wording that lacks a concrete launch/rollout target.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Produce or apply an approved report-first proposal for workflow, ROSE, skill, command, subagent, memory, install, or harness-doc changes; use after harness-issue-triage localizes a harness problem or when the user explicitly requests harness maintenance, and do not edit core harness files without explicit human approval.
日本語の概要は準備中です。原文の説明を表示しています。
Handle an explicit Git intent such as branch/worktree setup, commit organization, history archaeology, conflict resolution, PR preparation, or versioning; do not trigger as a process skill for every code or file change.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Build rich marketing/media frontend experiences with cinematic motion, AI assets, copy, and generative art.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Build Flutter/Dart cross-platform apps with widgets, state management, navigation, tests, and performance patterns.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Configure or diagnose project context, rules files, context packs, or documented context degradation when explicitly requested; do not trigger automatically at session start, task switching, ordinary repository exploration, implementation, or completion.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct one bounded evidence-grounded code review when the user explicitly requests review or ROSE names a concrete unresolved correctness/quality risk; do not trigger automatically after implementation, before every merge, for every bug fix/refactor, or as a completion gate.
日本語の概要は準備中です。原文の説明を表示しています。
Code-review quality gate and test-enhancement rubric. Use when ROSE needs sharper review output contracts, severity and risk prioritization, evidence anchors, negative review cases, fixture or golden-output drift guidance, or a Chinese review report profile; do not use as a duplicate code-review agent or final PASS authority.
日本語の概要は準備中です。原文の説明を表示しています。
Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。