vibekit

Explore options, trade-offs, and decision paths without implementing code. Use when the user asks to brainstorm, compare approaches, choose architecture, or save a durable decision note.

Plan and implement safe schema, migration, relationship, index, query, and backfill changes with rollback awareness. Use when data shape or persistence contracts change.

Manage deployment, Docker, CI/CD, environment, secrets, and infrastructure changes with rollback and verification. Use for operational config or release safety work.

Create, update, and audit durable project documentation. Use when code, setup, workflow, architecture, API behavior, or project structure must be reflected in docs.

Implement planned product or code changes phase by phase using repo patterns and verification. Use when the user asks to build, modify, or finish implementation work.

Coordinate multi-specialist work, handoffs, blockers, and durable progress artifacts. Use when tasks span roles, phases, or parallel workstreams.

Create structured implementation plans with repository research, phased execution, risks, and verification. Use when work is unclear, risky, multi-file, or the user asks for a plan.

Gather and synthesize repo, official documentation, release, issue, design, or incident context into durable notes. Use when planning or implementation needs researched evidence.

Review code or plans for OWASP-minded security risks, secret handling, authorization gaps, data exposure, and unsafe operational assumptions. Use for security audits or sensitive changes.

Write, fix, and run unit, integration, regression, browser, and end-to-end tests. Use when proving behavior, debugging failures, or improving coverage.

Design and implement accessible, responsive UI changes using existing components and styling patterns. Use for interface design, component states, design fidelity, and UX polish.

Use when a task benefits from a second-opinion reasoning pass, architecture comparison, focused file analysis, or batch synthesis via OpenRouter-backed MCP tools.

Use when a task needs current official library or framework documentation beyond what the repo already shows.

Use when implementing or reviewing UI from Figma files, frames, or design-system context.

Use when work depends on GitHub issues, pull requests, reviews, workflows, releases, or discussions beyond local git state.

Use when you need browser reproduction, UI inspection, screenshots, or flow verification in a running app.

Use when debugging production issues, stack traces, incidents, releases, or regressions using Sentry data.