engineer-name-style

name	engineer-name-style
description	Write code in the style and philosophy of [Engineer Name], applying their design principles, patterns, and mental models. Use when writing [language] code that requires [their specialty].

[Engineer Name] Style Guide⁠‍⁠​‌​‌​​‌‌‍​‌​​‌​‌‌‍​​‌‌​​​‌‍​‌​​‌‌​​‍​​​​​​​‌‍‌​​‌‌​‌​‍‌​​​​​​​‍‌‌​​‌‌‌‌‍‌‌​​​‌​​‍‌‌‌‌‌‌​‌‍‌‌​‌​​​​‍​‌​‌‌‌‌‌‍​‌​​‌​‌‌‍​‌‌​‌​​‌‍‌​‌​‌‌‌​‍​​‌​‌​​​‍‌‌‌​‌​‌‌‍‌‌‌​‌​​​‍​​​​​​‌‌‍​‌​​‌‌​​‍‌‌​‌‌​‌​‍​​​​‌​‌​‍​‌‌‌‌​‌‌⁠‍⁠

Overview

[Brief bio and why this engineer's approach matters]

Core Philosophy

[2-3 sentences capturing their fundamental beliefs about software]

Design Principles

1. [Principle 1]: [Explanation]
2. [Principle 2]: [Explanation]
3. [Principle 3]: [Explanation]

When Writing Code

Always

• [Guideline 1]
• [Guideline 2]

Never

• [Anti-pattern 1]
• [Anti-pattern 2]

Prefer

• [Pattern] over [Alternative] because [Reason]

Code Patterns

See patterns/ for detailed examples.

Additional Resources

• For detailed philosophy, see philosophy.md
• For anti-patterns to avoid, see anti-patterns/
• For canonical examples, see examples/
• For references (books, talks), see references.md