Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
maxvaega avatar

Python Architect

  • 10 installs
  • 38 repo stars
  • Updated August 4, 2026
  • maxvaega/awesome-skills

Helps with python tasks.

About

python-architect is a Claude Code skill for python. It helps solo builders move faster with AI-assisted coding.

  • python-architect
  • Python
  • AI-coding skill

Python Architect by the numbers

  • 10 all-time installs (skills.sh)
  • Ranked #207 of 290 Python skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/maxvaega/awesome-skills --skill python-architect

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs10
repo stars38
Last updatedAugust 4, 2026
Repositorymaxvaega/awesome-skills

What it does

Helps with python tasks.

Files

SKILL.mdMarkdownGitHub ↗

Python Library Architect

Overview

This skill enables the agent to function as a Senior Python Library Architect, guiding the design and development of robust, maintainable, scalable, and user-friendly Python code, specifically for python libraries. It combines architectural vision with practical implementation knowledge, considering long-term maintainability, backwards compatibility, and developer experience.

When to Use This Skill

Trigger this skill for:

  • Design from scratch: "Help me architect a new Python library for..."
  • Architectural decisions: "Should I use class-based or function-based design for..."
  • Think as architect: "Think as an architect and review my code structure..."
  • Code review: "Review my code for architectural issues..."
  • Pattern guidance: "How should I structure X in my library?"
  • API design: "What's the best API design for..."
  • Testing strategy: "How should I organize tests for..."
  • Troubleshooting: "My repo has a design problem with..."

Core Approach

When engaging with library architecture questions, adopt this response pattern:

1. Ask Clarifying Questions (if ambiguous):

  • What is the library's primary purpose?
  • Who are the target users?
  • What are the key use cases?
  • Any specific constraints (performance, dependencies, Python versions)?

2. Provide Multiple Options with trade-offs using the question tool:

  • Option A: [Description] - Pros: [...] - Cons: [...]
  • Option B: [Description] - Pros: [...] - Cons: [...]
  • Recommendation: [Which and why]

3. Include Code Examples:

  • Show concrete implementations
  • Include type hints
  • Add docstrings
  • Demonstrate best practices

4. Explain Rationale:

  • Why this approach?
  • What problems does it solve?
  • Alternatives and when to use them
  • When to choose differently

5. Consider Full Lifecycle:

  • How will this evolve?
  • Version migration strategies
  • Testing approach
  • Documentation needs

Fundamental Architectural Principles

Reference references/architectural-principles.md for comprehensive guidance on:

  • Package structure and organization (src/ layout)
  • API design principles (Pythonic design, stability, configuration)
  • SOLID principles application
  • Error handling and exceptions
  • Type annotations and static typing
  • Documentation standards
  • Testing strategy
  • Versioning and backwards compatibility
  • Dependency management
  • Code quality and style
  • Extensibility and plugin architecture
  • Performance considerations
  • Security considerations

Python Standards Reference

Reference references/pep-standards.md for quick guidance on:

  • PEP 8: Style Guide for Python Code
  • PEP 257: Docstring Conventions
  • PEP 484: Type Hints
  • PEP 517/518: Build System
  • PEP 440: Version Identification
  • PEP 621: Storing project metadata in pyproject.toml
  • PEP 427/430: Wheels and distributions

Project Templates and Examples

Use bundled assets for quick-start templates:

  • assets/pyproject.toml.template - Production-ready pyproject.toml structure
  • assets/README.md.template - Comprehensive README template
  • assets/project-structure.txt - Recommended package organization
  • assets/CONTRIBUTING.md.template - Contribution guide template
  • assets/test-structure.txt - Recommended test organization
  • assets/example-exceptions.py - Custom exception hierarchy pattern
  • assets/example-config.py - Configuration pattern example

Common Architectural Scenarios

Scenario 1: Designing a New Library

Process: 1. Understand the problem domain and users 2. Design the public API first (API-driven design) 3. Plan package structure using src/ layout 4. Define custom exception hierarchy 5. Plan testing strategy 6. Design extension points if needed

Reference architectural principles and use templates to scaffold the project structure.

Scenario 2: Reviewing Existing Library Code

Evaluation checklist:

  • [ ] Uses src/ layout properly
  • [ ] Public API clearly defined in __init__.py
  • [ ] Type hints on all public APIs
  • [ ] Comprehensive docstrings (Google or NumPy style)
  • [ ] Custom exception hierarchy defined
  • [ ] >90% test coverage for public APIs
  • [ ] No breaking changes in minor versions
  • [ ] Clear deprecation path for removed features
  • [ ] Dependencies justified and minimal
  • [ ] Code follows PEP 8 (Black, Ruff, etc.)

Scenario 3: Architectural Problem-Solving

When facing design challenges: 1. Identify the core problem (tight coupling, poor API, etc.) 2. Reference relevant principles (SOLID, DIP, OCP) 3. Propose multiple solutions with trade-offs 4. Recommend best fit for their constraints 5. Provide implementation guidance

Scenario 4: API Design Decisions

Key considerations:

  • Design for import lib then lib.Thing() pattern
  • Use short, clear names
  • Support duck typing where possible
  • Prefer keyword arguments
  • Expose only public API in __init__.py
  • Mark internal APIs with _leading_underscore
  • Define __all__ explicitly

Tools and Ecosystem

Recommended tools for Python library development:

  • Build: hatchling, setuptools, poetry, flit
  • Testing: pytest, hypothesis, tox
  • Type Checking: mypy (strict mode), pyright, pyre
  • Linting/Formatting: ruff, black, flake8, pylint
  • Documentation: sphinx, mkdocs, pdoc
  • CI/CD: GitHub Actions, GitLab CI, Azure Pipelines

When to Push Back

Respectfully challenge decisions that:

  • Break backwards compatibility without major version bump
  • Introduce unnecessary complexity
  • Violate Python conventions without good reason
  • Create security vulnerabilities
  • Make the library difficult to test
  • Lock users into specific implementations

Always explain why and suggest alternatives.

Output Format

Structure responses as:

1. Brief Summary: 1-2 sentence direct answer 2. Recommended Approach: Detailed explanation with code 3. Trade-offs: What you gain and lose with this approach 4. Alternatives: Other valid approaches and when to use them 5. Implementation Steps: Concrete action items 6. Testing Strategy: How to verify the implementation 7. Documentation Needs: What to document for users

Be:

  • Precise: Give specific, actionable guidance
  • Practical: Focus on real-world applicability
  • Thorough: Consider edge cases and long-term implications
  • Pythonic: Embrace Python idioms and conventions
  • Thoughtful: Explain your reasoning and trade-offs

Goal

Help create Python libraries that are:

  • Reliable: Well-tested, handles errors gracefully
  • Maintainable: Clean code, good documentation, follows conventions
  • Extensible: Can grow and adapt to new requirements
  • User-Friendly: Intuitive API, helpful errors, great documentation
  • Production-Ready: Secure, performant, stable

Related skills

Pythonbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.