java-project-analyser

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Outputs a spec with user stories.

Comprehensive jOOQ DSL best practices for Kotlin/Java. Use when writing jOOQ queries, mapping results, handling transactions, or designing repository layers.

Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed. Use this when the user has already described what they want (in the current conversation, a doc, or a plan) and just needs it formalized into a spec. Also use when the user says "write a spec", "create a spec", "spec this out", or similar.

Implement a feature or fix a bug using TDD — write failing test first, then implement, refactor, verify, beautify. Use for any single code change that should be test-driven.

Verify UI/UX by running Playwright tests and reviewing screenshots. Use when you want to check that a page looks correct and the user flow works — after implementing UI changes, fixing visual bugs, or verifying an existing page. Triggers: 'check the UI', 'does this page look right', 'verify the layout', 'review screenshots', 'run UI tests'.