1.1万 件 ・ 関連度順
概要と使いどころ
Improve platform resilience with timeout/retry/circuit-breaker strategy, capacity controls, chaos testing, and disaster recovery readiness. Use when tasks involve reliability hardening, failure-mode testing, incident prevention, or recovery objectives.
日本語の概要は準備中です。原文の説明を表示しています。
Design and enforce privacy and data protection controls across application, API, and database layers. Use when tasks involve PII handling, retention/deletion policies, consent, data minimization, auditability, or compliance-oriented architecture changes.
日本語の概要は準備中です。原文の説明を表示しています。
Base implementation skill for this repository across .NET/C#, backend APIs, database/ORM, frontend Vue/Quasar, and Rust with Clean Architecture rules. Use when the user asks to build features, fix bugs, refactor modules, or improve code-level performance, and use specialized skills as inheritance layers when available.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and sequence complex implementation work into deterministic, testable steps for this repository. Use when the user asks for planning, roadmap breakdown, execution strategy, effort estimation, or multi-step delivery coordination across domains.
日本語の概要は準備中です。原文の説明を表示しています。
Perform repository-aware code reviews focused on bugs, regressions, architectural violations, missing tests, and operational risks. Use when the user asks for review of diffs, pull requests, patches, or implementation quality.
日本語の概要は準備中です。原文の説明を表示しています。
Create safe, deterministic git worktrees for large or risky workstreams. Use when tasks are complex enough to warrant isolation from the main working tree.
日本語の概要は準備中です。原文の説明を表示しています。
Creates or updates the active planning artifact under planning/active/ for any change-bearing workstream. Consumes the active spec when one exists. Defines ordered tasks, target paths, commands, and checkpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates before build/package.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and sequence complex implementation work into deterministic, testable steps. Use when the user asks for planning, roadmap breakdown, execution strategy, effort estimation, or multi-step delivery coordination across domains.
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain CI/CD pipelines, containerization, Kubernetes manifests, and quality gates for this repository. Use when the user asks for Docker, Kubernetes, GitHub Actions/Azure DevOps pipelines, deployment, reliability, or static analysis workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, and stabilize automated tests in this repository (unit, integration, and E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.
日本語の概要は準備中です。原文の説明を表示しています。
Implement, organize, and test Rust modules in this repository following mandatory project organization and test discovery rules. Use when tasks involve Cargo crates, module structure, Rust refactors, or creation/fix of Rust tests including required error test coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Route tasks using this repository's static routing catalog and load only the minimal context pack.
日本語の概要は準備中です。原文の説明を表示しています。
Implement, organize, and test Rust modules following mandatory project organization and test discovery rules. Use when tasks involve Cargo crates, module structure, Rust refactors, or creation/fix of Rust tests including required error test coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, and stabilize automated tests (unit, integration, E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.
日本語の概要は準備中です。原文の説明を表示しています。
Extend dev-software-engineer with .NET/C# backend specialization for Clean Architecture, CQRS, EF Core, and production-ready API practices. Use when tasks involve ASP.NET endpoints, handlers, services, dependency injection, MediatR, migrations, or backend performance/resilience and should follow the base implementation workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Implement and refactor frontend features using Vue and Quasar with repository architecture, theming, UX, and performance standards. Use when tasks involve components, composables, Pinia, routing, i18n/UI behavior, responsive layouts, or frontend clean architecture changes.
日本語の概要は準備中です。原文の説明を表示しています。
Extend dev-software-engineer with .NET/C# backend specialization for Clean Architecture, CQRS, EF Core, and production-ready API practices. Use when tasks involve ASP.NET endpoints, handlers, services, dependency injection, MediatR, migrations, or backend performance/resilience.
日本語の概要は準備中です。原文の説明を表示しています。
Produce and maintain repository documentation and release artifacts including README files, PR descriptions, changelog entries, prompt templates, and instruction docs. Use when the user asks to create or update docs/process files under .github or project root.
日本語の概要は準備中です。原文の説明を表示しています。
Route tasks using the repository's static routing catalog and load only the minimal context pack. Use before execution when the task spans multiple domains or the correct instruction set is unclear.
日本語の概要は準備中です。原文の説明を表示しています。
Build and harden high-performance APIs with strong security controls, endpoint budgets, rate limiting, and resilience patterns. Use when tasks involve API latency/throughput tuning, abuse resistance, authz hardening, or API release gates.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update active planning documents under `planning/active`, then define the execution slices, validations, specialist handoff, and closeout expectations. Use when the task is non-trivial, multi-step, or explicitly asks for planning.
日本語の概要は準備中です。原文の説明を表示しています。
Start or resume a MYOT task by reading AGENTS.md, project_map.md, and history.md, archiving history.md when switching tasks, and preparing a concise current task snapshot.
日本語の概要は準備中です。原文の説明を表示しています。