Configure and operate ruff-sync to synchronize Ruff linter settings across Python projects. Use when the user wants to set up ruff-sync, sync Ruff config from an upstream source, check for configuration drift, integrate ruff-sync into CI, troubleshoot sync issues, or keep Ruff rules consistent across multiple repositories.
Handle python warnings properly by emitting them with warnings.warn, catching them in tests with catch_warnings, and translating them to errors if running in strict mode or via filterwarnings.
Use this skill to manage multiple versions of documentation for MkDocs-powered sites. Deploy new versions, update aliases (like 'latest' or 'stable'), set the default version for the site root, and manage versioned subdirectories in the deployment branch. Use this whenever the user wants to publish, version, or alias documentation, even if they don't explicitly mention "mike". Also use this when the user wants to troubleshoot or debug versioned documentation.
Build sophisticated Terminal User Interfaces (TUIs) in Python using an async, CSS-inspired framework.
Generate MkDocs documentation sites with Material theme, mkdocstrings for API docs, and versioning. Use when setting up or extending project documentation.
Systematic workflows for designing types, architecting classes, and resolving static type issues in Python 3.10. Trigger on "new class," "designing," "refactoring," or "mypy errors." Prioritizes healthy design (Generics, Protocols) over narrowing.
Create or update Agent Skills to extend capabilities for specific tasks, frameworks, or domain-specific workflows. Use this when the user asks to "add a skill," "create a tool for X," or "teach the agent how to Y."
Use this skill when you need to write declarative, readable, and maintainable assertions in Python tests. It is particularly effective for matching complex data structures, validating merged TOML configurations, and performing fuzzy matching on URLs, file paths, or object types. Use this when the user asks to "assert," "check," "verify," or "match" data in a test, even if they don't explicitly mention "dirty-equals."