By the end, you will have your own repository based on Python Template, passing checks, a local documentation website, and a first draft PR.
Open python-template and select Use this template > Create a new repository. Choose your owner, name, and visibility. This creates an independent project; use the template button rather than forking if you want a fresh history.
Clone your new repository. Replace YOUR-OWNER and MY-PROJECT in these commands:
git clone https://github.com/YOUR-OWNER/MY-PROJECT.git
cd MY-PROJECT
git switch -c chore/customize-templateRun the remaining commands from this folder.
Install Git, just,
Quarto, and Python 3.13+.
On Windows, make python available on PATH. On macOS/Linux use python3,
and provide python for Claude's command hook. just uses PowerShell on Windows.
Install uv.
Run uv python install 3.13 if you need the package's interpreter.
The hook launcher also needs a Python command on PATH.
Check git --version, just --version, quarto --version, and your Python command,
then run:
uv sync
just run
just checkThe example prints Hello from python-template!. just check should finish successfully. It runs the repository tests,
checks documentation links and configuration, and builds the Quarto site.
If a command is missing, finish installing that tool before continuing.
The command reference explains each recipe.
Follow the customization how-to to rename the distribution,
import package, entry point, tests, and example commands together. Run uv lock,
uv sync, just check, and just build after renaming. Do not run uv init over
this initialized template; the README has a separate from-scratch example.
Update the license for your additions while preserving the supplied MIT notice for reused starter code. Review AGENTS.md and the AI tooling guide before trusting repository hooks in Claude or Codex.
The Python version policy is manual. Read versioning before changing dependencies or application behavior; package metadata and uv.lock must stay synchronized.
Change this tutorial's title to one meaningful to your project, then run:
just docsOpen the localhost URL printed by Quarto and find the changed page under Tutorials.
Stop preview with Ctrl+C. Run just check again and inspect git diff.
Rendered output in docs/_site is ignored and should not appear in your changes.
Stage only the files you intentionally changed. For example, if you changed only this tutorial:
git add docs/tutorials/first-project.md
git commit -m "docs: personalize the first-project tutorial"
git push -u origin chore/customize-templateIf you also customized other files, inspect and stage those explicit paths before committing. Keep the commit command separate from staging and directory changes.
Open a draft PR on GitHub describing the changes and just check result.
CI should pass on Windows and Ubuntu. When using an agent, explicitly authorize
the intended commit and push; the supplied committer and PR manager handle those
steps within that authorization.
Your repository is ready for project work. Add documentation to the appropriate Diataxis category as behavior grows. Publishing the website is optional and separate from publishing the source repository.
The checked-in AGENTS.md, CLAUDE.md, and workflow skills are ready to use.
Follow customizing agent instructions
to record your project's layout and commands, then run just agents-sync and
just agents-check. Use the guide's docs-maintainer example to try a skill before
asking an agent to commit or open a PR.