Remove agent rules (refer to speculate instead).

Author: jlevy

README.md

@@ -16,24 +16,22 @@ Follow](https://img.shields.io/twitter/follow/ojoshe)](https://x.com/ojoshe)
 
 **simple-modern-uv** is a minimal, modern **Python project template** for new projects
 (Python 3.11–3.13) based on [**uv**](https://docs.astral.sh/uv/). This template aims to
-be a good base for serious work but also simple so it's an easy option for any small
+be a good base for serious work but also simple so it’s an easy option for any small
 project, like an open source library or tool.
 
 ## In a Hurry?
 
-> [!TIP]
-> 
-> You can try out this template right from your terminal.
-> Try running:
-> 
-> ```shell
-> uvx uvinit
-> ```
-> 
-> The [uvinit](https://git.new/uvinit) tool now walks you through using this template.
-> 
-> For more installation options, scroll down to [How to Use This
-> Template](#how-to-use-this-template).
+You can try out this template right from your terminal.
+Try running:
+
+```shell
+uvx uvinit
+```
+
+The [uvinit](https://git.new/uvinit) tool now walks you through using this template.
+
+For more installation options, scroll down to [How to Use This
+Template](#how-to-use-this-template).
 
 ## Why a New Python Project Template?
 
@@ -65,19 +63,19 @@ project, like an open source library or tool.
 Apologies for the digression.
 The point is that unfortunately, the accidents of history make it quite confusing to
 learn best practices for setting up Python projects and dependencies.
-But it shouldn't have to be this difficult, especially since uv has now significantly
+But it shouldn’t have to be this difficult, especially since uv has now significantly
 simplified Python dev tooling.
 
-If you haven't switched to uv, I can say I too was a little hesitant.
-It's often possible to switch dev tooling prematurely because a the new tool is shiny
+If you haven’t switched to uv, I can say I too was a little hesitant.
+It’s often possible to switch dev tooling prematurely because a the new tool is shiny
 and exciting. But the advantages of uv have become too numerous to ignore.
 [This article](https://www.bitecode.dev/p/a-year-of-uv-pros-cons-and-should) (Feb 2025)
 has a good overview.
 
 This is the template I now use myself as I have been migrating from Poetry to uv for
-several projects. It's new but it's working well.
+several projects. It’s new but it’s working well.
 
-## But I Don't Like Templates
+## But I Don’t Like Templates
 
 A lot of more senior engineers have justified hesitancy about templates.
 Templates can be a real problem if they add mindless, unexamined complexity.
@@ -86,17 +84,17 @@ code you can adapt, instead of leaving you to figure out each tool choice and se
 or blog posts (that are typically not maintained or updated).
 
 I think a good project template should be **3 Ms: minimalist, modern, and maintained**.
-I looked at [other templates](#alternatives) but wanted one that was modern and "done
-right" but *absolutely as simple as possible*. Few existing templates seem to be both
+I looked at [other templates](#alternatives) but wanted one that was modern and “done
+right” but *absolutely as simple as possible*. Few existing templates seem to be both
 simple and use the newest generation of tools and best practices.
 
 The template is short enough to read and understand in about 10 minutes.
-It's **only ~300 lines of code** so you can just look at it, use it, and change what you
+It’s **only ~300 lines of code** so you can just look at it, use it, and change what you
 want without fuss.
 
 Because this template is minimal, you can always start with it and then pull in other
 tools and features if you want them.
-(In fact, even if you don't like this template, you might want to use it as inspiration
+(In fact, even if you don’t like this template, you might want to use it as inspiration
 for your *own* Copier template, to take advantage of the Copier update workflow
 discussed next.)
 
@@ -114,17 +112,15 @@ tools, you can pull those improvements back into your project, much like a git m
 You could even fork this repo yourself, then build your own forked template, and
 maintain it yourself.
 
-> [!NOTE]
-> 
-> If you're not familiar with Copier, take a moment to understand the
-> [update feature](#updating-your-project-template).
-> Then the options below will make sense.
-> I put a few more thoughts on why a workflow like this is underrated is in
-> [a Twitter thread](https://x.com/ojoshe/status/1896696860297019733).
+If you’re not familiar with Copier, take a moment to understand the
+[update feature](#updating-your-project-template).
+Then the options below will make sense.
+I put a few more thoughts on why a workflow like this is underrated is in
+[a Twitter thread](https://x.com/ojoshe/status/1896696860297019733).
 
 ## What Tools are In This Template?
 
-simple-modern-uv uses uses the tools I've come to think are best for new projects:
+simple-modern-uv uses uses the tools I’ve come to think are best for new projects:
 
 - [**uv**](https://github.com/astral-sh/uv) for project setup and dependencies.
   There is also a simple makefile for dev workflows, but it simply is a convenience for
@@ -176,44 +172,34 @@ The template includes a few **starter docs** for you, collaborators, and users:
 - [publishing.md](https://github.com/jlevy/simple-modern-uv/blob/main/template/publishing.md)
   covers how to publish your project to PyPI.
 
-> [!TIP]
-> 
-> If you haven't done it before, publishing a package to PyPI can be a bit confusing,
-> especially because the
-> [official Python docs](https://packaging.python.org/en/latest/guides/section-build-and-publish/)
-> cover older and more complex workflows.
-> Be sure to check `publishing.md` for a modern and simple way that uses uv and GitHub
-> actions.
-
-You can edit or delete these, but typically it's sufficient to just edit the README.md.
+If you haven’t done it before, publishing a package to PyPI can be a bit confusing,
+especially because the
+[official Python docs](https://packaging.python.org/en/latest/guides/section-build-and-publish/)
+cover older and more complex workflows.
+Be sure to check `publishing.md` for a modern and simple way that uses uv and GitHub
+actions.
+
+You can edit or delete these, but typically it’s sufficient to just edit the README.md.
 It helps to have the others in separate files so they get updated whenever you update
 the template.
 
 ## Agent Rules
 
-This template also includes a few **agent rules** for use with Cursor, Claude Code, and
-OpenAI Codex.
-
-These cover a few specific rules for modern Python as well as remind agents to build,
-lint, and run tests correctly using uv.
+Previously, this template included a few agent rules for use with Claude Code, Codex,
+Cursor, etc. But agent rules are changing so fast I have since removed them from this
+template and instead suggest adding your own or copying my recent rules from the
+[Speculate](https://github.com/jlevy/speculate) repo.
 
-The rules are in [.cursor/rules](template/.cursor/rules) and copied by the
-[Makefile](template/Makefile) to
-[`CLAUDE.md`](https://docs.anthropic.com/en/docs/claude-code/memory) and
-[`AGENTS.md`](https://github.com/openai/codex#memory--project-docs) so that the same
-rules work for Claude Code and OpenAI Codex.
-(Of course you can adjust these as you wish.)
-
-## What's the Best Python Type Checker?
+## What’s the Best Python Type Checker?
 
 The choice of what tool to use for type checking deserves some explanation.
 This seems to be a confusing area.
 
-Like many, I'd previously been using [Mypy](https://github.com/python/mypy), the OG type
+Like many, I’d previously been using [Mypy](https://github.com/python/mypy), the OG type
 checker for Python. Mypy has since been enhanced with
 [BasedMypy](https://github.com/KotlinIsland/basedmypy).
 
-The other popular alternative is Microsoft's
+The other popular alternative is Microsoft’s
 [Pyright](https://github.com/microsoft/pyright).
 And it has a newer extension and fork called
 [BasedPyright](https://github.com/DetachHead/basedpyright).
@@ -224,13 +210,13 @@ checker warnings align with your IDE warnings.
 With the rises of AI-powered IDEs like Cursor and Windsurf that are VSCode extensions,
 it seems like type checking support as a VSCode-compatible extension is essential.
 
-However, Microsoft's popular
+However, Microsoft’s popular
 [Mypy VSCode extension](https://marketplace.visualstudio.com/items?itemName=ms-python.mypy-type-checker)
 is licensed only for use in VSCode (not other IDEs) and
 [sometimes](https://forum.cursor.com/t/pylance-server-fails-to-initialize-due-to-licensing-restriction/48548)
 [refuses](https://forum.cursor.com/t/does-pylance-just-not-work-with-cursor-how-to-get-imports-in-quick-fix-menu/5747)
-to work in Cursor. [Cursor's docs](https://docs.cursor.com/guides/languages/python)
-suggest Mypy but don't suggest a VSCode extension.
+to work in Cursor. [Cursor’s docs](https://docs.cursor.com/guides/languages/python)
+suggest Mypy but don’t suggest a VSCode extension.
 
 After some experimentation, I found
 [BasedPyright](https://github.com/detachhead/basedpyright) to be a credible improvement
@@ -243,24 +229,24 @@ So I have now switched this template to use BasedPyright.
 
 ## What Does This Template Not Include?
 
-The template doesn't have lots of options or try to use every bell and whistle.
+The template doesn’t have lots of options or try to use every bell and whistle.
 It just adds the above essentials.
 
 This template **does not** handle:
 
 - Using Docker
 
-- Private or enterprise package repositories (but you can add this—see [uv's docs on
+- Private or enterprise package repositories (but you can add this—see [uv’s docs on
   alternative
   indexes](https://docs.astral.sh/uv/guides/integration/alternative-indexes/))
 
 - Building websites or docs, e.g. with [mkdocs](https://github.com/mkdocs/mkdocs)
 
 - Using [Conda](https://github.com/conda/conda) for dependencies (but note many deep
-  learning libraries like PyTorch now support pip so this isn't as necessary as often as
+  learning libraries like PyTorch now support pip so this isn’t as necessary as often as
   it used to be)
 
-- Using a code repo or build system that isn't GitHub and GitHub Actions
+- Using a code repo or build system that isn’t GitHub and GitHub Actions
 
 - Boilerplate docs or project management of any kind, like issue templates, contributing
   guidelines, code of conduct, etc.
@@ -274,13 +260,11 @@ references.
 
 ## How to Use This Template
 
-> [!NOTE]
-> 
-> By default this template uses MIT license.
-> If you want a different license or are not publishing your project as open source,
-> update `license` in pyproject.yaml and the LICENSE file.
-> If desired, you may delete the `.github/workflows/publish.yml` file if you are not
-> publishing to PyPI.
+By default this template uses MIT license.
+If you want a different license or are not publishing your project as open source,
+update `license` in pyproject.yaml and the LICENSE file.
+If desired, you may delete the `.github/workflows/publish.yml` file if you are not
+publishing to PyPI.
 
 The template can be used in three ways.
 Option 1 is the quickest option with full flexibility.
@@ -289,14 +273,14 @@ Option 3 is handy if you prefer a GitHub template.
 
 ### Option 1: Run `uvx uvinit`
 
-I've now created a little tool, [uvinit](https://www.github.com/jlevy/uvinit) that
+I’ve now created a little tool, [uvinit](https://www.github.com/jlevy/uvinit) that
 copies this template for you and walks you through everything:
 
 ```shell
 uvx uvinit
 ```
 
-It's the same as running `copier` and a few `git` commands yourself, with a little more
+It’s the same as running `copier` and a few `git` commands yourself, with a little more
 guidance and less typing.
 
 ### Option 2: Use `copier` and `git` Yourself
@@ -349,7 +333,7 @@ If you prefer you can click the **use this template** on
 [**this repository**](https://github.com/jlevy/simple-modern-uv-template), which is the
 current output of this template.
 
-Go there and hit the "Use this template" button.
+Go there and hit the “Use this template” button.
 Once you have the code, search for **`changeme`** for all field names like project name,
 author, etc. You want to do this to the `.copier-answers.yml` file as well.
 You will also want to check the license/copyright.
@@ -377,8 +361,8 @@ There are a couple other good uv templates, especially
 [**copier-uv**](https://github.com/pawamoy/copier-uv) you may wish to consider.
 
 This template takes a somewhat different philosophy.
-I found existing templates to have machinery or files you often don't need.
-And it's hard to maintain a complex template repo.
+I found existing templates to have machinery or files you often don’t need.
+And it’s hard to maintain a complex template repo.
 This is intended instead to be a very simple template.
 You can always add to it if you want.
 
@@ -403,7 +387,7 @@ For [Conda](https://github.com/conda/conda) dependencies, also consider the newe
 
 ## Contributing
 
-I'm new to uv, so please help me improve this!
+I’m new to uv, so please help me improve this!
 Please use the Discussions thread with any feedback or suggestions.
 PRs welcome on [this repository](https://github.com/jlevy/simple-modern-uv) (not on the
 GitHub template repo, which mirrors this one).