From e2137baeb237e36994d55a56cd9e134d9f73404f Mon Sep 17 00:00:00 2001 From: Johannes Horn Date: Fri, 18 Sep 2026 17:39:55 +0200 Subject: [PATCH 1/2] docs: added AI usage into the README --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index e490aec..40b6c23 100644 --- a/README.md +++ b/README.md @@ -54,3 +54,24 @@ Before a pull request can be merged: 3. **Pushing new commits dismisses the approval**, so if you change something after being approved, ask for another review. This is deliberate: what was approved is what gets merged. + +## Use of AI in this project + +We have used Claude (through Claude Code) as a tool during development. In +short, it was used for: + +- **Code review and requirements checks.** Reviewing our own code before + pull requests, and checking the project against the functional and + technical requirements. +- **Test setup.** Setting up Vitest and React Testing Library and writing the + initial tests. We then removed the tests that did not add value and wrote + new ones ourselves (for example the tests for `fetchWork`, `toDescription` + and `SearchBar`). +- **Understanding.** Explaining how mocking, spies and `vi.mock` work, so that + we can explain every test in the project ourselves. +- **Open Library API.** Working out the shape of some API responses, such as + the `description` field of a work. + +Where AI contributed directly to a piece of code, there is a comment saying +so, for example in [src/api/types.ts](src/api/types.ts) and +[src/main.tsx](src/main.tsx). From 4ca58ac34064e7b6c052ba778ed5e7e1d0dd9097 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Str=C3=B8m-Andersen?= Date: Fri, 18 Sep 2026 20:23:06 +0200 Subject: [PATCH 2/2] docs: expand AI usage documentation --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 40b6c23..e4a5f7e 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,9 @@ short, it was used for: new ones ourselves (for example the tests for `fetchWork`, `toDescription` and `SearchBar`). - **Understanding.** Explaining how mocking, spies and `vi.mock` work, so that - we can explain every test in the project ourselves. + we can explain every test in the project ourselves. Team members less experienced + with React and TypeScript also found AI useful as a resource to ask questions + about concepts while learning and working with the project. - **Open Library API.** Working out the shape of some API responses, such as the `description` field of a work.