Introduction

Vikit extends Claude Code with 80+ specialized skills across 10 modular packages — plan, implement, test, review, and ship features with a single slash command.

Start Here

STEP 01Install vikitSet up the CLI, configure access, run your first command.STEP 02Learn the kitsHow skills, agents, and slash commands fit together.STEP 03Run a workflowPlan to implement to test to review, end to end.

What is Vikit?

Vikit extends Claude Code with specialized skill packages for the whole software lifecycle. Instead of writing prompts from scratch, you call workflows tuned for speed and quality.

Every skill is a slash command — for example /vk:eng:fix — installed by vikit-cli into ~/.claude/skills/. Skills are grouped into packages, so you install only what you need, and vikit-engineer ships everywhere as the core engineering workflow.

The 10 packages

Each package focuses on one area of the development lifecycle:

vikit-engineer — The core engineering workflow: planning, implementation, debugging, testing, git, code review, and ship.
vikit-ai — Image, video, and audio generation, multimodal analysis, context management.
vikit-backend — APIs, databases, auth, and deployment.
vikit-frontend — Web UI, testing, and design systems.
vikit-creative — Copywriting, brand design, and UI/UX.
vikit-integrations — Third-party services and platform SDKs.
vikit-research — Autonomous research and codebase analysis.
vikit-ops — Project management and team orchestration.
vikit-docs — Documentation management and visualization.
vikit-labs — Experimental: 3D, video, shaders, and code analysis.

How it works

Describe a feature in one line. The planner agent spawns researcher agents in parallel, drafts a plan under plans/, then Claude Code implements it while the tester and code-reviewer agents validate the result.

planner → researcher → developer → tester → code-reviewer collaborate end to end
Code, tests, and docs/ updates land in a clean conventional commit

/vk:eng:plan add user authentication
Implement the plan
/vk:eng:test
/vk:eng:git cm

Why use Vikit?

Speed — structured workflows replace repetitive prompting for feature work
Quality — battle-tested skill prompts reduce bugs and technical debt
Consistency — the same development patterns across your whole team
Modular — install one package or the full suite; re-running vk init is safe
Composable — specialized agents collaborate across the full lifecycle

Where to start

New to Vikit? Start with vikit-engineer — the core workflow used in every project. Add packages as you need them: vikit-ai for generation, vikit-backend for APIs and databases, vikit-frontend for UI.

Next steps

Installation — Set up vikit-cli and install the packages you need.
Quick Start — Ship your first feature fast.
CLI Reference — Every vikit-cli command.
Browse engineer skills — Every skill in the core package.