I’m the creator of Vibe Monitor. Three problems motivated this project: features accumulate in individual files unless someone asks to split components; a move from a monolith to services needs a timely architectural decision; and systems spanning hardware and software need planning beyond implementing the next feature.
For the first problem, a useful checkpoint is to ask whether the next change belongs in the same file. If unrelated components are accumulating there, giving the agent a specific extraction task creates a decision it can act on. A large file alone does not tell us what the right components are.
Before adding the next feature, list the responsibilities in this file. Propose one small extraction, explain the data crossing its interface, and wait for review before changing code.
For the second, a reminder should support the decision, not assume its answer. Service separation needs a reason grounded in the project’s requirements. The question is what has become difficult to change or operate together, and whether separating it would help enough to justify the added coordination.
What requirement would justify a separate service here? Compare a simpler internal module with the deployment, communication and failure-handling work a service would add. Identify missing requirements before recommending a migration.
For the third, project context matters: which devices, environments and interfaces must the system support? A code observation cannot validate hardware compatibility or replace that planning.
Map the target devices and operating systems to the interfaces they require. Separate assumptions from evidence, and identify what must be tested on real hardware.
These are suggested review prompts, not claims of completed migrations or hardware tests.
Vibe Monitor brings architecture evolution observations and staged advice into AI coding sessions over local MCP. It does not automatically split components, migrate to microservices, or validate hardware compatibility. I’d like feedback on when reminders help and when they become noise.
Setup requires Node.js 22+:
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install
The installer updates supported MCP/agent configuration and creates backups. Source analysis is read-only. The client is Apache-2.0; cloud policy/scoring is a separate proprietary service. Bounded pseudonymous telemetry defaults on; opting out s Free analysis.
Source and current setup: https://github.com/tubban1/vibe-monitor
My original motivations were written in Chinese; AI helped translate, organise, and expand these notes into this article and the example prompts.