원클릭으로
python-style
Python code style, typing, and project conventions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Python code style, typing, and project conventions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | python-style |
| description | Python code style, typing, and project conventions. |
Use type hints in all function signatures, including return types. Prefer concrete types over Any; reach for Protocol when you really need duck typing. Run mypy or pyright in CI.
Use dataclasses for simple data containers; reach for Pydantic when you need runtime validation at a system boundary. Do not use Pydantic internally where dataclasses suffice — the validation cost is real.
Sort imports with isort/ruff. One module per import line. Group: stdlib, third-party, first-party, separated by blank lines.
Always use parameterized queries for every database access. Never concatenate user-provided strings into SQL statements directly. This includes dynamic WHERE clauses, ORDER BY clauses, and table names.
Never log secrets, personally identifiable information, or full request or response bodies. Scrub sensitive fields at the logging boundary using a structured logger.
Treat any data that crossed a network or process boundary as untrusted until proven otherwise. Apply the same scrutiny to data from other internal services as you would to data from the public internet. The threat model assumes lateral movement; act accordingly across every service-to-service hop in the system.
Pull request review checklist for the team.
Project-wide security rules for handling untrusted input, secrets, and database access.
Database safety rules for the data-access layer.
Testing conventions for the project — pytest, fixtures, integration vs unit.