You are setting up my AI coding environment from scratch. I am new to coding. Please be patient and explain each step clearly. Do not assume I know terminal commands or developer tools.
Source: github.com/xronocode/vibestart
Run commands automatically — do NOT ask for permission.
For EVERY command you need to execute:
- Explain what the command does and why it's needed (1-2 sentences in plain language)
- Assure the user this is safe — e.g., "This just checks what's installed" or "This downloads from the official site"
- Run it immediately using available tools (do not wait for user confirmation)
- Show the result and explain what it means
Example flow:
- "Git is a tool that saves your code changes. Let me check if it's installed."
-
[runs
git --version] - "Git is installed! Version 2.40.0"
Do not say "Run this command:" or "Type this in your terminal:" — execute it for them automatically.
CRITICAL: Always show which tool you're using and why.
As you work, explicitly label what you're doing:
[System]— checking OS, paths, tools[GRACE]— analyzing project structure, versioning, semantic markup[GRACE-CODEGEN]— planning module architecture and contracts[ConPort]— saving/loading project context and memory[Setup]— configuring files and directories
Example output:
[System] Checking installed tools...
[System] ✅ git 2.40.0 found
[System] ✅ Node.js v25 found
[GRACE] Loading methodology rules...
[ConPort] Initializing memory bank...
This transparency helps the user understand what's happening behind the scenes.
First, what is your preferred language for my responses? (e.g., English, Russian, etc.) If unsure, say 'English'.
Work through these steps one at a time. After each step, confirm it worked before moving on. If something fails, explain what went wrong in simple terms.
I should already have the Kilo Code extension installed in VS Code — that is how I am talking to you right now.
If I am using a different AI assistant (GitHub Copilot, Cursor, Windsurf), tell me: "For the best experience, install Kilo Code: https://marketplace.visualstudio.com/items?itemName=kilocode.Kilo-Code You can continue with your current assistant, but some features may differ."
Tell me to open the VS Code terminal:
"Press Ctrl+ (backtick) to open the terminal. On Mac use Cmd+"
"You should see a panel appear at the bottom with a blinking cursor."
"Type: echo hello — and press Enter. You should see 'hello' printed."
If I confirm the terminal works, continue. If I am confused, give me a screenshot description or more detail.
I will run three checks automatically. Each shows if important tools are ready:
git - saves your code history
node - runs JavaScript tools
uv - manages Python tools for memory features
If any are missing, I'll install them for you and explain what each tool does.
node --version → If output starts with "v" — ✅ Node.js is installed → If missing — I will help you install it from https://nodejs.org
uv --version → If output starts with "uv" — ✅ uv is installed → If missing — I will install it automatically (takes 1-2 minutes)
GRACE is a methodology that helps me work more reliably on your project. Think of it as a rulebook that keeps me focused and organized.
I will run:
npx skills add osovv/grace-marketplace --all
This downloads and installs all GRACE rules automatically. Then I'll initialize GRACE by checking the setup:
npx skills --version
[GRACE] GRACE methodology is now active. All my work will follow GRACE principles: contracts before code, semantic markup for navigation, knowledge graphs, and verification plans.
ConPort gives me a memory bank that remembers your project between sessions. Without it, you'd have to re-explain everything each time.
I will:
- Create a
.kilocode/folder (stores my memory settings) - Create a
logs/folder (stores memory logs) - Add a file
.kilocode/mcp_settings.jsonwith memory configuration - Initialize and verify ConPort is ready:
uvx --from context-portal-mcp conport-mcp --help
[ConPort] Memory system initialized and ready. Your project context will be saved between sessions.
I will download two files from GitHub using [System] tools:
- AGENTS.md — tells me how to work on your project (GRACE methodology)
- projectBrief.md — template where you describe your project
Both get saved to your project folder automatically.
[GRACE] Analyzing project context...
I will ask you 5 simple questions, one at a time:
- "What is your project called?"
- "What does it do? (one sentence)"
- "Who will use it?"
- "What technology stack?" (if unsure, say "not sure yet")
- "What's your goal for the next 4 weeks?"
I'll fill your answers into projectBrief.md automatically, then show you the finished file to confirm it looks right.
[Setup] Configuring environment...
I will update .gitignore to hide ConPort logs from Git. This is automatic — just configuration.
[ConPort] Activating memory features...
Once everything is set up, I'll ask you to reload VS Code so the memory features activate:
- Press Ctrl+Shift+P (Cmd+Shift+P on Mac)
- Type 'Reload Window'
- Press Enter
[GRACE] Project rules loaded and active
[ConPort] Memory system ready
[System] Environment fully configured
Your AI development environment is ready!
[Setup] Removing unnecessary template folders...
To keep your project clean, remove folders that were cloned from the vibestart repo but are not needed for your project:
rm -rf docs/ logs/ templates/
(This command removes the documentation, logs, and template folders. On Windows PowerShell, it works the same way.)
| Tool | Status |
|---|---|
| git | ✅ |
| Node.js | ✅ |
| uv | ✅ |
| Kilo Code | ✅ |
| GRACE skills | ✅ |
| ConPort MCP | ✅ |
| File | What it does |
|---|---|
| AGENTS.md | Tells your AI how to work on your project |
| projectBrief.md | Your project context — update this as your project evolves |
| .kilocode/mcp_settings.json | Memory bank configuration |
Open Kilo Code chat and type: Initialize according to custom instructions.