Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
Use when running mutation testing, killing mutants, verifying test quality, checking mutation score, or analyzing survivors after the test baseline is green.
Use when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses.
Internal procedure for the Auditor agent. Use /spec instead — it orchestrates the full pipeline. Runs Steps 5-6 (validate + update docs) with an independent context and an added coherence review. Produces an Audit Report.
Spec-driven development orchestrator. The single entry point for all spec work: creating features, fixing bugs, evolving APIs. Drives the full 6-step pipeline (spec → RED tests → implement → GREEN tests → validate → update docs) autonomously, only pausing for developer approval at gate points. Use when asked to 'add a…
Internal procedure for Step 6. Use /spec instead — it orchestrates the full pipeline. This skill contains detailed instructions for updating documentation pages after a spec is implemented or updated.
Author and maintain projects built with ADL (Agent Definition Language) - the YAML manifest format from inference-gateway/adl that adl-cli turns into a full A2A agent scaffold (Go/Rust/TypeScript). Use when working inside a generated agent project (presence of agent.yaml + .adl-ignore), when editing the manifest, when…
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Use when implementing domain logic, designing aggregates, entities, value objects, repositories, domain services, domain model design, ensuring data consistency, or when user mentions 'aggregate design', 'aggregate root', 'entity vs value object', 'domain event', 'repository pattern', 'domain service', 'data…
Use before any major initiative, architecture decision, or competitive strategy choice. Triggers on "should we build this?", "how do we compete?", "is the timing right?", or when evaluating resource allocation. Scores five parallel factors (Tao/Heaven/Earth/Command/Method) → go/caution/stop verdict.
Modern Go (Golang) development best practices (2024-2025). Use for project setup, modules, generics, concurrency, testing, HTTP/gRPC services, databases, CLI, linting, Docker, and production deployment.
Modern Python development best practices (2024-2025). Use this skill for project setup, dependency management, typing, testing, linting, async patterns, FastAPI, SQLAlchemy, Pydantic, and production deployment.
Build and evolve C# backend microservices with Genocs Library. Use for ASP.NET Core API implementation, CQRS endpoints, MongoDB repositories, messaging integration, authentication, logging, telemetry, and production hardening.
Applies authoritative Genocs NuGet package guidance from docs/-Agent-Documentation.md. Use when implementing or refactoring Genocs libraries (WebApi, Messaging, Saga, Http, Logging, Telemetry, Persistence, OpenAPI, CQRS, Auth, Outbox, RabbitMQ integrations), when the user names a Genocs package, or when agent behavior…