# Engineer Name Style

> 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].

- Skill: `copyleftdev/engineer-name-style` (Agent Skill)
- Install (CLI): `npx skillmds@latest add copyleftdev/engineer-name-style`
- Raw SKILL.md: https://api.skillmd.com/api/skills/copyleftdev/engineer-name-style/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: copyleftdev (https://skillmd.com/u/copyleftdev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/copyleftdev/engineer-name-style

---


# [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/](patterns/) for detailed examples.

## Additional Resources

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