PythonCourt

Prohibits relying on Any, uncontracted dicts and blind typing.cast, to avoid turning core data flows into untyped “duck‑typed” fog that static checks cannot protect.

Prohibits primitive or container types on HTTP/adaptor boundaries, to avoid leaking internal models instead of explicit DTO / contract types at the system edge.

Prohibits cross‑component imports that bypass core abstractions, to avoid breaking dependency inversion and tightly coupling modules to one another’s implementations.

Prohibits direct use of datetime.now() / datetime.utcnow(), to avoid hidden time drift and untestable time‑dependent logic outside a single TimeProvider.

Prohibits public functions and classes from lacking clear, non‑trivial docstrings, to avoid opaque APIs whose intent and contract cannot be reviewed or taught.

Prohibits hard‑coded business literals and magic numbers outside constant modules, to avoid hiding configuration and cross‑engine contracts in scattered code.

Prohibits functions whose length or cyclomatic complexity exceeds agreed thresholds, to avoid procedures that are too large and tangled to reason about safely.

Prohibits using bare object as a type in core code, to avoid “grey fog” values with no contract, where invariants and capabilities cannot be enforced.

Prohibits treating adjustable business rules as core constants and bypassing the rule provider to directly access rule files, to avoid confusing operational controls with technical constants.

Prohibits bloated __init__.py files that contain logic, control flow or export gymnastics, to avoid package facades degenerating into a second hidden implementation module.

Prohibits hard‑coding Skill IDs or directly reading from assets/skills via file I/O, to avoid coupling business code to physical skill layouts instead of a central SkillId registry and provider.