agents-skills

Use when creating, updating, or standardizing GitHub Actions workflows for a .NET repository, especially C# libraries, NuGet packages, ABP/EAF web apps, or Angular frontends.

Bootstrap a complete production-ready agent harness in a repository — CLAUDE.md, .claude/, .devin/, skills/, rules/, ignore files, and sub-agents. Use when initializing AI agent support in a new repo, restructuring existing agent files into modern File-based Context conventions, or generating harness artifacts following Agent = Model + Harness principles. Targets Claude Code and Devin CLI only — does NOT create artifacts for OpenCode, Cursor, Gemini, Copilot or JetBrains AI. Do NOT use for building MCP servers (use building-mcp-servers).

Install and configure RTK (Rust Token Killer) — a high-performance CLI proxy that reduces LLM token consumption by 60-90%. Automatically rewrites shell commands to their rtk equivalents via hooks. Use when setting up a new dev environment or when token optimization is needed. Do NOT use when raw unfiltered output is required (use rtk proxy for that).

Apply Test-Driven Development to skill authoring — write pressure scenarios with subagents (test cases), observe baseline failures (RED), write the skill (GREEN), close loopholes through refactor cycles. Use when creating new skills, editing existing skills, or verifying skills work before deployment. Do NOT use for one-off solutions, project-specific conventions (put in AGENTS.md/CLAUDE.md), or mechanical constraints enforceable via regex/validation. Companion skills: brainstorming (for design phase), create-agent-harness (for bootstrapping agent harness in a repo).

Use when working with ABP module system, dependency injection, base classes, time handling, business exceptions, or localization patterns

Use when designing and implementing RESTful APIs with ASP.NET Core, or when applying security, error handling, documentation, testing, or performance optimization to API endpoints

Use when building Blazor applications with Microsoft Fluent UI components, setting up the library, or troubleshooting FluentUI component issues

Use when creating, updating, or managing GitHub issues — bug reports, feature requests, labels, assignments, dependencies, or workflows

Use when establishing repository structure following OpenAI harness engineering principles with AGENTS.md as index and knowledge in docs/

Use when writing modern C# code, optimizing performance-critical paths, or designing APIs with C# 12+ features

Use when identifying performance bottlenecks, optimizing queries, implementing caching, or profiling .NET applications

Use when implementing JWT authentication in .NET applications, configuring authorization policies, or securing API endpoints

Use when fixing SonarQube code quality issues automatically across any language or framework

Use when SQL queries are slow, need optimization, or when analyzing database performance bottlenecks

Use when starting feature work that needs isolation from current workspace or before executing implementation plans

Use when building or reviewing Angular UI components, routing, or service integration in ABP Angular projects. Covers generate-proxy, ListService, PermissionGuard, abpLocalization pipe, ConfirmationService, ToasterService, ConfigStateService.

Use when working with the single-layer web application template or when the project has no layered separation. Covers single project structure, feature-based file organization, and no separate Domain/Application.Contracts projects.

Use when creating or reviewing application services, DTOs, or working in the Application or Application.Contracts projects. Covers Application Services, DTOs, CRUD service, object mapping (Mapperly/AutoMapper), validation, and error handling.

Use when working with permissions, authorization, role-based access, or security in ABP projects. Covers PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, and multi-tenancy side.

Use when building or reviewing Blazor Server or WebAssembly UI components in ABP projects. Covers AbpComponentBase, AbpCrudPageBase, DataGrid, IMenuContributor, Message/Notify, Validations, and JavaScript interop.

Use when the user asks how to run ABP CLI commands, generate proxies, install libraries, or use ABP Suite. Covers generate-proxy, install-libs, add-package-ref, new-module, install-module, abp update, abp clean, and abp suite generate.

Use when designing domain layer, creating entities, repositories, or domain services in ABP projects. Covers Entities, Aggregate Roots, value objects, Repositories, Domain Services, Domain Events, and Specifications.

Use when reviewing project structure, adding new project references, or checking if a dependency direction is correct. Covers ABP project layer dependency rules, which projects can reference which, domain/application/infrastructure separation, and cross-layer violations to avoid.

Use when adding new features or entities to an ABP project. Covers step-by-step guide for adding new entities, migrations, application services, localization, permissions, and tests.

Use when working in EntityFrameworkCore projects, adding migrations, or implementing EF Core repositories. Covers DbContext, entity configuration, EfCoreRepository implementation, migrations (dotnet ef migrations add), and data seeding.

Use when working with settings, feature flags, caching, event bus, or background jobs in ABP. Covers ISettingProvider, IFeatureChecker, IDistributedCache, ILocalEventBus, IDistributedEventBus, IBackgroundJobManager, and localization resource.

Use when working with the ABP microservice solution template or inter-service communication patterns. Covers service structure, Integration Services ([IntegrationService]), inter-service HTTP proxies, distributed events with Outbox/Inbox, Entity Cache, and RabbitMQ/Redis/YARP setup.

Use when building or reviewing reusable ABP modules that will be distributed or consumed by other solutions. Covers EF Core + MongoDB dual support, virtual methods for extensibility, DbTablePrefix, module options pattern, entity extension, and separate connection string.

Use when working in MongoDB projects or implementing MongoDB repositories in ABP. Covers AbpMongoDbContext, IMongoCollection, MongoDbRepository, no migrations, embedded documents vs references, and manual UpdateAsync required.

Use when working with multi-tenant features, tenant-specific data isolation, or switching tenant context. Covers IMultiTenant interface, CurrentTenant, CurrentTenant.Change(), DataFilter.Disable(IMultiTenant), tenant resolution order, and database-per-tenant.

Use when working on MVC or Razor Pages UI in ABP projects. Covers AbpPageModel, abp tag helpers (abp-card, abp-dynamic-form, abp-modal), JavaScript abp.ajax/abp.auth/abp.notify, DataTables integration, and bundle/minification.

Use when writing or reviewing tests for application services, domain services, or repositories in ABP projects. Covers integration tests over unit tests, GetRequiredService, IDataSeedContributor, Shouldly assertions, AddAlwaysAllowAuthorization, NSubstitute mocking, and WithUnitOfWorkAsync.

Use when implementing SOLID principles in your code, applying Gang of Four (GoF) design patterns, choosing appropriate architectural patterns, refactoring code to improve design and maintainability, solving common design problems with proven patterns, or creating flexible and extensible software architecture.

Use when working with Entity Framework Core in .NET applications, needing guidance on data context design, entity design, performance optimization, migrations, querying patterns, change tracking, security, or testing strategies.

Use when setting up EF Core in a new project, optimizing query performance, managing database migrations, integrating EF Core with .NET Aspire, debugging change tracking issues, or loading multiple navigation collections efficiently (query splitting).

Use when designing EF Core models and relationships, optimizing database queries for performance, implementing proper data access patterns, handling migrations and database updates, or troubleshooting EF Core performance issues.

Turn ideas into fully formed designs and specs through collaborative dialogue. You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation; produces design doc at docs/specs/YYYY-MM-DD-<topic>-design.md and hands off to writing-plans. Do NOT use for direct implementation (proceed to writing-plans after approval), bootstrapping an agent harness in a repo (use create-agent-harness), or building MCP servers (use building-mcp-servers).

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in TypeScript (MCP SDK), Python (FastMCP), or C# (ModelContextProtocol.AspNetCore).

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject <=50 chars, body only when 'why' isn't obvious. Use when user says 'write a commit', 'commit message', 'generate commit', '/commit', or invokes /caveman-commit. Do NOT use for merge commits or automated release messages.

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or 'compress memory file'. Do NOT use for customer-facing docs or compliance artifacts.