'gui' 검색 결과

Route tasks using this repository's static routing catalog and load only the minimal context pack.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a minimal context pack and recommend the correct specialist path for token-efficient execution. Use when the task is non-trivial, spans multiple domains, or should reduce token usage before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sync shared repo assets into local ~/.github, ~/.codex, and ~/.claude, and apply MCP settings from the shared canonical runtime catalog. Use when runtime assets are stale or after onboarding a new machine.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is reached.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 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 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create safe, deterministic git worktrees for large or risky workstreams using the repository-owned runtime helper and Windows-safe defaults.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.