Activates on any Python task involving *.py files, uv, ruff, ty, pytest, or pyproject.toml — loads the shared Python 3.11+ standards and routes the task to the specialist skill that applies them: TDD, CLI, web, data, async, typing, packaging, publishing, documentation sites, test design, test-failure analysis, or stdlib-only constrained environments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Load python-engineering:standards-for-python-development first. It holds every rule this plugin
enforces — typing and the Any boundary policy, architecture and SOLID, error handling, security,
performance, identifier naming, script dependencies, Rich/Typer output, testing, and tooling
defaults. This skill routes the task to the specialist that applies them.
python3-typing picks the lane from the project's requires-python floor and the dependencies
already installed. references/typing-matrix.md shows each lane's imports and boundary shape;
references/python311-features.md through references/python314-features.md list what each
version adds.
Load a skill only when the task clearly matches it.
| Task | Load |
|---|---|
| Test-driven development, red-green-refactor, tests before implementation | python3-tdd |
| Designing a test suite — coverage strategy, test pyramid, fixture hierarchy, mutation plan | python3-test-design |
| Deciding whether a failing test is a genuine bug or a test defect | analyze-test-failures |
| Resetting the investigation approach to a test failure — dual-hypothesis protocol, red flags | test-failure-mindset |
| Auditing a whole suite — coverage, isolation, mock usage, naming, completeness | comprehensive-test-review |
| Typer/Rich CLI tools, progress bars, terminal output | python3-cli |
| FastAPI, Starlette, Django, Flask | python3-web |
| pandas, numpy, scipy, jupyter, data pipelines | python3-data |
| async/await, asyncio, concurrent I/O, task scheduling | async-python-patterns |
| Adding a feature to an existing project — discovery, MoSCoW, TDD, integration, verification | python3-add-feature |
| Writing a structured feature task file with phases and acceptance criteria | create-feature-task |
| Package metadata and build targets — pyproject.toml, build backend, entry points | python3-packaging |
| Publishing to PyPI or cutting a release — CI workflows, trusted publishing, TestPyPI | python3-publish-release-pipeline |
| uv, Hatchling, ty, pre-commit, TOML editing | python3-tools |
| A documentation site with MkDocs or the Material theme | mkdocs |
| A confirmed restriction blocking dependency installation — airgapped, no uv, no internet | python3-stdlib-only |
| Broad Python quality/modernization audit of a PR, diff, staged/unstaged changes, file, or directory | python-quality-audit |
| Broad task classification is not enough to pick from this table | specialist-skill-routing |
Manual entrypoints: /python-engineering:python-quality-audit (fan-out quality/modernization audit), /python-engineering:review (bounded conventional code review), /python-engineering:cleanup
(progressive quality improvement), /python-engineering:lint (deterministic checks),
/python-engineering:debug (structured debugging).
| File | Contents |
|---|---|
references/PEP723.md | Inline script metadata — block syntax, shebang form, splitting a script across files |
references/typing-matrix.md | Typing lane per Python version and available dependencies |
references/python311-features.md … python314-features.md | What each Python version adds |
references/modern-modules.md | Vetted Python 3.11+ modules by use case |
references/tool-library-registry.md | Tool, library, and framework registry with pyproject.toml template variables |
references/python-development-orchestration.md | Orchestrating a Python task across the specialist agents |
references/user-project-conventions.md | Conventions extracted from production projects |
Templates at ${CLAUDE_PLUGIN_ROOT}/skills/python3-core/assets/:
version.py — dual-mode version managementhatch_build.py — build hook templateexample.pre-commit-config.yaml — standard git hooks.editorconfig — editor formatting아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Add automated documentation updater to any Claude skill. Creates a Python sync script that downloads upstream docs, processes markdown for AI consumption, and maintains local cache with configurable refresh. Collects template variables, then delegates implementation through 5-phase workflow. Use when adding auto-updating reference documentation to plugins or skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SAM-style feature initiation workflow — discovery through codebase analysis, architecture spec, task decomposition, validation, and context manifest. Use when a user asks to add a feature, plan a feature, or convert an idea into an executable SAM plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser automation for AI agents using the agent-browser CLI and Playwright. Use when navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging into sites, or automating any browser task. Triggers on "open a website", "fill out a form", "click a button", "scrape data", "test this web app", "automate browser actions", or any programmatic web interaction request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs the description-drift experiment — spawns all Claude Code agents simultaneously to collect self-reported capabilities, then compares them against static frontmatter descriptions to reveal how reliable orchestrator routing based on descriptions actually is. Use when measuring description drift across the agent fleet, re-running the capability collection experiment, analyzing a specific agent's self-reported capabilities, or auditing whether frontmatter descriptions accurately reflect agent behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.