From c19309fe7ea77e44e07ce1146a655bd3a88267ab Mon Sep 17 00:00:00 2001 From: Benson Wong Date: Wed, 7 Jan 2026 21:34:23 -0800 Subject: [PATCH] CLAUDE.md: small instruction tweaks --- CLAUDE.md | 43 ++++++++++++++++++++++--------------------- 1 file changed, 22 insertions(+), 21 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index c38aa9a6..4215f035 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,5 +1,3 @@ -# Project: llama-swap - ## Project Description: llama-swap is a light weight, transparent proxy server that provides automatic model swapping to llama.cpp's server. @@ -9,6 +7,13 @@ llama-swap is a light weight, transparent proxy server that provides automatic m - golang - typescript, vite and react for UI (ui/) +## Workflow Tasks + +- when summarizing changes only include details that require further action +- just say "Done." when there is no further action +- use `gh` to create PRs and load issues +- do not mention "created by claude" in commit messages + ## Testing - Follow test naming conventions like `TestProxyManager_`, `TestProcessGroup_`, etc. @@ -16,30 +21,26 @@ llama-swap is a light weight, transparent proxy server that provides automatic m - Use `make test-dev` after running new tests for a quick over all test run. This runs `go test` and `staticcheck`. Fix any static checking errors. Use this only when changes are made to any code under the `proxy/` directory - Use `make test-all` before completing work. This includes long running concurrency tests. -## Workflow Tasks +### Commit message example format: -### Plan Improvements +``` +proxy: add new feature -Work plans are located in ai-plans/. Plans written by the user may be incomplete, contain inconsistencies or errors. +Add new feature that implements functionality X and Y. -When the user asks to improve a plan follow these guidelines for expanding and improving it. +- key change 1 +- key change 2 +- key change 3 -- Identify any inconsistencies. -- Expand plans out to be detailed specification of requirements and changes to be made. -- Plans should have at least these sections: - - Title - very short, describes changes - - Overview: A more detailed summary of goal and outcomes desired - - Design Requirements: Detailed descriptions of what needs to be done - - Testing Plan: Tests to be implemented - - Checklist: A detailed list of changes to be made +fixes #123 +``` -Look for "plan expansion" as explicit instructions to improve a plan. +## Code Reviews -### Implementation of plans +- use three levels High, Medium, Low severity +- label each discovered issue with a label like H1, M2, L3 respectively +- High severity are must fix issues: -When the user says "paint it", respond with "commencing automated assembly". Then implement the changes as described by the plan. Update the checklist as you complete items. + - security issues -## General Rules - -- when summarizing changes only include details that require further action (action items) -- when there are no action items, just say "Done." +- Medium are recommended improvements