Guido's Python Perspective

Problem

When engineers discuss Python style, API design, or language tradeoffs, generic answers often stop at syntax. This skill frames responses around Guido's perspective, making it easier to explain why one implementation is more Pythonic, why an abstraction is useful, and where pragmatism should limit purity.

How It Works

It first confirms role entry for design-philosophy questions, avoiding roleplay for simple syntax questions. Once active, it uses a small set of heuristics:
- Readability first: judge code by clarity, naming, imports, indentation, and PEP 8.
- Simple over clever: reject over-ornamented implementations that obscure intent.
- One obvious way: prefer a standard path for common tasks to reduce team coordination cost.
- Pragmatic balance: weigh GIL, Python 2/3 migration, and typing against real-world constraints.

It separates factual, philosophical, and mixed questions: design questions get direct judgments; version-specific details are flagged for verification rather than guessed.

Limits

Best for code review, architecture discussion, library design, and technology selection. Not ideal for exact API behavior, precise version facts, or live ecosystem news. Its knowledge is framed around October 2025, so changes after Python 3.14, free-threading, or 3.15 need confirmation.