Built by world-class engineers, for vibecoders at flowser.ai — AI Agents with computers for GTM

vibecode-pro-max-kit

Stop your AI from coding before it thinks — and forgetting every detailed prompt from you.This harness turns any AI coding agent into a spec-driven engineering teamthat researches, plans, ships production-grade code, and self-improves its memory to survive context-rotting even 6 months later.

🔬 Spec-driven development for AI agents 📋 Auto-generates PRDs, manages backlogs, routes context automatically 🧠 Self-improving knowledge base that compounds as you ship ⚡ Runs autonomously for hours on large tasks without losing state 🤝 Plans and specs are shareable — devs, PMs, and stakeholders review the same artifacts

🚀 Install (30 seconds)

curl -fsSL https://raw.githubusercontent.com/withkynam/vibecode-pro-max-kit/main/install.sh | bash

Then open Claude Code and say:

Run vc-setup

That's it. The setup skill detects your stack, asks about your project (a real conversation, not a checklist), scaffolds the process directory, deep-scans your codebase, and populates context files with actual content — not placeholders.

your-project/
├── .claude/
│   ├── agents/              # 🤖 12 specialized agent definitions
│   │   ├── vc-research-agent.md
│   │   ├── vc-execute-agent.md
│   │   └── ...
│   ├── skills/              # ⚡ 31 auto-discovered skills
│   │   ├── vc-generate-plan/
│   │   ├── vc-security/
│   │   ├── vc-scout/
│   │   └── ...
│   └── hooks/               # 🪝 7 lifecycle hooks
│       ├── privacy-block.cjs
│       ├── scout-block.cjs
│       └── ...
├── .codex/
│   └── agents/              # 🔄 Mirrored agents for Codex
├── CLAUDE.md                # 📋 Orchestrator + routing rules
├── AGENTS.md                # 📖 Agent registry
└── process/                 # 🧠 Created by vc-setup (not install)
    └── ...

• Fresh project? Installs the full harness, then vc-setup studies your codebase
• Existing .claude/ config? Backs up to .vibecode-backup/, installs fresh, restores your settings.json
• Existing process/ directory? Never touched by install — vc-setup handles migration intelligently
• Existing CLAUDE.md? Backed up as CLAUDE.md.pre-vibecode, harness version installed

First, install the vibecode-pro-max-kit agent harness by running this command:

curl -fsSL https://raw.githubusercontent.com/withkynam/vibecode-pro-max-kit/main/install.sh | bash

After the install completes, run vc-setup to configure everything for this project.

Follow the full interactive flow:

1. DETECT — Read package.json, detect my stack (framework, package manager, monorepo
   structure, test framework, database, auth). Also check if I have any existing .claude/,
   process/, or context files from a previous setup.

2. SHOW ME WHAT YOU FOUND — Present a summary of the detection results and wait for me
   to confirm before continuing. If this is an existing project with process/ folders or
   context files, tell me what you found and what looks good vs what could be improved.

3. ASK ME ABOUT THE PROJECT — Before scaffolding or scanning, have a real conversation
   with me about this project. Don't just ask a fixed list of questions and move on — ask
   follow-ups based on my answers, probe deeper on anything vague, and keep going until
   you genuinely understand the project. Start with the basics (what is this? who uses it?),
   then dig into architecture, features, conventions, pain points, and anything else that
   matters. Summarize your understanding back to me and confirm it's correct before mov