Archive
Latest entries
Each article is written around the concrete problems VibeSmith is trying to solve: setup drift, context handoff, hidden dependencies, and governance across multiple AI coding repositories.
Mar 11, 2026 · 7 min read
Unused skills, agents, commands, hooks, and rules are not passive clutter. They add search noise, distort AI context, and make cross-repo reuse riskier unless teams clean them deliberately.
- vibesmith
- ai-coding
- component-operations
Read article
Mar 11, 2026 · 4 min read
Cursor, Claude Code, MCP, and GitLab Duo can accelerate one repo quickly. The real systems problem begins when standards, dependencies, and context have to survive across many repos.
- multi-repo
- ai-coding
- vibesmith
Read article
Mar 10, 2026 · 4 min read
Cursor Rules and AGENTS.md solve different parts of the same problem. Teams that use both deliberately get more durable AI coding context across repositories.
Read article
Mar 9, 2026 · 4 min read
Claude Code is increasingly powerful, but multi-repo teams get the most leverage from shared hooks, project commands, and durable review gates rather than one-off prompts.
Read article
Mar 8, 2026 · 3 min read
MCP matters because it turns tool integrations into a shared protocol. It does not solve standards, naming, approvals, or dependency visibility by itself.
- mcp
- ai-infrastructure
- workflows
Read article