Compare commits

...

6 Commits

Author SHA1 Message Date
Kim Morrison
4810e0ca2d casing 2025-11-04 05:01:24 +01:00
Kim Morrison
8ee3f771f9 use nproc 2025-11-04 05:01:03 +01:00
Kim Morrison
b1d1d74576 better advice for tests 2025-11-04 04:59:56 +01:00
Kim Morrison
5350ac7ec7 cases sensitive, awesome 2025-11-04 04:58:00 +01:00
Kim Morrison
0c342748db meta 2025-11-04 04:33:39 +01:00
Kim Morrison
8a5316b4dc chore: basic dev instructions for Claude 2025-11-04 04:28:29 +01:00

14
.claude/CLAUDE.md Normal file
View File

@@ -0,0 +1,14 @@
When asked to implement new features:
* begin by reviewing existing relevant code and tests
* write comprehensive tests first (expecting that these will initially fail)
* and then iterate on the implementation until the tests pass.
To build Lean you should use `make -j$(nproc) -C build/release`.
To run a test you should use `cd tests/lean/run && ./test_single.sh example_test.lean`.
*Never* report success on a task unless you have verified both a clean build without errors, and that the relevant tests pass. You have to keep working until you have verified both of these.
All new tests should go in `tests/lean/run/`. Note that these tests don't have expected output, and just run on a success or failure basis. So you should use `#guard_msgs` to check for specific messages.
If you are not following best practices specific to this repository and the user expresses frustration, stop and ask them to help update this `.claude/CLAUDE.md` file with the missing guidance.