agentleFS
nuncaeslupusnuncaeslupus/literary-critic/.claude/skills/python-bootstrap/SKILL.md

python-bootstrap

Skill0 starsChanged 27 days agoMITView on GitHub

Scaffolds or retrofits a Python project to the arsenal defaults (uv, ruff, strict mypy, standard Makefile, 3.12+). Use when the user sets up Python tooling. Not for publishing (pypi-release) or dependency upgrades (dep-upgrade).

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from the target project root, since the script reads the current directory:

    line 28
  2. Very specific:

    Remove black when adding ruff format, so the two do not fight.

    line 47
  3. Very specific:

    If model_gen.specs_present is true, the project drives a JSON-spec backend generator.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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-bootstrap

Brings a Python project in line with the arsenal defaults — uv, ruff, strict mypy, the standard Makefile, requires-python>=3.12 — from scratch or as a retrofit.

CANARY: python-bootstrap-loaded-2026-06-04-ea39c2b5-394e8afa1019319d

When to load

Load when a Python repo needs its tooling created or brought up to standard: no pyproject.toml yet, or one missing the ruff select list, the strict mypy block, or the Makefile targets. Publishing belongs to pypi-release, upgrades to dep-upgrade.

Step 1 — Report the gaps

Run from the target project root, since the script reads the current directory:

python3 "${CLAUDE_SKILL_DIR}/scripts/analyze_project.py" [project_dir]

The JSON gives mode (scaffold without pyproject.toml, else retrofit), ruff.missing_select, mypy.missing_keys, makefile.missing_targets, requires_python_ok, and model_gen.

Step 2 — Apply the canonical blocks

Load references/canonical-config.md before applying any block: it holds the pyproject (ruff + mypy), Makefile and uv blocks. Apply only what the report flags:

  • Merge into existing [tool.ruff] and [tool.mypy] tables, keeping the project's per-file-ignores, extra select codes and module overrides.
  • Match target-version, python_version and requires-python to what the project supports; the flags are defaults, the versions are not.
  • Remove black when adding ruff format, so the two do not fight.
  • On an untyped codebase, stage strict mypy with per-module [[tool.mypy.overrides]] rather than weakening the global block.

Then run the project's make lint and make test (or uv run ruff check . and uv run mypy .) to confirm the new config is clean.

Step 3 — Hand off model specs

If model_gen.specs_present is true, the project drives a JSON-spec backend generator; SQLAlchemy models, Pydantic schemas and FastAPI routes belong to the model-generator toolkit (model-gen / model-val). This skill sets up repo tooling only.

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.