Apply these opinionated Python 3.11+ conventions when writing Python in this codebase: type hints with mypy, async/await, pytest fixtures, dataclasses, Poetry packaging, production patterns.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Python
House conventions for Python 3.11+. Apply them to code you are writing or changing — don't refactor untouched files to match unless asked.
## Conventions
- **Type every public signature** and keep `mypy --strict` green. Types on internals are optional; types at the boundary are what stop a caller passing the wrong thing.
- **Built-in generics and `X | None`** — `list[str]`, `dict[str, int]`, `str | None`. `typing.List` and `Optional[str]` are the pre-3.10 spelling and only cost an import.
- **`Protocol` over ABC inheritance.** Structural typing lets any correctly-shaped object satisfy the contract — including a test double — with no inheritance tree to maintain.
- **Dataclasses for data**, `slots=True` and `frozen=True` where they fit. They generate `__init__`, `__repr__`, and `__eq__` correctly; a hand-written `__init__` is where field drift starts. Pydantic is for validation and (de)serialisation at a boundary, not for plain records.
- **`pathlib`, not `os.path`.** Operator joins can't silently produce a wrong path from a stray separator.
…
The line at the top of this page pins the label git:20261013.ecfffa1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_u2ij6vwb6dwztpb6
GET https://markdownregistry.com/api/v1/resolve?ref=alexander-danilenko/cortex-claude-code-plugins/conventions
GET https://markdownregistry.com/api/v1/blob/b0981e3526da7a11515f8e65d49bc877733db2a84e8b45898f9ff4778811f382
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
alexander-danilenko/cortex-claude-code-plugins · plugins/common/cortex-communication/skills/answer-buzzkill/SKILL.md · Write a short, fact-checked reply that answers a colleague's question in one meaning only, ready to copy and paste. The…
alexander-danilenko/cortex-claude-code-plugins · plugins/common/cortex-communication/skills/humanize-text/SKILL.md · Remove signs of AI-generated writing from text. Use after drafting to make copy sound more natural and human-written…
alexander-danilenko/cortex-claude-code-plugins · plugins/common/cortex-communication/skills/simple-english/SKILL.md · Write or audit technical text against ASD-STE100 Simplified Technical English so a tired, non-native reader understands…
alexander-danilenko/cortex-claude-code-plugins · plugins/engineering/cortex-coderabbit/skills/resolve-feedback/SKILL.md · Resolve CodeRabbit review feedback on a GitHub pull request. Collects every open CodeRabbit finding (inline threads…
alexander-danilenko/cortex-claude-code-plugins · plugins/engineering/cortex-jira/skills/qa-scope/SKILL.md · Draft the QA scope and plain-language Given/When/Then test scenarios for a Jira ticket, built from the full ticket, the…
alexander-danilenko/cortex-claude-code-plugins · plugins/engineering/cortex-jira/skills/report-comment/SKILL.md · Turn the git commits for a Jira ticket into a short, business-friendly implementation report and save it as local…
alexander-danilenko/cortex-claude-code-plugins · plugins/engineering/cortex-knowledge/skills/documentation/SKILL.md · ALWAYS invoke for any task involving docstrings, JSDoc/TSDoc, or REST API documentation — even when the request seems…
alexander-danilenko/cortex-claude-code-plugins · plugins/engineering/cortex-knowledge/skills/learn-with-docs-refresh/SKILL.md · Audit and maintain the learnings in `docs/solutions/` against the current codebase — fix drifted paths and links, merge…
alexander-danilenko/cortex-claude-code-plugins · plugins/engineering/cortex-knowledge/skills/learn-with-docs/SKILL.md · Capture a solved, verified problem as a durable learning in `docs/solutions/` so the next agent or engineer does not…
alexander-danilenko/cortex-claude-code-plugins · plugins/engineering/cortex-testing/skills/conventions/SKILL.md · Apply these opinionated testing conventions whenever writing, reviewing, or planning tests: what earns a test and what…
alexander-danilenko/cortex-ai-skills · plugins/engineering/cortex-testing/skills/conventions/SKILL.md · Apply these opinionated testing conventions whenever writing, reviewing, or planning tests: what earns a test and what…
alexander-danilenko/cortex-ai-skills · plugins/engineering/cortex-python/skills/conventions/SKILL.md · Apply these opinionated Python 3.11+ conventions when writing Python in this codebase: type hints with mypy…
