STS2 MCP Wrapper — current setup
This diagram shows the development workflow used when building the STS2 MCP wrapper dashboard with Claude Code. It covers both client-side widget development and upstream mod patching across a multi-machine environment (host, Hyper-V VM, upstream repo).
flowchart TD
A[Identify Need] --> B{Client or Mod?}
B -->|Client Widget| C[Edit widget code locally]
C --> D[Test against live API]
D --> E{Working?}
E -->|No| C
E -->|Yes| F[Lint with ruff]
F --> G[Stage & Commit to sts2-mcp-wrapper]
B -->|Mod Patch Needed| H[Edit McpMod.StateBuilder.cs]
H --> I[dotnet build locally]
I --> J{Build OK?}
J -->|No| H
J -->|Yes| K[Commit & Push to fork/main]
K --> L[Clipboard deploy command]
L --> M[User pastes on win11-base VM via RDP]
M --> N[VM: git fetch fork, build, install DLL]
N --> O[User restarts game]
O --> P[Test via API from host]
P --> Q{Working?}
Q -->|No| H
Q -->|Yes| R{Upstream?}
R -->|Stage| S[Create branch off origin/main\nCherry-pick change\nPush to fork - no PR yet]
R -->|Submit| T[Create PR against\nGennadiyev/STS2MCP]
R -->|Later| G
S --> G
T --> U[Monitor PR feedback]
U --> V{Changes requested?}
V -->|Yes| W[Update branch\nForce-push]
W --> U
V -->|Merged| X[Done]
Thanks for fork, just updated with a screenshot feedback loop workflow.