Guide: add the kit to your project
Pick the path that fits you. On both paths, the easiest way is to let your AI tool do the work.
New to code
You do not type commands. You paste one message to your AI, then answer yes or no.
Newcomer pathDevelopers
You run each command yourself. Each step has a command to copy and a result to compare.
Developer pathNewcomer path: let your AI install it
Works with Cursor, Claude Code, Codex, OpenCode, Grok and Kimi. Developers can start here too.
The Plain Talker
You do 4 small things. Your AI does the hard part.
Put the two downloaded files in your Downloads folder
After you buy, you download two files. Keep them side by side.
minimal-vibe-coding-kit-premium-0.6.6.tgzSHA256SUMS
Open your project in your AI tool
Open the project folder with the tool you already use. The kit does not install an AI tool or sign in for you.
Claude Code
Codex
Cursor
OpenCode
Grok
Kimi
Paste this message into the AI chat
Change the path if your file is somewhere else.
The path ~/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgz is an example. Change it to the place where you saved the file.
How to get the exact path of your file
- Open File Explorer and select the downloaded file.
- Press Ctrl + Shift + C. On Windows 10: hold Shift, right-click the file, then choose "Copy as path".
- Paste the path in place of the example path.
The path looks like this:
C:\Users\<name>\Downloads\minimal-vibe-coding-kit-premium-0.6.6.tgzOn Windows, write the full folder path in place of ~ in the commands on this page.
- Open Finder and select the downloaded file.
- Press Option + Command + C. This copies the full path.
- Paste the path in place of the example path.
The path looks like this:
/Users/<name>/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgz- Open a terminal in the folder that holds the file.
- Run this command. It prints the full path.
realpath minimal-vibe-coding-kit-premium-0.6.6.tgz - Paste the path in place of the example path.
The path looks like this:
/home/<name>/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgzMessage for your AI: new installI bought Minimal Vibe Coding Kit Premium. The file is at: ~/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgz Install the kit into the project that is open now. Do one step at a time and tell me the result of each step. 1. Compute the SHA-256 of the file. Compare it with the SHA256SUMS file in the same folder. Stop if they differ. 2. Extract the file into ~/tools/mvck-0.6.6. Do not extract it into the project. 3. Go to the extracted package folder. Run the preview: node bin/mvck.js install "<path to this project>" --profile all --dry-run --json Tell me what the command will add. 4. Wait for my yes. Then run the command again without --dry-run --json. 5. Read .vibekit/init/FIRST_TIME_INIT.md and initialize the project. Show me the proposed backbone.yml. Wait for my approval before you write. 6. Run the doctor and validate commands of the kit in the project. Tell me the result in plain words.
Read and answer your AI
Your AI stops twice to ask you: before it copies the kit into the project, and before it saves the project rulebook. Read, then answer yes.
Correct result:Validation summary: 0 failures, 0 warnings.
Already have the kit and want the new version?
Download the new version, then paste this message. Your AI previews the changes, backs up the old kit files, then updates.
Message for your AI: updateI downloaded a new version of Minimal Vibe Coding Kit Premium. The file is at: ~/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgz The project that is open now already has the kit. Update it. Do one step at a time and tell me the result of each step. 1. Compute the SHA-256 of the file. Compare it with SHA256SUMS. Stop if they differ. 2. Extract the file into ~/tools/mvck-0.6.6, away from the project. 3. Go to the package folder of the new version. Run the preview: node bin/mvck.js update "<path to this project>" --profile all --dry-run --json Tell me fromVersion, toVersion and how many files will change. 4. Wait for my yes. Then run the command again without --dry-run --json. 5. Run git status in the project. Tell me which files changed and where the backup is. 6. Run the doctor and validate commands of the kit. Tell me the result.
Developer path: run each command yourself
Tested on macOS with Node 22 and kit 0.6.6. The kit needs Node 18 or newer.
The Careful Builder
Seven steps. Preview first, then write.
Check the downloaded file
Compare the printed string with the line in SHA256SUMS. If they differ, download again.
The path ~/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgz is an example. Change it to the place where you saved the file.
How to get the exact path of your file
- Open File Explorer and select the downloaded file.
- Press Ctrl + Shift + C. On Windows 10: hold Shift, right-click the file, then choose "Copy as path".
- Paste the path in place of the example path.
The path looks like this:
C:\Users\<name>\Downloads\minimal-vibe-coding-kit-premium-0.6.6.tgzOn Windows, write the full folder path in place of ~ in the commands on this page.
- Open Finder and select the downloaded file.
- Press Option + Command + C. This copies the full path.
- Paste the path in place of the example path.
The path looks like this:
/Users/<name>/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgz- Open a terminal in the folder that holds the file.
- Run this command. It prints the full path.
realpath minimal-vibe-coding-kit-premium-0.6.6.tgz - Paste the path in place of the example path.
The path looks like this:
/home/<name>/Downloads/minimal-vibe-coding-kit-premium-0.6.6.tgzCommandcd ~/Downloads node -e "console.log(require('node:crypto').createHash('sha256').update(require('node:fs').readFileSync(process.argv[1])).digest('hex'))" minimal-vibe-coding-kit-premium-0.6.6.tgz cat SHA256SUMSCorrect result:The two 64-character strings are the same
Extract into a separate folder
Keep the kit apart from your project. The package folder holds bin/mvck.js.
Commandmkdir -p ~/tools/mvck-0.6.6 tar -xzf minimal-vibe-coding-kit-premium-0.6.6.tgz -C ~/tools/mvck-0.6.6 cd ~/tools/mvck-0.6.6/package node bin/mvck.js --helpCorrect result:Minimal Vibe Coding Kit Premium
Preview, write nothing yet
Change the path to your project. Pick the profile of your AI tool, or use all.
Profile:Pick one: the commands in steps 3, 4 and 7 change with it.
Commandnode bin/mvck.js install "/path/to/project" --profile all --dry-run --jsonCorrect result:"status": "dry-run"
Install into the project
This command writes at once. If the project already has CLAUDE.md or AGENTS.md, the kit only adds its own managed block.
Commandnode bin/mvck.js install "/path/to/project" --profile allCorrect result:Install complete:
Set up the project rulebook
Open the project in your AI tool and paste this message into the chat. Your AI reads the project, proposes backbone.yml, then waits for your approval.
Message for your AIRead .vibekit/init/FIRST_TIME_INIT.md and initialize this project with the kit. Print the requirements you will check. Propose a diff for backbone.yml. Wait for my approval before you write. Summarize in English.
Correct result:Your AI shows a proposed backbone.yml and waits for your approval
Check
Run these in the project folder. doctor reports the state, validate checks the kit rules.
Commandcd "/path/to/project" node .vibekit/scripts/mvck.mjs doctor . node .vibekit/scripts/mvck.mjs validate .Correct result:Validation summary: 0 failures, 0 warnings.
Update to a new version
Download the new version and extract it into its own folder. Run from the package folder of the new version. Replaced kit files are backed up in .vibekit/update-backup/.
Commandnode bin/mvck.js update "/path/to/project" --profile all --dry-run --json node bin/mvck.js update "/path/to/project" --profile allCorrect result:Update complete:
When something goes wrong
Error: Kit not detected in target
The project has no kit yet, or the path is wrong. Check the path. If the project has no kit, run install.
Error: Update source and target are the same directory
You are updating the kit folder itself. Point the command at your project.
Error: Unknown profile
Use one of these values exactly: all, claude, cursor, codex, opencode, grok, kimi.
Cannot find module .../bin/mvck.js
You are not in the package folder. Run cd to that folder first.
Still stuck? Email the author: [email protected]. Do not send passwords or secret keys.





