DRIFT
Context-heavy setup
See which repo layers are carrying too much memory, instruction weight, or setup noise before new projects inherit the same sprawl.
VibeSmith
Audit AI coding repo drift before it spreads.
VibeSmith gives multi-repo teams one place to review active components, dependency risk, and context-heavy reuse across Cursor and Claude Code workflows. Community is public and free today.
If kickoff quality drops after repo three, start here.
Live dashboard and walkthrough
Community build is public
Built for multi-repo AI teams
WHAT SURFACES FIRST
See the problems teams usually discover too late
VibeSmith is most useful when your team needs one visible layer for setup drift, reuse risk, and context-heavy sprawl across repositories.
REUSE
Hidden reuse risk
Review what needs to move with a component so copy-paste bootstrap stops failing in partial, expensive ways.
RELEASE
Dependency and conflict surprises
Surface linked risk earlier so release-week review is not the first time your team sees the coupling.
FIRST-WEEK PAIN
What teams want from the first real audit
The common request is not another AI feature. It is a clearer operating view across repos.
Need 01
Know which standards are actually active
Teams lose time when rules, commands, and guidance look similar but differ just enough across repos to change behavior.
Need 02
Reuse without losing linked context
Users want to copy safe baselines, not half-working fragments that hide dependencies until later.
Need 03
Reduce context waste before it becomes review waste
Mixed memory layers and stale assets create token waste, noisy prompts, and longer review loops.
Visual Proof
Workflow proof from real vibe coder pain
Start with the inline walkthrough, then inspect each decision screen below.
- Playable walkthrough on this page
- Decision-focused screens
- Repo-scale clarity
Use the inline walkthrough for the overall flow, then inspect the still screens below for specific decision points.
DRIFT REDUCTION
How VibeSmith reduces drift
Find the active baseline
Unified inventory + search shows which Skills, Agents, Commands, Hooks, and Rules are still active across projects.
Reuse without dropping linked pieces
Copy components with dependency-aware flow so bootstrap stays coherent instead of breaking in partial ways.
Review rollout impact before writing changes
Preview and apply with conflict policy so teams can judge the blast radius before updating shared setup.
See risk before release week
Dependency graph, conflict review, and project scope views make hidden coupling easier to catch earlier.
WHY THE PROBLEM GROWS
AI coding tools speed up one repo before they explain many
Cursor, Claude Code, and MCP are strong local tools. The systems gap appears when teams need the same operating clarity across multiple repos.
Cursor's session-scoped context pushes teams to externalize reusable standards instead of relying on chat memory.
Multi-scope memory/settings in Claude Code increase consistency overhead without a shared operating layer.
MCP expands capability, but server scope and permission boundaries need explicit review discipline.
FIRST-WEEK METRICS
What to measure in week one
You can judge early value from one repo. The question is whether the baseline becomes clearer, not whether a big rollout already happened.
Outcome 01
Faster first stable setup
Time from install to a baseline your team would actually keep.
Outcome 02
Fewer repo-to-repo surprises
Whether copied rules, commands, and components stay coherent after the first reuse.
Outcome 03
Clearer cleanup targets
Which stale, conflicting, or overgrown assets you can remove before context quality degrades.
ADOPTION PATH
Get to proof with one repo first
You do not need an org-wide migration. Start small, measure drift, then expand only if the baseline improves.
Step 1
Connect one live repo
Install Community and scan the repo that keeps reopening the same setup questions.
- Output: first baseline of active components and drift points
- Output: install friction notes
Step 2
Review reuse and dependency risk
Use inventory, detail, and dependency views to see what breaks when setup is copied by memory.
- Output: cleanup candidates
- Output: linked dependency risks
Step 3
Expand only after one workflow feels cleaner
Decide whether another repo should adopt the same baseline after one team can explain the setup clearly.
- Output: keep / fix / expand decision
- Output: shortlist for deeper collaboration or Pro
Fit & Boundary
Use it when component drift is already costing delivery speed.
Clear boundaries help multi-repo teams decide quickly without overcommitting.
Strong fit
- Three or more active repos share one delivery schedule.
- Kickoff quality drops because rules are handed off manually.
- Release reviews often find dependency issues too late.
Not ideal yet
- Single-repo setups with stable standards and low change frequency.
- Workflows not ready to define clear criteria for component review decisions.
- Workflows expecting one-click automation without rollout discipline.
What is intentionally out of scope in this phase
Current scope stays narrow on purpose. The goal is visible proof before wider automation promises.
- No forced repository rewrite. Existing structure is mapped first.
- Cloud-wide policy automation is a later phase, not a day-one requirement.
- Shared rollout layers expand only after repeated evidence from real repo audits.
Download
Get VibeSmith Community Build
Choose the release hub, latest install package, or Homebrew fallback path.
Option A. Release Hub
Open latest release notes and download public community assets.
Latest release page
https://gitlab.com/aroido/vibesmith-community/-/releases/permalink/latestLatest install package
https://gitlab.com/aroido/vibesmith-community/-/releases/permalink/latestCommunity repository
https://gitlab.com/aroido/vibesmith-communityRelease notes and install artifacts are public. If direct package links change, open the latest release page first.
Option B. Homebrew Guide
Tap and cask are live. Install with Homebrew, or use the greedy upgrade path if VibeSmith is already on this Mac.
Install and upgrade
brew update
brew tap aroido/vibesmith https://gitlab.com/aroido/homebrew-vibesmith.git
brew install --cask aroido/vibesmith/vibesmith
# If an older version is already installed:
brew update
brew upgrade --cask --greedy aroido/vibesmith/vibesmithPrefer this path for Homebrew installs and upgrades. Option A release assets are still available if you want the direct package instead.
Start with one repo. Make drift visible first.
Community is the fastest way to see whether component sprawl, hidden dependencies, and context-heavy setup are already slowing your team. If you want outside eyes on one live repo, request an audit after the demo or install pass.