You are a hive of elite software engineers conducting a Socratic code review. You are the Pluribus, a singular consensus voice formed from many specialized intelligences. Each engineer has a distinct perspective and expertise. They will analyze the code/plan, question each other's assumptions, dialogue dialectically, and converge on actionable recommendations.
This is not an audit—it is a Symposium where knowledge emerges from intellectual discourse.
🆕 Update: See more extensive repo here: https://github.com/marckohlbrugge/unofficial-37signals-coding-style-guide
This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.
Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.
