Benson Wong
3dc36032fb
* proxy: skip very slow tests in -short test mode * CLAUDE.md: update testing instructions
46 lines
1.8 KiB
Markdown
46 lines
1.8 KiB
Markdown
# Project: llama-swap
|
|
|
|
## Project Description:
|
|
|
|
llama-swap is a light weight, transparent proxy server that provides automatic model swapping to llama.cpp's server.
|
|
|
|
## Tech stack
|
|
|
|
- golang
|
|
- typescript, vite and react for UI (ui/)
|
|
|
|
## Testing
|
|
|
|
- Follow test naming conventions like `TestProxyManager_<test name>`, `TestProcessGroup_<test name>`, etc.
|
|
- Use `go test -v -run <name pattern for new tests>` to run any new tests you've written.
|
|
- 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
|
|
|
|
### Plan Improvements
|
|
|
|
Work plans are located in ai-plans/. Plans written by the user may be incomplete, contain inconsistencies or errors.
|
|
|
|
When the user asks to improve a plan follow these guidelines for expanding and improving it.
|
|
|
|
- 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
|
|
|
|
Look for "plan expansion" as explicit instructions to improve a plan.
|
|
|
|
### Implementation of plans
|
|
|
|
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.
|
|
|
|
## General Rules
|
|
|
|
- when summarizing changes only include details that require further action (action items)
|
|
- when there are no action items, just say "Done."
|