Loading...
Loading...
Found 67 Skills
Critical Akka.NET best practices including EventStream vs DistributedPubSub, supervision strategies, error handling, Props vs DependencyResolver, work distribution patterns, and cluster/local mode abstractions for testability.
Safely refactor code to improve structure, clarity, or testability without changing intended behavior. Use when the user says "refactor it", asks to clean up a module, extract helpers, reduce duplication, or prepare code for a feature — not for product behavior changes (use fix-it) or pure test adds (use test-it). Prefer small steps with tests green between steps.
Generate a requirements-quality checklist for an OpenSpec change and run it against the proposal/design/tasks/delta — validating completeness, clarity, consistency, and testability BEFORE you approve the spec. Modeled on GitHub Spec-Kit's /checklist. Use when reviewing a spec at the human approval gate, or before launching implementation, to catch under-specified requirements early.
ALWAYS USE for test work that requires changes: write, add, generate, repair, or strengthen tests for existing code in xUnit, MSTest, NUnit, pytest, Vitest/Jest, Go, or another framework. Includes regression cases, failing or flaky tests, coverage-driven additions, and audit-then-fix requests. Focused work stays direct; broad or multi-stage work invokes test-engineer. DO NOT USE for only running tests, analysis-only audits, framework/platform migrations, a test blocked on a missing production seam (testability-obstacle), or MSTest API/configuration corrections that do not design new cases (writing-mstest-tests). Within an active test-engineer pipeline, reuse supplied guidance and do not re-enter this skill.
Use this skill when the user wants to formulate, sharpen, or stress-test a research question or hypothesis. Triggers include "help me frame my research question", "is this a good research question", "turn this observation into a hypothesis", "what should I research about X", "I have a vague idea about Y", or "is this gap worth pursuing". Handles question decomposition, testability checks, and scope calibration. Do not use for literature searching or paper reading — use literature-review or paper-analyst instead.
Review a change along one specific quality dimension — bugs, design, simplicity, maintainability, testability, test quality, type safety, contracts, operational readiness, docs, prose value, change intent, defect-class completeness after a fix, or context-file adherence. Loads exactly one dimension reference and reports findings graded by consequence; applies a caller-supplied acceptance policy when a gate verdict is requested. Use when verifying a change before merge, auditing a diff for a named concern, or running a manifest acceptance gate.
Hexagonal Architecture (Ports and Adapters) with Domain-Driven Design for TypeScript and Node.js backends built with NestJS, Express or Fastify, Prisma, TypeORM or Drizzle, and Vitest. Use it to design, implement, review, refactor or migrate TypeScript server-side code - REST APIs, use cases, aggregates, value objects, repositories, unit of work, domain events and outbox, bounded contexts, error handling, idempotency, pagination and tests per boundary. Trigger it when the project has package.json with tsconfig.json or .ts sources and the user mentions hexagonal, ports and adapters, clean architecture, DDD, layers, use cases, repositories, services, a fat controller, decoupling from NestJS, Express, Fastify or the ORM, or how to structure a Node API, even if they never say "hexagonal". Also use it for architecture, SOLID or testability reviews of TypeScript backend code. Not for other languages - use the matching hexagonal-<language> skill.
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
This skill should be used when the user asks to "implement dependency injection in Python", "use the dependency-injector library", "decouple Python components", "write testable Python services", or needs guidance on Inversion of Control, DI containers, provider types, and wiring in Python applications.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.