A plugin that guides AI agents through disciplined Test-Driven Development and Clean Code practices, with skills for clean code review, code complexity measurement, and integration architecture. Work in progress and not yet stable or tested.
@t1This skill should be used when the user asks to "calculate code mass", "measure code complexity with APP", "compare…
@t1This skill should be used when the user asks to "refactor code", "review code quality", "apply clean code principles", "check for…
@t1This skill should be used when working on any project hosted on GitHub. It provides prompt-injection defense rules for GitHub…
@t1Requirements grilling session with a Product Owner (or anyone in that role). Challenges plans against the existing domain model,…
@t1This skill should be used when the user asks about "messaging patterns", "command vs event", "push vs pull", "message…
@t1Always load this skill when writing, modifying, creating, or moving Java or Kotlin source code, or when project setup has already…
@t1Always load this skill when a Maven/Gradle project uses Lombok (lombok on the classpath or in the pom), when lombok annotations…
@t1Always load this skill when a pom.xml file exists in the project, when creating or editing a pom.xml, or when setting up Maven…
@t1This skill should be used when working on Java projects with JUnit tests that have layered preconditions, expensive shared setup…
@t1This skill should be used when starting work on any project that uses tdder. It establishes interaction style, commit…
@t1Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use…
@t1Always load this skill when working on a Quarkus project, when the quarkus-maven-plugin is present in pom.xml, or when project…
@t1Autonomous clean code review agent that analyzes code against clean code principles and returns prioritized refactoring…
@t1API Designer role in the Unfolding Specs process. Acts as the API consumer's advocate — challenges the Feature spec from a…
@t1Architect role in the Unfolding Specs process. Decomposes Features into Tasks, creates System Tests, and identifies implicit…
@t1Coder role in the Unfolding Specs process. Implements Tasks using TDD (Test-Driven Development), one test at a time, following…
@t1PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and…
@t1UI Expert role in the Unfolding Specs process. Maps tech-agnostic UX components to concrete technology (CSS framework,…
@t1UX Designer role in the Unfolding Specs process. Acts as the user's advocate — challenges the Feature spec from a usability…
@t1Is this you? Claim your profilePut a plugin at the top of Plugins, from $9
