Back when I started learning Moose I coded up a bunch of the classic 'Gang of Four' design patterns as I was exploring the framework. Originally I intended to release them as part of a blog series which I never got around to doing.
Since then I've had a love/hate thing going with design patterns. Although some are clearly useful and rationally translated to dynamic languages like Perl, it often feels like some of the problems the classic patterns are trying to solve are more specific to the static language domain. As a result most of the design pattern implementations I have seen for Perl and related dynamic languages seem to suffer from, to put it nicely, 'Java-itis' :)
On the other hand if the implementations are not awesome, perhaps those problems could be solve with a more dynamic language approach. I'm not 100% sure what that might be, but I've tossed some code into the ring on Github, with the hope of generating a conversation. I'm starting with the Chain of Responsibility pattern, which is probably one of the more useful ones I've reached for time and again. Although not currently intended for CPAN, I am writing these as CPAN modules, which is the normal practice for Perl project.
From my perspective I am thinking 1) a conversation about what design patterns reinvented for modern Perl would look like; 2) create a repository that people can look at when creating their own code and 3) examples of well understood code that can serve as a useful bit of education and advocacy (for example Wikipedia design pattern entries lack a lot of solid Perl examples.