python_engineering
Python Engineering Skill Policy
Code is Mechanism, Prompt is Policy
Python Standards (v2.0 - Modern)
When writing or editing Python code:
- State Management - Use
StrEnuminstead of magic strings - Control Flow - Prefer
match/caseover complexif/elifchains - Type Safety - Use
@overridefor inherited methods and new generic syntaxclass Foo[T] - Concurrency - Use
asyncio.TaskGroupinstead ofgather - Standards - Follow PEP 8, 4 spaces, and Google style docstrings
See lang-python-modern.md for complete standards.
Tools Available
lint_python_style- Check code with ruff/flake8 (Configured for py313)run_pytest- Execute test suitecheck_types- Run pyright type checkingformat_python- Format code with ruff/black
More from tao3k/omni-dev-fusion
crawl4ai
Use when crawling web pages, extracting markdown content, or scraping website data with intelligent chunking and skeleton planning. Use when the user provides a URL or link to fetch or crawl.
50software_engineering
Use when analyzing project architecture, exploring codebase structure, understanding system design, reviewing code patterns, or navigating modular components.
18code_tools
Use when searching code by structure or meaning, analyzing code patterns, finding class or function definitions, or exploring codebase architecture.
16rust_engineering
Use when analyzing Rust project structure, managing Cargo dependencies, building and testing Rust projects, or generating Rust code.
16git
Use when committing code, managing branches, pushing to remote, creating pull requests, or performing version control operations. Conforms to docs/reference/skill-routing-value-standard.md.
15researcher
Use when analyzing repositories, conducting deep research on codebases, performing architecture reviews, or exploring large projects from a git URL.
15