Basic Workflow

Step-by-step guide to the vibe coding development workflow.

Development Workflow Overview

Follow this workflow for all code changes. Never skip steps!

Step 1: Start with Plan Mode

Before writing any code, tell Claude which app you're working on and use Plan Mode to analyze your request. This ensures Claude understands the monorepo guidelines and creates a proper feature branch.

Start your work session with this prompt
Claude prompt
my-app-name: I want to work on this app. First, use PLAN MODE to analyze my request and the Monorepo guidelines (CLAUDE.md). Start from the develop branch and create a feature branch for the following task. Ask me questions to clarify if needed. What I want to do: - [ ] Add feature / Fix issue / Update documentation - [ ] [Describe what you want to accomplish] [Add any additional context or requirements here]

Claude will:

  1. Read the monorepo guidelines (CLAUDE.md)
  2. Analyze your request and ask clarifying questions
  3. Create a plan for implementation
  4. Create a feature branch from develop
Or create the branch yourselfbash
# Switch to develop and pull latest
git checkout develop
git pull origin develop

# Create your feature branch
git checkout -b feature/your-feature-name

Step 2: Make Your Changes

  • Write code with AI assistance
  • Test locally with pnpm dev
  • Critical: Run build before committing
Ask Claude to run local verification
Claude prompt
Start the development server for my-app-name and then run the build to verify everything compiles correctly.
Or run it yourselfbash
# Start development server
pnpm dev:your-app-name

# REQUIRED: Test build before committing
pnpm build:your-app-name

Step 3: Commit, Push, and Create PR

Once your changes are ready and the build passes, ask Claude to commit your changes and create a Pull Request to develop.

Ask Claude to commit and create a PR
Claude prompt
The local test was good. Commit my changes and create a Pull Request to develop.

Claude will:

  1. Stage and commit your changes with a proper commit message
  2. Push to the remote branch
  3. Create a Pull Request to develop using gh pr create
  4. Return the PR URL for you to review
Or run it yourselfbash
# Stage and commit
git add .
git commit -m "feat: add new feature description"

# Push to remote
git push -u origin feature/your-feature-name

# Create PR to develop
gh pr create --base develop --fill

Commit Message Format

PrefixUse For
feat:New features
fix:Bug fixes
docs:Documentation
chore:Maintenance

Step 4: Wait for CI and Review

After creating the PR:

  1. CI checks will run automatically (linting, type checking, building)
  2. Wait for all checks to pass (green checkmarks)
  3. Review the PR description and make any edits if needed
  4. Once approved and checks pass, merge the PR

Step 5: Merge and Deploy

  • Staging: Merge to develop → auto-deploys to staging
  • Production: Merge develop to main → auto-deploys to production

Workflow Quiz

Quiz

What should you do BEFORE committing your changes?

Common Mistakes to Avoid

  • ❌ Committing directly to develop or main
  • ❌ Skipping local build verification
  • ❌ Not pulling latest changes before creating branch
  • ❌ Using unclear commit messages