Runs when you submit a prompt, before the agent sees it for checkpoint, compress context, update plan, show status, show progress and resume from summary tool calls, running an inline shell check. From ThiagoGuislotti/copilot-instructions.
Runs when the agent finishes a response, executing export-planning-summary.ps1 via pwsh with --- (2 commands). From ThiagoGuislotti/copilot-instructions.
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.
Assembles the minimal context pack for a given task. Use when the task spans multiple domains or the context set has obvious redundancy. Do not trim required working context by default.
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.
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.
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.
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 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.
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.
Design and implement observability and SRE controls including SLO/SLI, OpenTelemetry instrumentation, alerting, dashboards, and incident readiness. Use when tasks involve telemetry coverage, operational reliability metrics, incident response, or runbook quality.
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.
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 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.
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.
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.
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.
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…