kagents

Plugin kagents from marketplace kagents in GrexyLoco/K.Agents. Commands read from the repo's manifest — 1 month ago.

Skills (49)

• api-design-patterns

  API-Design-Muster — Minimal APIs vs. Controller, TypedResults, Versioning, DTOs, Validation. USE FOR: designing REST API structure, implementing request/response patterns, versioning strategies. DO NOT USE FOR: Minimal API syntax details (use minimal-api-patterns) or authentication (use authenticati

• api-documentation

  API-Dokumentation — XML-Doc Comments (C#), Comment-Based Help (PowerShell), Parameter-Dokumentation. USE FOR: writing XML-Doc for public APIs, adding PowerShell Comment-Based Help, documenting method signatures. DO NOT USE FOR: inline code comments (use inline-documentation) or user-facing docs (use

• app-architecture

  .NET Applikationsarchitektur — Modular Monolith, Microservices, Clean Architecture für Blazor, MAUI, ASP.NET Core

• aspire-architecture

  .NET Aspire AppHost, Service Defaults, integrations (Postgres, Redis), service discovery, health checks, Polly resilience, telemetry pipeline. USE FOR: configuring Aspire orchestration, adding service references, setting up cloud-native distributed applications. DO NOT USE FOR: Aspire integration te

• aspire-integration-testing

  .NET Aspire integration testing — DistributedApplicationTestingBuilder, AppHost test fixtures, service mocking, health check validation, TUnit with ClassDataSource. USE FOR: writing and debugging integration tests against Aspire-orchestrated services. DO NOT USE FOR: Aspire app configuration (use as

• automation-architecture

  CI/CD Pipeline-Architektur, PowerShell Module, GitHub Packages, Release-Strategien, ReleaseFlow

• azure-monitoring

  Azure Monitor, Application Insights, OpenTelemetry — metrics, traces, logs, custom Meter/Counter/Histogram, SLO-based alerts, Aspire Dashboard. USE FOR: configuring monitoring pipelines, creating alert rules, instrumenting .NET services with OpenTelemetry. DO NOT USE FOR: Aspire AppHost configuratio

• blazor-patterns

  Blazor Server, WASM, Hybrid, Static SSR patterns for .NET 10 — render mode decisions, component architecture, code-behind, state management, EventCallback, cascading values, @key, IDisposable. USE FOR: building Blazor components, choosing render modes, implementing state management. DO NOT USE FOR:

• changelog-automation

  Changelog-Automatisierung — Changelog aus Commits generieren, Keep-a-Changelog Format, Commit-Kategorisierung (feat → Added, fix → Fixed, perf → Improved, refactor → Changed). Breaking Changes mit `!` oder BREAKING CHANGE-Footer. USE FOR: generating changelogs from Conventional Commits, extracting i

• code-security-review

  Code Security Review — hardcoded secrets, IDOR, SQL injection, command injection, path traversal, CSRF, authorization flaws. USE FOR: reviewing code for security vulnerabilities, auditing endpoint authorization, validating input handling. DO NOT USE FOR: dependency vulnerabilities (dotnet-dependency

• conventional-commits

  Conventional Commits — type/scope/description format (feat, fix, docs, refactor, perf, test, chore, ci), breaking changes, scopes (.NET, CI/CD, PowerShell), SemVer mapping. USE FOR: writing commit messages, validating commit format, understanding version-bump rules. DO NOT USE FOR: release process o

• csharp-concurrency-patterns

  C# concurrency patterns \u2014 async/await, Channel<T>, SemaphoreSlim, CancellationToken, Task.WhenAll, parallel execution, producer/consumer, rate limiting. USE FOR: implementing async workflows, choosing concurrency primitives, fixing deadlocks or async anti-patterns. DO NOT USE FOR: general C# sy

• csharp-patterns

  C# 14 / .NET 10 patterns — primary constructors, collection expressions, pattern matching, records, required members, nullable reference types, file-scoped namespaces, sealed classes, naming conventions. USE FOR: writing modern C# code, applying .NET 10 language features, enforcing naming and style

• database-performance

  EF Core query performance — N+1 detection, compiled queries, split queries, query tags, AsNoTracking, index strategy (composite, filtered, covering), read/write DbContext separation. USE FOR: diagnosing slow queries, optimizing EF Core performance, designing database indexes. DO NOT USE FOR: DbConte

• documentation-patterns

  Technische Dokumentation — README, API-Docs, Changelogs, Release Notes, XML-Doc Comments, Comment-Based Help

• dotnet-aot-compat

  Native AOT and trimming compatibility for .NET — IL analyzer warnings (IL2026, IL2070, IL2067, IL2072, IL3050), IsAotCompatible, DynamicallyAccessedMembers, source-generated serialization, reflection-free DI. USE FOR: resolving IL warnings, enabling AOT compilation, making libraries trim-safe. DO NO

• dotnet-build-diagnosis

  .NET build error diagnosis — MSBuild (MSB*), NuGet (NU*), SDK (NETSDK*), compiler (CS*) errors, dependency conflicts, restore failures, Central Package Management, Directory.Build.props. USE FOR: diagnosing build failures, resolving NuGet version conflicts, fixing SDK version mismatches. DO NOT USE

• dotnet-dependency-scanning

  .NET Dependency Scanning — dotnet audit, CVE analysis, GitHub Advisory Database integration, vulnerable package detection, security patch recommendations. USE FOR: scanning dependencies for vulnerabilities, analyzing CVE severity and exploitability, recommending security patches. DO NOT USE FOR: gen

• efcore-patterns

  Entity Framework Core for .NET 10 \u2014 DbContext design, IEntityTypeConfiguration, Fluent API, migrations, seed data, query patterns (AsNoTracking, Include, projection). USE FOR: designing EF Core entities, creating migrations, writing optimized queries with Fluent API. DO NOT USE FOR: advanced qu

• git-forensics

  Git-Historia-Analyse — blame, bisect, pickaxe, Conventional Commits Validierung, Changelog-Generierung, Change Tracking

• github-actions-architecture

  GitHub Actions Architecture — Reusable Workflows, Composite Actions, Matrix-Builds, Caching-Strategien, Concurrency-Gruppen. USE FOR: architecting scalable CI/CD pipelines, optimizing build performance, managing secrets securely. DO NOT USE FOR: debugging failing workflows (use github-actions-debugg

• github-actions-debugging

  GitHub Actions debugging — failed workflow analysis, error pattern diagnosis (exit codes, permissions, rate limiting, timeouts), log downloading, matrix failure isolation, gh CLI, debug re-runs. USE FOR: analyzing why a workflow run failed, diagnosing CI performance issues, reading workflow logs. DO

• github-actions-patterns

  GitHub Actions workflow patterns — reusable workflows, composite actions, GitHub App Token, least-privilege permissions, matrix builds, caching, Quality Gate pipelines, pwsh shell. USE FOR: creating CI/CD workflows, optimizing pipeline structure, implementing GitHub Actions best practices. DO NOT US

• github-actions-security

  GitHub Actions Security — secret masking, OIDC, minimal permissions, SHA pinning, environment protection. USE FOR: securing secrets, OIDC, permissions, pinning. DO NOT USE FOR: debugging (github-actions-debugging) or patterns (github-actions-patterns).

• init-project

  Bootstrappt ein neues Repo mit CLAUDE.md, path-scoped Rules und .gitignore-Eintrag für CLAUDE.local.md. Analysiert den Stack automatisch und fragt nach Lücken.

• inline-documentation

  Inline-Dokumentation — Workarounds, Business Rules, Wann/Wann-nicht kommentieren. USE FOR: deciding when to add code comments, explaining workarounds and business rules, enforcing comment discipline. DO NOT USE FOR: method-level docs (use api-documentation) or README content (use readme-patterns).

• maui-accessibility

  .NET MAUI accessibility — SemanticProperties, AutomationProperties, screen readers (TalkBack, VoiceOver, Narrator), heading levels, programmatic focus, WCAG 2.1 compliance. USE FOR: making MAUI apps accessible, adding screen reader support, validating WCAG compliance. DO NOT USE FOR: general MAUI UI

• maui-blazor-hybrid

  Blazor Hybrid in .NET MAUI — BlazorWebView setup, JavaScript-C# interop (IJSRuntime, JSInvokable), shared Razor Class Libraries, platform-specific DI services, CSS isolation, NavigationManager. USE FOR: embedding Blazor in MAUI apps, sharing UI between MAUI and Blazor Web, implementing JS interop. D

• maui-hot-reload

  .NET MAUI Hot Reload — C# hot reload, XAML hot reload, Blazor Hybrid hot reload, dotnet watch, MetadataUpdateHandler, hot reload limitations and workarounds. USE FOR: troubleshooting hot reload failures, configuring dotnet watch for MAUI, understanding C# Hot Reload limitations. DO NOT USE FOR: gene

• maui-patterns

  .NET MAUI cross-platform patterns — MVVM (CommunityToolkit.Mvvm, ObservableProperty, RelayCommand), Shell navigation, ContentPage, CollectionView, platform-specific partial classes, state management. USE FOR: building MAUI views, implementing MVVM, configuring Shell navigation. DO NOT USE FOR: perfo

• maui-performance

  .NET MAUI performance — profiling (dotnet trace, dotnet counters), compiled bindings, CollectionView vs ListView, layout optimization, startup time, AOT for Release, PublishTrimmed, image optimization. USE FOR: profiling slow MAUI apps, optimizing layout rendering, reducing startup time, enabling tr

• minimal-api-patterns

  ASP.NET Core Minimal API for .NET 10 \u2014 MapGroup, endpoint routing, TypedResults, request/response records, IValidator<T>, OpenAPI generation. USE FOR: building REST API endpoints with Minimal API syntax, structuring endpoint groups, implementing request validation. DO NOT USE FOR: Blazor compon

• owasp-dotnet

  OWASP Top 10 for .NET and PowerShell — injection (SQL, XSS, Invoke-Expression), broken access control ([Authorize], CORS), cryptographic failures (bcrypt, no MD5/SHA1), vulnerable dependencies (dotnet audit), SecureString, TLS 1.2+. USE FOR: reviewing code for security vulnerabilities, auditing depe

• pester-patterns

  Pester 5.6.x patterns — Describe/Context/It structure, BeforeAll/AfterAll, Mock, InModuleScope, Should assertions, test helpers, GitHub CLI mocking, exit code testing. USE FOR: writing PowerShell tests, mocking commands, testing private module functions with InModuleScope. DO NOT USE FOR: .NET tests

• playwright-blazor-testing

  Blazor E2E testing with Playwright and TUnit — TUnit.Playwright, browser automation, WebApplication test fixtures, Blazor rendering waits, screenshot capture on failure. USE FOR: writing end-to-end UI tests for Blazor apps, setting up Playwright test fixtures with TUnit. DO NOT USE FOR: Blazor compo

• powershell-module-design
• powershell-module-publishing
• readme-patterns
• release-management
• release-notes-patterns
• releaseflow-coding-patterns
• releaseflow-conflict-fix
• releaseflow-domain
• releaseflow-push
• releaseflow-train-status
• security-audit
• setup-identity
• solution-layer-design
• tunit-patterns

Subagents (16)

• App Architect

  .NET application architecture — Modular Monolith, Microservices, Clean Architecture for Blazor, MAUI, ASP.NET Core. Solution structure, architecture pattern decisions, technical design. USE FOR: making architecture decisions, structuring solutions, choosing between architectural patterns. DO NOT USE

• Automation Architect

  CI/CD pipeline architecture, PowerShell module structure, GitHub Packages, release strategy, workflow run analysis. USE FOR: designing pipelines, structuring automation projects, planning release strategies, analyzing workflow run patterns. DO NOT USE FOR: writing PowerShell code (use powershell-eng

• Azure Specialist

  Azure resources, .NET Aspire integration, Application Insights, OpenTelemetry, monitoring, logging, alerting — always includes EU-sovereign alternatives with cost comparison. USE FOR: cloud infrastructure design, observability setup, Azure resource provisioning. DO NOT USE FOR: writing .NET applicat

• Code Reviewer

  Code review for .NET (C# 14) and PowerShell — architecture conformity, best practices, performance, naming, testability, maintainability. Severity levels: Blocker, Important, Improvement, Note. USE FOR: reviewing code quality, checking architecture conformity, pull request reviews. DO NOT USE FOR: s

• Commit Messenger

  Commit-Nachrichten generieren und validieren — Conventional Commits Format, Scope-Erkennung, Breaking-Change-Kennzeichnung, Issue-Referenzen. USE FOR: schnelles Generieren von Commit-Messages aus staged Changes, Validierung von Commit-Format, Batch-Commit-Messages für mehrere Änderungen. DO NOT USE

• Database Engineer

  EF Core database engineering — DbContext design, entity configuration, migrations, schema design, query optimization, seed data, index design. USE FOR: designing database schemas, creating and reviewing migrations, optimizing queries. DO NOT USE FOR: general .NET development (use dotnet-developer) o

• Documentation Agent

  Technical documentation — README, API docs, changelogs (Keep a Changelog), release notes, XML-Doc comments (C#), Comment-Based Help (PowerShell), inline documentation. USE FOR: writing READMEs, generating changelogs, documenting APIs, adding XML-Doc or Comment-Based Help. DO NOT USE FOR: writing or

• .NET Architect

  ASP.NET Core, Blazor, EF Core — Architektur-Entscheidungen, Refactoring-Pläne, Tech-Stack-Abwägungen. Gibt strukturierte Empfehlungen ohne Code zu schreiben. USE FOR: Architektur-Entscheidungen, Solution Design, .NET-Technologieauswahl. DO NOT USE FOR: Code schreiben (use dotnet-developer), Tests pl

• .NET Developer

  C# 14 / .NET 10 development — Blazor components, MAUI views, ASP.NET Core APIs, services, DTOs, dependency injection, middleware. USE FOR: writing, refactoring, and debugging .NET code across Blazor, MAUI, and ASP.NET Core. DO NOT USE FOR: database schema design (use database-engineer), architecture

• Git Forensics

  Git history analysis — blame, bisect, pickaxe, diff, change tracking, Conventional Commits validation, changelog generation. USE FOR: investigating when, why, and by whom a change was introduced, reviewing commit conventions. DO NOT USE FOR: writing code (use dotnet-developer or powershell-engineer)

• Orchestrator

  Meta-Agent fuer automatisches Routing. Analysiert Aufgaben und delegiert sofort an spezialisierte Agenten. Fuehrt NIEMALS selbst Aufgaben aus.

• Pester Tester

  PowerShell testing with Pester 5.6.x — unit tests, integration tests, infrastructure validation, mocking, InModuleScope, debug-first principle. USE FOR: writing, debugging, and analyzing PowerShell tests with Pester. DO NOT USE FOR: .NET tests (use tunit-tester), writing PowerShell production code (

• Planning Agent

  Feature planning and GitHub Issue creation — transforms vague requirements into structured GitHub Issues with milestones and user stories. 6-phase workflow: codebase analysis, feature definition, test cases, story cutting, story writing, issue creation. USE FOR: planning features, defining requireme

• PowerShell Engineer

  PowerShell Core scripts and modules, GitHub Actions workflows — strictly cross-platform (Windows, Linux, macOS). USE FOR: implementing PowerShell code, CI/CD workflows, and automation scripts. DO NOT USE FOR: PowerShell tests (use pester-tester), pipeline architecture decisions (use automation-archi

• Security Auditor

  Security analysis — dependency scanning, OWASP Top 10, NuGet vulnerability checks, code security review, severity classification, compliance reporting. USE FOR: scanning for vulnerabilities, auditing dependencies, checking security compliance. DO NOT USE FOR: code quality or architecture review (use

• TUnit Tester

  .NET testing with TUnit — dual mode: (1) Test Strategist during planning — defines executable test skeletons for GitHub Issues, co-designs test cases. (2) TDD Driver during implementation — Red-Green-Refactor cycle, writes failing tests first. Also classical post-implementation testing. Async assert

MCP servers (2)

• microsoftdocs

  connects to: https://learn.microsoft.com/api/mcp

• github

  connects to: https://api.githubcopilot.com/mcp/

Hooks (6)

• PreToolUse

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/secret-scanner.ps1"

• PreToolUse

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/destructive-command-guard.ps1"

• PreToolUse

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/releaseflow-guardrail.ps1"

• PreToolUse

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/crossplatform-lint-guard.ps1"

• PreToolUse

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/pre_tool_call.ps1"

• PostToolUse

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/post_tool_call.ps1"

Similar plugins