VibeCoders Playbook

Step 1

Install with one command (menu in interactive terminals)

PowerShell

iex "& { $(irm https://raw.githubusercontent.com/YoussefSelk/VibeCode-PlayBook/main/scripts/install.ps1) }"

Bash

curl -fsSL https://raw.githubusercontent.com/YoussefSelk/VibeCode-PlayBook/main/scripts/install.sh | bash

The installer always adds common files plus one assistant pack. If interactive, it prompts you to choose the assistant. In non-interactive environments, it falls back to codex. You can always force selection with -Assistant claude|github|codex (Bash: --assistant claude|github|codex).

Claude pack contents: CLAUDE.md, .claude/commands/*, and .claude/agents/*.

Step 1b

Installer options explained

Option PowerShell Bash What it does
Destination -Destination --destination Install files into a specific project directory.
Assistant pack -Assistant codex|claude|github --assistant codex|claude|github Forces one assistant pack and skips menu selection.
Overwrite -Force --force Overwrites files that already exist in target path.
Backup before overwrite -Backup --backup Creates timestamped .bak files before overwrite (with Force).
Custom source base -RepoBase --repo-base Downloads from a custom raw source URL (testing/mirror use).

Step 1c

Every common command pattern

PowerShell examples

  • Menu mode run the default command and choose 1/2/3
  • Force Claude -Assistant claude
  • Install to folder -Destination 'C:\\path\\to\\project'
  • Overwrite safely -Force -Backup
  • Custom source -RepoBase https://raw.githubusercontent.com/<owner>/<repo>/main

Bash examples

  • Menu mode run the default command and choose 1/2/3
  • Force GitHub --assistant github
  • Install to folder --destination /path/to/project
  • Overwrite safely --force --backup
  • Custom source --repo-base https://raw.githubusercontent.com/<owner>/<repo>/main

Step 2

Fill the minimum context set

Required files

  • agent_docs/project_brief.md
  • agent_docs/tech_stack.md
  • agent_docs/active_context.md
  • agent_docs/verification.md

Load order for every task

  1. AGENTS.md
  2. agent_docs/active_context.md
  3. Only the specific docs needed

Step 3

Use role routing before implementation

Role Ownership
prompt-engineer Turns rough ask into actionable execution plan
db Schema, migrations, persistence contracts
backend APIs, business logic, auth, validation
frontend UI behavior, accessibility, client integration
devops CI/CD, deployment safety, environment, infra operability
tester Runtime flow and integration verification
reviewer Final risk and regression gate

Step 3b

Use a strict handoff contract between agents

Required handoff fields

  • goal
  • scope (files/symbols/flows)
  • changes
  • evidence (commands/tests/results)
  • risks (assumptions/open questions/blockers)
  • next-owner
  • done-criteria

Context-efficient research

Use .agents/reference-links.md and include only the domain section needed for the current pass.

Step 4

Run validation before closure

Runtime

Test the real user flow, not only unit behavior.

Contracts

Confirm request/response and data schema consistency.

Risk

Add security and legal checks when boundaries change.

Production-ready means implementation quality + runtime proof + reviewer-level acceptable risk.

Step 5

Enable GitHub production controls

Repository baseline

  • CODE_OF_CONDUCT.md
  • SECURITY.md
  • SUPPORT.md
  • .github/CODEOWNERS
  • .github/dependabot.yml

GitHub settings checklist

  • Protect main with required pull request reviews
  • Enable required status checks for CI workflows
  • Enable Dependency graph and Dependabot alerts
  • Enable Secret scanning and push protection when available
  • Set Pages source to GitHub Actions