5.7万 件 ・ 関連度順
Use for non-trivial, design-bearing, or architecture-affecting work before execution planning. Creates or updates a versioned spec under planning/specs/active/ with design intent, alternatives, risks, and acceptance criteria.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Create safe, deterministic git worktrees for large or risky workstreams. Use when tasks are complex enough to warrant isolation from the main working tree.
日本語の概要は準備中です。原文の説明を表示しています。
Use for non-trivial feature, behavior, workflow, or architecture work before execution planning. Create or update a versioned spec under planning/specs/active with design intent, alternatives, risks, acceptance criteria, and planning readiness.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use as the single visible starter and controller for workspace work that may change files, runtime assets, planning state, docs, settings, or governance. Normalize the request into the Super Agent lifecycle: intake, spec registration for non-trivial work, planning registration, specialist routing, execution, testing, review, closeout, and planning-state updates before implementation begins.
日本語の概要は準備中です。原文の説明を表示しています。
Sync shared repo assets into local ~/.github and ~/.codex, and apply MCP settings from the shared canonical runtime catalog.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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, 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.
日本語の概要は準備中です。原文の説明を表示しています。
Base implementation skill. Use for code changes, bug fixes, refactors, and script work across .NET/C#, backend APIs, database/ORM, Vue/Quasar frontend, Rust, PowerShell, Docker, K8s, CI/CD, security, observability, and SRE domains. Specialized skills extend this as a base.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare a MYOT commit by writing SuggestedCommit.txt and SuggestedCommitBody.md following Conventional Commits, without actually committing.
日本語の概要は準備中です。原文の説明を表示しています。
Code implementation, refactoring, and bugfixes. USE FOR: implementing features; refactoring code; fixing bugs; modifying existing code. DO NOT USE FOR: writing tests (separate skill); documentation (separate skill); commit conventions (separate skill).
日本語の概要は準備中です。原文の説明を表示しています。
Code implementation, refactoring, and bugfixes for create-vue-dsfr. Use for implementing features, refactoring code, or fixing bugs. Read the shared project skill before acting.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reading or changing example.com content, settings, products or pricing through the MCP API at /api/mcp — the 27 JSON-RPC tools, how to authenticate, which changes need a redeploy and which are live immediately, and the commercial scope rule that the product tools enforce.
日本語の概要は準備中です。原文の説明を表示しています。
Apply this site's visual identity — colours, type, logo files and fixed brand strings. Use for any page, component, social asset or document that should look like the site.
日本語の概要は準備中です。原文の説明を表示しています。
Use after building a feature — explore it in a real browser to find what nobody predicted, then turn each finding into a deterministic test that guards it forever. Covers the agentic pass, what to generate vs hand-write, and how to skip honestly when a capability is missing.
日本語の概要は準備中です。原文の説明を表示しています。
Use FIRST when someone asks for a new feature or a change to an existing one — before any schema, code or test. Works out what is actually being asked for, whether to build it or integrate a third party (Trustpilot, Stripe, Calendly and the like), where the data lives, who may do what, and what happens when the vendor is down. Produces a decision, then hands to feature-schema.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing or improving example.com's SEO/indexing — Google Search Console issues (404s, sitemap, "discovered not indexed"), on-page checks (title/meta/canonical/OG/H1/internal links), or wiring search-engine notification (IndexNow/GSC/Bing/Yandex). Also use when the operator pastes GSC findings and asks to fix + validate.
日本語の概要は準備中です。原文の説明を表示しています。