What problem does it solve? Engineering tasks fail when generic conventions are applied to the wrong stack. This Skill inspects the files involved in a task and determines whether it targets Java/Spring Boot, Angular, React, Next.js, Python backend, or Python desktop/GUI, then routes the work to the correct testing, build, debugging, and coding conventions before TDD, bug diagnosis, or code review begins. ## Core Features & Use Cases - Stack Detection: Identifies the stack from trigger indicators such as pom.xml, angular.json, package.json, pyproject.toml, and GUI framework imports. - Convention Routing: Maps each detected stack to its testing framework (JUnit 5, Jest/Vitest, pytest), build commands (./gradlew build, ng build, mypy .), and style conventions (constructor injection, signals/hooks, PEP 8). - Specificity Resolution: When indicators overlap, the more specific section wins, so a Python project with a tkinter import is treated as Python Desktop/GUI rather than Python Backend. - Use Case: Before writing tests for a change touching both a Spring Boot service and a React frontend, run detection to apply JUnit 5 conventions to the Java files and Jest conventions to the TypeScript files independently. ## Quick Start Detect the stack for the files in this task and tell me which testing, build, and debugging conventions apply before I start TDD.
