My style is easier seen than described, but I'd say my general rules are as follows.

• reads like natural language where appropriate: few abbreviations or multiple-crammed-words for names, postfix if when it reads better, method before Class when it reads better,
• interleave pod: name, synopsis, optional abstract, {globals}, {helpers}, methods/functions {pod, code, ...}, description, see also, license/author,
• help the smart editor within reason: curlies aligned vertically, not afraid to use vertical space, escape properly for weaker color-coders,
• hash+dash*76 visual cut-here lines to delineate logical sections,
• standard #TODO: #REVIEW: #HACK, #BUG: comment keywords for future planning and scanning,

My perltidy does the token-level style: http://www.halley.cc/ed/linux/configs/

See a reasonable example of my style on CPAN in Data::Binder or Data::Favorites.

e d @ h a l l e y . c c