agentleFS
axrmxvaxrmxv/claude-config/skills/standards-python/SKILL.md

standards-python

Skill1 starsChanged 4 months agoMITView on GitHub

Python coding standards — strict type annotations, frozen dataclasses and immutability, Protocol-based interfaces, pydantic at boundaries, pytest with 80% coverage, bandit scanning, black/isort/ruff. Use when writing, reviewing, or testing Python code.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the one that matches what you are doing:

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Python Standards

The Python delta over the always-loaded rules in .claude/rules/common/. Nothing here restates a rule from common/ — read this alongside it, not instead of it.

What applies immediately

  • Annotate every public signature, parameters and return type. No bare Any to appease the type checker — use a precise type, a Protocol, or a generic.
  • PEP 8 naming: snake_case for functions and modules, PascalCase for classes, UPPER_SNAKE_CASE for constants. The naming section in common/coding-style.md is JS/TS-flavored and does not apply here.
  • Frozen dataclasses for values you pass around or expose.
  • Fail fast on missing secrets — os.environ["KEY"] raises at startup; beyond a small script use a typed settings object.
  • Formatting is not your job: black, isort, and ruff own it. Configure them in pyproject.toml; do not hand-maintain PEP 8 details.

Reference files

Read the one that matches what you are doing:

FileCovers
coding-style.mdType annotations, naming, immutability, formatting/lint ownership
patterns.mdProtocol duck typing, dataclass vs pydantic DTOs, context managers, generators
security.mdSecret management from the environment, bandit scanning
testing.mdpytest, pytest-asyncio, coverage command, pytest.mark categorisation
hooks.mdPostToolUse formatting and type-check hooks, print() warnings

Building a FastAPI service? The standards-fastapi skill extends this one with layering, async SQLAlchemy, and request/response model rules.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.