Skip to content

astroville/sprout / .claude/skills/groovy-stack

groovy-stack

Verified

Groovy implementation guidance for application code, Gradle logic, DSLs, and Spock-oriented testing.

Focus areas

  • Prefer readable Groovy over magic-heavy dynamic behavior.
  • Be careful with implicit coercion and runtime-only failures.
  • Keep Gradle and DSL changes focused and easy to reason about.
  • Use Spock or existing test patterns to express behavior clearly.

Guardrails

  • Do not spread custom build logic without a strong reason.
  • Avoid dynamic shortcuts that reduce maintainability.
  • Be explicit where Groovy interacts with typed JVM APIs.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall