Communitygithub.com

Quarkus TDD

Testgetriebene Entwicklung für Quarkus 3.x LTS mit JUnit 5, Mockito, REST Assured, Camel-Tests und JaCoCo. Verwenden beim Hinzufügen von Funktionen, Beheben von Fehlern oder Refactoring von ereignisgesteuerten Diensten.

Was ist Quarkus TDD?

Diese Skill-Anleitung beschreibt eine testgetriebene Entwicklungsumgebung (TDD) für Quarkus 3.x Dienste, die Codeabdeckung von 80% oder mehr (Unit- und Integrationstests) anstrebt. Sie ist speziell für ereignisgesteuerte Architekturen mit Apache Camel optimiert. Der Workflow folgt dem klassischen TDD-Zyklus: Tests zuerst schreiben, minimale Implementierung, Refactoring mit grünen Tests und Überprüfung der Abdeckung mit JaCoCo. Die Anleitung enthält detaillierte Codebeispiele für Unit-Tests mit `@Nested`-Klassen und `@DisplayName`, Camel-Routentests mit `MockEndpoint` und `AdviceWith`, sowie Tests für Ereignisdienste und `CompletableFuture`-Operationen. Besonderer Wert wird auf klare Testbenennung (given/when/then), das AAA-Pattern und die Überprüfung von Interaktionen mit Mockito gelegt. Die Anleitung ist für Entwickler geeignet, die neue Funktionen implementieren, Fehler beheben oder bestehenden Code refaktorieren möchten.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/ECC/tree/main/skills/quarkus-tdd

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Quarkus TDD Workflow

TDD-Anleitung für Quarkus 3.x Dienste mit 80%+ Abdeckung (Unit + Integration). Optimiert für ereignisgesteuerte Architekturen mit Apache Camel.

Wann verwenden

  • Neue Funktionen oder REST-Endpunkte
  • Fehlerbehebungen oder Refactorings
  • Hinzufügen von Datenzugriffslogik, Sicherheitsregeln oder reaktiven Streams
  • Testen von Apache Camel-Routen und Ereignisbehandlern
  • Testen von ereignisgesteuerten Diensten mit RabbitMQ
  • Testen von bedingten Ablauflogiken
  • Validierung von CompletableFuture-asynchronen Operationen
  • Testen der LogContext-Propagation

Arbeitsablauf

  1. Schreibe zuerst Tests (sie sollten fehlschlagen)
  2. Implementiere minimalen Code, um sie zu bestehen
  3. Refaktoriere mit grünen Tests
  4. Erzwinge Abdeckung mit JaCoCo (80%+ Ziel)

Unit-Tests mit @Nested-Organisation

Befolgen Sie diesen strukturierten Ansatz für umfassende, lesbare Tests:

@ExtendWith(MockitoExtension.class)
@DisplayName("OrderService Unit Tests")
class OrderServiceTest {

  @Mock
  private OrderRepository orderRepository;

  @Mock
  private EventService eventService;

  @Mock
  private FulfillmentPublisher fulfillmentPublisher;

  @InjectMocks
  private OrderService orderService;

  private CreateOrderCommand validCommand;

  @BeforeEach
  void setUp() {
    validCommand = new CreateOrderCommand(
        "customer-123",
        List.of(new OrderLine("sku-123", 2))
    );
  }

  @Nested
  @DisplayName("Tests für createOrder")
  class CreateOrder {

    @Test
    @DisplayName("Sollte Bestellung speichern und Fulfillment-Ereignis veröffentlichen")
    void givenValidCommand_whenCreateOrder_thenPersistsAndPublishes() {
      // ARRANGE
      doNothing().when(orderRepository).persist(any(Order.class));

      // ACT
      OrderReceipt receipt = orderService.createOrder(validCommand);

      // ASSERT
      assertThat(receipt).isNotNull();
      assertThat(receipt.customerId()).isEqualTo("customer-123");
      verify(orderRepository).persist(any(Order.class));
      verify(fulfillmentPublisher).publishAsync(receipt);
      verify(eventService).createSuccessEvent(receipt, "ORDER_CREATED");
    }

    @Test
    @DisplayName("Sollte fehlende Kunden-ID ablehnen")
    void givenMissingCustomerId_whenCreateOrder_thenThrowsBadRequest() {
      // ARRANGE
      CreateOrderCommand invalid = new CreateOrderCommand("", validCommand.lines());

      // ACT & ASSERT
      WebApplicationException exception = assertThrows(
          WebApplicationException.class,
          () -> orderService.createOrder(invalid)
      );

      assertThat(exception.getResponse().getStatus()).isEqualTo(400);
      verify(orderRepository, never()).persist(any(Order.class));
      verify(fulfillmentPublisher, never()).publishAsync(any());
    }

    @Test
    @DisplayName("Sollte Fehlerereignis aufzeichnen, wenn Persistenz fehlschlägt")
    void givenPersistenceFailure_whenCreateOrder_thenRecordsErrorEvent() {
      // ARRANGE
      doThrow(new PersistenceException("Datenbank nicht verfügbar"))
          .when(orderRepository).persist(any(Order.class));

      // ACT & ASSERT
      PersistenceException exception = assertThrows(
          PersistenceException.class,
          () -> orderService.createOrder(validCommand)
      );

      assertThat(exception.getMessage()).contains("Datenbank nicht verfügbar");
      verify(eventService).createErrorEvent(
          eq(validCommand),
          eq("ORDER_CREATE_FAILED"),
          contains("Datenbank nicht verfügbar")
      );
      verify(fulfillmentPublisher, never()).publishAsync(any());
    }

    @Test
    @DisplayName("Sollte null-Befehle ablehnen")
    void givenNullCommand_whenCreateOrder_thenThrowsNullPointerException() {
      // ACT & ASSERT
      assertThrows(
          NullPointerException.class,
          () -> orderService.createOrder(null)
      );

      verify(orderRepository, never()).persist(any(Order.class));
    }
  }
}

Wichtige Testmuster

  1. @Nested-Klassen: Tests nach zu testender Methode gruppieren
  2. @DisplayName: Lesbare Testbeschreibungen für Testberichte bereitstellen
  3. Namenskonvention: givenX_whenY_thenZ für Klarheit
  4. AAA-Muster: Explizite // ARRANGE, // ACT, // ASSERT Kommentare
  5. @BeforeEach: Gemeinsame Testdaten einrichten, um Duplikate zu reduzieren
  6. assertDoesNotThrow: Erfolgsszenarien testen, ohne Ausnahmen abzufangen
  7. assertThrows: Ausnahmeszenarien mit Nachrichtenvalidierung mit AssertJ testen
  8. Umfassende Abdeckung: Happy Paths, null-Eingaben, Randfälle, Ausnahmen testen
  9. Interaktionen überprüfen: Mockito verify() verwenden, um korrekte Methodenaufrufe sicherzustellen
  10. Nie überprüfen: never() verwenden, um sicherzustellen, dass Methoden in Fehlerszenarien NICHT aufgerufen werden

Testen von Camel-Routen

@QuarkusTest
@DisplayName("Business Rules Camel Route Tests")
class BusinessRulesRouteTest {

  @Inject
  CamelContext camelContext;

  @Inject
  ProducerTemplate producerTemplate;

  @InjectMock
  EventService eventService;

  @InjectMock
  DocumentValidator documentValidator;

  private BusinessRulesPayload testPayload;

  @BeforeEach
  void setUp() {
    // ARRANGE - Testdaten
    testPayload = new BusinessRulesPayload();
    testPayload.setDocumentId(1L);
    testPayload.setFlowProfile(FlowProfile.BASIC);
  }

  @Nested
  @DisplayName("Tests für business-rules-publisher Route")
  class BusinessRulesPublisher {

    @Test
    @DisplayName("Sollte Nachricht erfolgreich an RabbitMQ veröffentlichen")
    void givenValidPayload_whenPublish_thenMessageSentToQueue() throws Exception {
      // ARRANGE
      MockEndpoint mockRabbitMQ = camelContext.getEndpoint("mock:rabbitmq", MockEndpoint.class);
      mockRabbitMQ.expectedMessageCount(1);

      // Ersetzen des echten Endpunkts durch Mock für Tests
      camelContext.getRouteController().stopRoute("business-rules-publisher");
      AdviceWith.adviceWith(camelContext, "business-rules-publisher", advice -> {
        advice.replaceFromWith("direct:business-rules-publisher");
        advice.weaveByToString(".*spring-rabbitmq.*").replace().to("mock:rabbitmq");
      });
      camelContext.getRouteController().startRoute("business-rules-publisher");

      // ACT
      producerTemplate.sendBody("direct:business-rules-publisher", testPayload);

      // ASSERT — body ist ein JSON-String nach .marshal().json(JsonLibrary.Jackson)
      mockRabbitMQ.assertIsSatisfied(5000);

      assertThat(mockRabbitMQ.getExchanges()).hasSize(1);
      String body = mockRabbitMQ.getExchanges().get(0).getIn().getBody(String.class);
      assertThat(body).contains("\"documentId\":1");
    }

    @Test
    @DisplayName("Sollte Marshalling zu JSON handhaben")
    void givenPayload_whenPublish_thenMarshalledToJson() throws Exception {
      // ARRANGE
      MockEndpoint mockMarshal = new MockEndpoint("mock:marshal");
      camelContext.addEndpoint("mock:marshal", mockMarshal);
      mockMarshal.expectedMessageCount(1);

      camelContext.getRouteController().stopRoute("business-rules-publisher");
      AdviceWith.adviceWith(camelContext, "business-rules-publisher", advice -> {
        advice.weaveAddLast().to("mock:marshal");
      });
      camelContext.getRouteController().startRoute("business-rules-publisher");

      // ACT
      producerTemplate.sendBody("direct:business-rules-publisher", testPayload);

      // ASSERT
      mockMarshal.assertIsSatisfied(5000);

      String body = mockMarshal.getExchanges().get(0).getIn().getBody(String.class);
      assertThat(body).contains("\"documentId\":1");
      assertThat(body).contains("\"flowProfile\":\"BASIC\"");
    }
  }

  @Nested
  @DisplayName("Tests für document-processing Route")
  class DocumentProcessing {

    @Test
    @DisplayName("Sollte Rechnung an den korrekten Prozessor weiterleiten")
    void givenInvoiceType_whenProcess_thenRoutesToInvoiceProcessor() throws Exception {
      // ARRANGE
      MockEndpoint mockInvoice = camelContext.getEndpoint("mock:invoice", MockEndpoint.class);
      mockInvoice.expectedMessageCount(1);

      camelContext.getRouteController().stopRoute("document-processing");
      AdviceWith.adviceWith(camelContext, "document-processing", advice -> {
        advice.weaveByToString(".*direct:process-invoice.*").replace().to("mock:invoice");
      });
      camelContext.getRouteController().startRoute("document-processing");

      // ACT
      producerTemplate.sendBodyAndHeader("direct:process-document",
          testPayload, "documentType", "INVOICE");

      // ASSERT
      mockInvoice.assertIsSatisfied(5000);
    }

    @Test
    @DisplayName("Sollte Validierungsfehler elegant behandeln")
    void givenValidationError_whenProcess_thenRoutesToErrorHandler() throws Exception {
      // ARRANGE
      MockEndpoint mockError = camelContext.getEndpoint("mock:error", MockEndpoint.class);
      mockError.expectedMessageCount(1);

      camelContext.getRouteController().stopRoute("document-processing");
      AdviceWith.adviceWith(camelContext, "document-processing", advice -> {
        advice.weaveByToString(".*direct:validation-error-handler.*")
            .replace().to("mock:error");
      });
      camelContext.getRouteController().startRoute("document-processing");

      // Mock-Validator-Bean zum Auslösen einer Exception
      when(documentValidator.validate(any())).thenThrow(new ValidationException("Ungültiges Dokument"));

      // ACT
      producerTemplate.sendBody("direct:process-document", testPayload);

      // ASSERT
      mockError.assertIsSatisfied(5000);

      Exception exception = mockError.getExchanges().get(0).getException();
      assertThat(exception).isInstanceOf(ValidationException.class);
      assertThat(exception.getMessage()).contains("Ungültiges Dokument");
    }
  }
}

Testen von Ereignisdiensten

@ExtendWith(MockitoExtension.class)
@DisplayName("EventService Unit Tests")
class EventServiceTest {

  @Mock
  private EventRepository eventRepository;

  @Mock
  private ObjectMapper objectMapper;

  @InjectMocks
  private EventService eventService;

  private BusinessRulesPayload testPayload;

  @BeforeEach
  void setUp() {
    // ARRANGE
    testPayload = new BusinessRulesPayload();
    testPayload.setDocumentId(1L);
  }

  @Nested
  @DisplayName("Tests für createSuccessEvent")
  class CreateSuccessEvent {

    @Test
    @DisplayName("Sollte Erfolgsereignis mit korrekten Attributen erstellen")
    void givenValidPayload_whenCreateSuccessEvent_thenEventPersisted() throws Exception {
      // ARRANGE
      when(objectMapper.writeValueAsString(testPayload)).thenReturn("{\"documentId\":1}");

      // ACT
      assertDoesNotThrow(() ->
          eventService.createSuccessEvent(testPayload, "DOCUMENT_PROCESSED"));

      // ASSERT
      verify(eventRepository).persist(argThat(event ->
          event.getType().equals("DOCUMENT_PROCESSED") &&
          event.getStatus() == EventStatus.SUCCESS &&
          event.getPayload().equals("{\"documentId\":1}") &&
          event.getTimestamp() != null
      ));
    }

    @Test
    @DisplayName("Sollte Exception werfen, wenn Payload null ist")
    void givenNullPayload_whenCreateSuccessEvent_thenThrowsException() {
      // ARRANGE
      Object nullPayload = null;

      // ACT & ASSERT
      NullPointerException exception = assertThrows(
          NullPointerException.class,
          () -> eventService.createSuccessEvent(nullPayload, "EVENT_TYPE")
      );

      assertThat(exception.getMessage()).isEqualTo("Payload darf nicht null sein");
      verify(eventRepository, never()).persist(any());
    }
  }

  @Nested
  @DisplayName("Tests für createErrorEvent")
  class CreateErrorEvent {

    @Test
    @DisplayName("Sollte Fehlerereignis mit Fehlermeldung erstellen")
    void givenError_whenCreateErrorEvent_thenEventPersistedWithMessage() throws Exception {
      // ARRANGE
      String errorMessage = "Verarbeitung fehlgeschlagen";
      when(objectMapper.writeValueAsString(testPayload)).thenReturn("{\"documentId\":1}");

      // ACT
      assertDoesNotThrow(() ->
          eventService.createErrorEvent(testPayload, "PROCESSING_ERROR", errorMessage));

      // ASSERT
      verify(eventRepository).persist(argThat(event ->
          event.getType().equals("PROCESSING_ERROR") &&
          event.getStatus() == EventStatus.ERROR &&
          event.getErrorMessage().equals(errorMessage) &&
          event.getPayload().equals("{\"documentId\":1}")
      ));
    }

    @ParameterizedTest
    @DisplayName("Sollte ungültige Fehlermeldungen ablehnen")
    @ValueSource(strings = {"", " "})
    void givenBlankErrorMessage_whenCreateErrorEvent_thenThrowsException(String blankMessage) {
      // ACT & ASSERT
      IllegalArgumentException exception = assertThrows(
          IllegalArgumentException.class,
          () -> eventService.createErrorEvent(testPayload, "ERROR", blankMessage)
      );

      assertThat(exception.getMessage()).contains("Fehlermeldung darf nicht leer sein");
    }
  }
}

Testen von CompletableFuture

@ExtendWith(MockitoExtension.class)
@DisplayName("FileStorageService Unit Tests")
class FileStorageServiceTest {

  @Mock
  private S3Client s3Client;

  @Mock
  private ExecutorService executorService;

  @InjectMocks
  private FileStorageService fileStorageService;

  private InputStream testInputStream;
  private LogContext testLogContext;

  @BeforeEach
  void setUp() {
    // ARRANGE
    testInputStream = new ByteArrayInputStream("Testinhalt".getBytes());
    testLogContext = new LogContext();
    testLogContext.put("traceId", "trace-123");
  }

  @Nested
  @DisplayName("Tests für uploadOriginalFile")
  class UploadOriginalFile {

    @Test
    @DisplayName("Sollte Datei erfolgreich hochladen und Dokumenteninfo zurückgeben")
    void givenValidFile_whenUpload_thenReturnsDocumentInfo() throws Exception {
      // ARRANGE
      doAnswer(invocation -> {
        ((Runnable) invocation.getArgument(0)).run();
        return null;
      }).when(executorService).execute(any(Runnable.class));

      when(s3Client.putObject(any(PutObjectRequest.class), any(RequestBody.class)))
          .thenReturn(PutObjectResponse.builder().build());

      // ACT
      CompletableFuture<StoredDocumentInfo> future = fileStorageService.uploadOriginalFile(
          testInputStream, testLogContext);

      // ASSERT
      StoredDocumentInfo info = future.get(5, TimeUnit.SECONDS);
      assertThat(info).isNotNull();
      assertThat(info.getFileName()).isEqualTo("original.pdf");
      assertThat(info.getSize()).isEqualTo(1024L);
    }

    @Test
    @DisplayName("Sollte null-Stream ablehnen")
    void givenNullInputStream_whenUpload_thenThrowsException() throws Exception {
      // ARRANGE
      InputStream nullStream = null;

      // ACT & ASSERT
      assertThrows(NullPointerException.class, () ->
          fileStorageService.uploadOriginalFile(nullStream, testLogContext).get(5, TimeUnit.SECONDS));
    }

    @Test
    @DisplayName("Sollte LogContext korrekt propagieren")
    void givenLogContext_whenUpload_thenContextPropagatedToAsyncTask() throws Exception {
      // ARRANGE
      final AtomicBoolean contextChecked = new AtomicBoolean(false);
      doAnswer(invocation -> {
        Runnable task = invocation.getArgument(0);
        assertThat(LogContext.get()).isNotNull();
        assertThat(LogContext.get().get("traceId")).isEqualTo("trace-123");
        contextChecked.set(true);
        task.run();
        return null;
      }).when(executorService).execute(any(Runnable.class));

      when(s3Client.putObject(any(PutObjectRequest.class), any(RequestBody.class)))
          .thenReturn(PutObjectResponse.builder().build());

      // ACT
      fileStorageService.uploadOriginalFile(testInputStream, testLogContext).get(5, TimeUnit.SECONDS);

      // ASSERT
      assertThat(contextChecked.get()).isTrue();
    }

    @Test
    @DisplayName("Sollte Fehler mit vollständigen Kontextdetails protokollieren")
    void givenS3Failure_whenUpload_thenLogIncludesContext() throws Exception {
      // ARRANGE
      doAnswer(invocation -> {
        Runnable task = invocation.getArgument(0);
        task.run();
        return null;
      }).when(executorService).execute(any(Runnable.class));

      when(s3Client.putObject(any(PutObjectRequest.class), any(RequestBody.class)))
          .thenThrow(S3Exception.builder().statusCode(500).build());

      // ACT & ASSERT
      ExecutionException exception = assertThrows(ExecutionException.class, () ->
          fileStorageService.uploadOriginalFile(testInputStream, testLogContext).get(5, TimeUnit.SECONDS));

      assertThat(exception.getCause()).isInstanceOf(S3Exception.class);
    }
  }
}

JaCoCo-Konfiguration

<plugin>
  <groupId>org.jacoco</groupId>
  <artifactId>jacoco-maven-plugin</artifactId>
  <version>0.8.11</version>
  <executions>
    <execution>
      <goals>
        <goal>prepare-agent</goal>
      </goals>
    </execution>
    <execution>
      <id>report</id>
      <phase>test</phase>
      <goals>
        <goal>report</goal>
      </goals>
    </execution>
    <execution>
      <id>check</id>
      <phase>verify</phase>
      <goals>
        <goal>check</goal>
      </goals>
      <configuration>
        <rules>
          <rule>
            <element>BUNDLE</element>
            <limits>
              <limit>
                <counter>INSTRUCTION</counter>
                <value>COVEREDRATIO</value>
                <minimum>0.80</minimum>
              </limit>
            </limits>
          </rule>
        </rules>
      </configuration>
    </execution>
  </executions>
</plugin>

Wichtige JaCoCo-Einstellungen

  • prepare-agent: Fügt JaCoCo-Agent zum Start hinzu
  • report: Erzeugt HTML/XML-Berichte in target/jacoco-ut/
  • check: Erzwingt 80%+ Abdeckung während der verify-Phase
  • Ausschlüsse: Fügen Sie generierte Klassen und Testinfrastruktur mit <excludes> hinzu

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

affaan-m/ECC

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

affaan-m/fal-ai-media

Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.

affaan-m/manim-video

日本語翻訳:このファイルは manim-video 用の日本語翻訳が必要です

affaan-m/remotion-video-creation

Remotion のベストプラクティス - React で動画を作成する。3D、アニメーション、音声、字幕、チャート、トランジションなどをカバーするドメイン固有の29のルール。

affaan-m/video-editing

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

agent-self-evaluation

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.

ai-regression-testing

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.

android-clean-architecture

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Verwandte Skills