sheldon/loop-loop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: replace specific MCP recommendations with general guidance

Browse Source 
Avoid maintaining specific install commands that will go stale.
The evaluator uses whatever tools are available — let users
configure their own testing environment.
This commit is contained in:
Sheldon Finlay
2026-03-28 12:19:50 -04:00
parent c46de6815c
commit 9fd428ac51
1 changed files with 2 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@@ -95,27 +95,9 @@ Before the loop starts, the planner generates contracts for each story. These de
| `config.json` | Harness configuration |
| Git commits | Code changes with story-tagged messages |
## Optional: Runtime Testing Tools
## Runtime Verification
The evaluator verifies code actually runs, not just that it looks correct. It uses whatever tools are available. For richer verification, install these optional MCP servers:
**Web projects (Playwright):**
```bash
claude mcp add playwright npx @playwright/mcp@latest --headless --browser=chromium
```
**iOS/Xcode projects (XcodeBuildMCP):**
```bash
brew tap getsentry/xcodebuildmcp && brew install xcodebuildmcp
claude mcp add xcodebuild -- xcodebuildmcp
```
**iOS Simulator interaction:**
```bash
claude mcp add ios-simulator -- npx -y ios-simulator-mcp
```
These are optional — the evaluator works without them but may miss runtime-only issues.
The evaluator verifies code actually runs, not just that it looks correct. It uses whatever testing tools are available in your environment — test runners, linters, build tools, and any MCP servers you have installed (e.g., browser automation, simulator interaction). The more verification tools available, the more thorough the evaluator can be.
## Design Principles