writing-python
Python Development (3.14+)
Core Philosophy
-
Stdlib and Mature Libraries First
- Always prefer Python stdlib solutions
- External deps only when stdlib insufficient
- Prefer dataclasses over attrs, pathlib over os.path
-
Type Hints Everywhere (No Any)
- Python 3.14 has lazy annotations by default
- Use Protocol for structural typing (duck typing)
- Avoid Any—use concrete types or generics
-
Protocol Over ABC
- Protocol for implicit interface satisfaction
- ABC only when runtime isinstance() needed
- Protocols are more flexible and Pythonic
More from alexei-led/claude-code-config
brainstorming-ideas
Turn ideas into designs through collaborative dialogue. Use when user wants to brainstorm, design features, explore approaches, or think through implementation before coding.
19refactoring-code
Batch refactoring via MorphLLM edit_file. Use for "refactor across files", "batch rename", "update pattern everywhere", large files (500+ lines), or 5+ edits in same file.
11testing-e2e
E2E testing with Playwright MCP for browser automation, test generation, and UI testing. Use when discussing E2E tests, Playwright, browser testing, UI automation, visual testing, or accessibility testing. Supports TypeScript tests and Go/HTMX web applications.
10looking-up-docs
Library documentation via Context7. Use for API references, code examples, framework docs.
7writing-typescript
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or discussing TS patterns. Emphasizes strict typing, composition, and modern tooling (bun/vite).
7fixing-code
Fix ALL issues via parallel agents with zero tolerance quality enforcement. Use when user says "fix", "fix issues", "fix errors", "fix all", "fix bugs", "fix lint", "fix tests", or wants to resolve code problems.
6