cc-python-project-standard
/cc-python-project-standard
Use when Python package layout, pyproject conventions, typing, import-time behavior, dependency boundaries or repository-wide Python quality checks need design or review.
- Author
- bovinphang ↗
- Repository
- backend-craft ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 9
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: examples/engineering/resource_boundary.py, examples/engineering/test_resource_boundary.py
What it does and when to use it
Use when Python package layout, pyproject conventions, typing, import-time behavior, dependency boundaries or repository-wide Python quality checks need design or review.
Original author description
Use when Python package layout, pyproject conventions, typing, import-time behavior, dependency boundaries or repository-wide Python quality checks need design or review.
How it works
- Apply the workflow
- Task boundary
- Engineering practices
SKILL.md preview
--- name: cc-python-project-standard description: "Use when Python package layout, pyproject conventions, typing, import-time behavior, dependency boundaries or repository-wide Python quality checks need design or review." --- # Python project engineering Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language. Read pyproject, lock/environment conventions, supported Python versions and current package layout. Do not mix new installers or replace the environment implicitly. ## Apply the workflow 1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now. 2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change. 3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result. 4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only. ## Task boundary Focused event-loop cancellation or blocking-I/O problems belong to the async specialty. ## Engineering practices Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.
Files in this package (9)
- SKILL.md 2 KB
- examples/engineering/README.md 1 KB
- examples/engineering/resource_boundary.py 1 KB
- examples/engineering/test_resource_boundary.py 2 KB
- references/engineering-practices.md 4 KB
- references/practice.md 2 KB
- references/common/engineering-practices.md 12 KB
- references/common/engineering-practices.rules.json 2 KB
- references/common/engineering-practices.sources.json 16 KB
Versions
The database has no other skills named cc-python-project-standard.
Database snapshot: 13.11.2026 · package version c1dfe27d7740 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100python-conventions
Enforce Python tooling conventions for uv, ty, Ruff, pytest, and pyproject.toml. Use when working on .py files or Python project config. NOT for JS/TS, shell scripts, CI design, profiling, or test architecture. - 90cc-go-project-standard
Use when Go module/workspace organization, package ownership, error and context conventions, dependency boundaries or engineering validation need design or review. - 90cc-java-project-standard
Use when Java package/module structure, build-tool conventions, application boundaries, exceptions, persistence ownership or repository-wide Java engineering needs design or review. - 100write-python
Python project conventions for this codebase. Use when creating a new Python project, configuring Python tools (ruff, pyright, ty, pytest, bandit, vulture), writing or reviewing pyproject.toml, setting up Nx targets for Python, or asked about Python tooling setup, uv, or the… - 100python-helper
Current Python development guidance for versions, uv and pip, packaging, typing, asyncio, pytest, Ruff, security, and runtime boundaries. Use when writing or reviewing Python, pyproject.toml, Python CI, tests, dependency workflows, or Python upgrades. - 91python-repository-layout
Python repository layout. Use for Literate AI workflow tasks.