@@ -2,15 +2,15 @@
22 description: Run one-shot mc sessions across all SDK paths, capture output, and write a UI/UX analysis report to UI-REPORT.md.
33 ---
44
5-The goal is to capture a realistic perspective of what the users see when using mini-coder.
5+The goal is to capture a realistic perspective of what the users see when using mini-coder. And ensure the core idea (mini-coder-idea.md) is well executed in the output.
66
7-Run `mc` one-shots using one cheap model per Zen SDK path, capture their raw terminal output, then analyse it yourself and write `UI-REPORT.md` in the repo root.
7+Run `mc` using one cheap modern model per provider path, capture their raw terminal output, then analyse it yourself and write `UI-REPORT.md` in the repo root.
88 Do NOT delegate the report to the models under test.
9-Use `tmux` so you can test interactive sessions properly.
9+Use `tmux` so you can test interactive sessions properly. Remember to send Enter to submit, and careful with the paste handling.
1010
1111 ## Models to use (one per SDK path)
1212
13-Pick cheap options. Verify available models at https://opencode.ai/docs/zen/ if needed, then choose:
13+Pick cheap options. Verify available models at https://opencode.ai/docs/zen/, then choose:
1414
1515 - `@ai-sdk/anthropic` path → a `zen/claude-*` haiku-class model
1616 - `@ai-sdk/google` path → a `zen/gemini-*` flash-class model
@@ -22,38 +22,17 @@ Also use a Anthropic Oauth model for completness
2222
2323 ## Prompt to give each model
2424
25-```
26-Read mini-coder-idea.md and TODO.md, then create mc-summary.md in the repo root with a short summary of what mini-coder is and a list of the key TODO items.
27-```
28-
29-This prompt is intentionally simple: it covers file reads, a write, and exposes path resolution, spinner, error handling, and output formatting behaviour.
30-
31-## Steps
32-
33-1. Create `logs/` in the repo root if it doesn't exist.
34-2. For each model, run:
35- ```
36- mc -m <model> "<prompt>" > logs/<model>.log 2>&1
37- ```
38- Run them sequentially (not in parallel) to avoid SQLite lock issues.
39-3. Strip ANSI escape codes from each log for clean reading:
40- ```
41- sed 's/\x1b\[[0-9;?]*[mKlh]//g; s/\r//g' logs/<model>.log > logs/<model>-clean.log
42- ```
43-4. Read all clean logs yourself and analyse what a user would actually see.
44-5. Clean up any `mc-summary.md` files left behind by the test models. And the log files
25+Use prompts that will ensure a realistic pattern, using multi steps and turns. Check the db for examples if needed.
4526
4627 ## Report structure for UI-REPORT.md
4728
4829 Write `UI-REPORT.md` in the repo root with these sections:
4930
50-- **Methodology** — models tested, prompt used, how output was captured
51-- **Per-model results** — for each model: did it complete the task? what did the user see step by step? any errors or recovery detours?
52-- **Shared UI observations** — patterns across all models: spinner behaviour, tool call chrome (symbols, indentation), reasoning block display, diff output, final response format, banner/status bar presence
53-- **UI/UX** how can it be improved, is the output elegant, clear and hierchial?
54-- **Bugs found** — table: severity, description, likely source file
55-- **Alignment with mini-coder-idea.md** — table comparing each idea goal against what was observed (✅ / ⚠️ / ❌)
56-- **Recommendations** — split into immediate bugs and polish items
31+- **Summary** -- a short summary of how you tested and what your found.
32+- **Alignment with mini-coder-idea.md** -- Comparison summary, avoid using tables.
33+- **Recommendations** -- split into immediate bugs and polish items
34+
35+Don't be verbose, be concise in your report.
5736
5837 Use `mini-coder-idea.md` and `TODO.md` as the source of truth for what the UI _should_ look like.
5938 The report is analysis only — no code changes.