Backend
Defines Python tooling rules and a linting/formatting workflow using uv, pyrefly, and black.
View sourceWhat this file does
Defines Python tooling rules and a linting/formatting workflow using uv, pyrefly, and black.
When to use it
- You want to enforce uv as the only Python package manager
- You need a simple make-based lint-and-format check for Python code
- You want to prevent direct edits to pyproject.toml
Assumes this stack
Backend
Python
Always use uv for Python. Never edit pyproject.toml directly. Never use pip.
Linting and formatting
After every bigger code change, run:
make check-and-format-py
This runs pyrefly (type checker) then black (formatter). Fix any errors before proceeding.
By bigger code we mean that you should not actually run this check every time you edit something, but you should always run it before you try to present the code to the user.
What's inside
2 sections: Python tooling rule and linting/formatting workflow with one make command.
Change this for your project
- Replace
make check-and-format-pywith your own make target if different - Replace
pyreflywith your preferred type checker if different
Where it goes
Save as CLAUDE.md in your repository root. Claude Code reads it automatically at the start of every session.
Related Documents
Code indexing for AI agents: summarization strategies and evaluation systems
Synthesises 2024-2025 research on code indexing for AI agents, covering summarisation strategies, hybrid retrieval architectures, and evaluation benchmarks.
write-script
Guides an AI through writing a YouTube video script with strict structural, language, and quiz rules for a survival channel.
Claude AI Git Workflow Integration
Recommends using the git-ai-commit CLI tool for AI-generated commit messages instead of manual ones.
Missing Business Agents Research — FLUXION 2026
Identifies 12 missing business operations agents for an indie software company and ranks them by impact and effort with €0 implementation plans.