Vibe Coding Tips

Define code style, architecture constraints, and prohibitions in project root.

Monitor context usage: 50-70% caution, 70-90% use /compact, 90%+ force /clear.

One worktree per feature branch — parallel dev without interference.

Don't let AI be PM and developer simultaneously — separate concerns.

Superpowers enforces RED/GREEN TDD — significantly reduces AI logic errors.

Vet third-party skills before install. MCP servers can read/write your codebase.

Don't describe entire project at once — brainstorm → plan → implement.

Split complex tasks to specialized sub-agents with isolated context.

Use Playwright MCP to verify UI changes visually — screenshot and interact.

Combine small focused skills instead of one monolithic prompt.

Use Vibe Rules to scan and inventory all MCP servers across your agents.

Always review skill differences across agents before syncing.

Write a failing test that reproduces the bug before attempting any fix.

Define clear handoff boundaries — what each agent receives and returns.