Use when writing, reviewing, or modifying Groovy code. Applies general programming principles and design conventions. Does not cover formatting or indentation.
Use when writing, reviewing, or modifying Spock specifications. Applies conventions for structuring feature methods, mocking, and data-driven tests.
Use when writing, reviewing, or modifying Java code. Applies general programming principles and design conventions. Does not cover formatting or indentation.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A collection of Claude Code plugins for coding conventions and team-based development workflows.
Coding convention skills for JVM languages. These are non-user-invocable skills loaded automatically by agents when writing or reviewing code.
| Skill | Description |
|---|---|
groovy-coding-conventions | General Groovy programming principles and design conventions |
groovy-spock-coding-conventions | Spock test structuring, mocking, data-driven tests, and interaction verification |
java-coding-conventions | General Java programming principles and design conventions |
Team-based development workflows using coordinated agents.
| Skill | Description |
|---|---|
feature | Orchestrates feature development end-to-end. Validates the repo is clean, then launches the agent team. User-invocable. |
The feature skill spawns a four-agent team that follows a TDD workflow:
| Agent | Role |
|---|---|
architect | Lead teammate. Researches the codebase, plans interactively with the user, broadcasts requirements to the team. Loads architecture convention skills. Never writes code. |
tester | Owns the red phase. Translates the architect's requirements into failing Spock tests, gets them reviewed, then hands off to the implementer. |
implementer | Owns the green phase. Makes failing tests pass, then submits code for review. Loads coding convention skills. |
reviewer | Quality gate. Reviews test and implementation code against loaded conventions. Must approve before work proceeds. |
User Request
└─► architect (plans with user)
└─► tester (writes failing tests)
└─► reviewer (approves tests)
└─► implementer (makes tests green)
└─► reviewer (approves implementation)
Located in .claude/agents/, these are available outside the team workflow:
| Agent | Description |
|---|---|
spock-test-writer | Writes Spock unit tests with strict convention compliance. Loads groovy-coding-conventions and groovy-spock-coding-conventions skills. Iterates through implement → review → fix cycles until zero violations, then runs tests. |
npx claudepluginhub joke/claude-plugins --plugin conventionsJoke's personal workflows
Guides AI agents through disciplined coding practices. Language and build-system agnostic core with extensible language/build skills.
Comprehensive JUnit testing framework skills for Java projects with annotations, assertions, and extensions.
Skills for development standards: commit messages, code review, testing, documentation, and more. Supports 25 comprehensive skills for the full development lifecycle.
Core agents and commands required by all Developer Kit plugins
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls