AspireAcademy

Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman), Azure deployment after local testing (use azure-deploy skill). INVOKES: Aspire CLI commands (aspire start, aspire describe, aspire otel logs, aspire docs search, aspire add), bash. FOR SINGLE OPERATIONS: Use Aspire CLI commands directly for quick resource status or doc lookups.

Adds new features to the application including API endpoints, React pages, components, and curriculum content. USE FOR: implementing new features, adding API endpoints, creating React components, adding curriculum content, writing unit/API tests. DO NOT USE FOR: E2E browser tests (use add-e2e-tests skill), adversarial/break testing (use adversarial-tester skill).

Adds E2E tests using C# Playwright against the real running app. USE FOR: adding end-to-end tests, verifying test coverage, writing browser-based integration tests, E2E test failures. DO NOT USE FOR: unit tests or API-only tests (use add-feature skill).

Runs adversarial testing against the live app to find bugs and broken flows. USE FOR: breaking things deliberately, stress testing UI flows, finding edge cases, testing error handling, verifying XSS/injection protection, double-click prevention, refresh resilience. DO NOT USE FOR: writing new features (use add-feature skill), structured E2E test suites (use add-e2e-tests skill).