ThiagoGuislotti

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

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

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.

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

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.

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

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.

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

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.

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

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

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

Sync shared repo assets into local ~/.github and ~/.codex, and apply MCP settings from the shared canonical runtime catalog.

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

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.

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

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.

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

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.

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

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 using the repository-owned runtime helper and Windows-safe defaults.

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

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.

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