VibeCodeProjects

A collection of projects and reusable Claude Code skills.

Structure

VibeCodeProjects/
├── .claude/
│   └── skills/              # Generic, reusable skills available to all projects
│       ├── brainstorm/      # Solution architecture and design discussions
│       ├── plan/            # Execution planning from architecture documents
│       ├── execute/         # Phase-by-phase implementation with progress tracking
│       └── review/          # Comprehensive code review with prioritized fixes
│
└── projects/                # Individual project folders
    ├── salesforce-nl-chat/  # Salesforce natural language query tool
    └── pacman/              # Pacman game

Generic Skills

Skills in .claude/skills/ are available across all projects when working in this repository.

/brainstorm

Collaborative solution architecture and design discussions. Use this skill when:

• Planning new features or systems
• Evaluating technical approaches
• Designing architecture before implementation
• Exploring trade-offs between different solutions

Usage: /brainstorm <problem or feature to design>

Output: Creates ARCHITECTURE.md with design decisions and technical approach.

/plan

Create and manage step-by-step execution plans from architecture documents. Use this skill when:

• Converting architecture designs into actionable implementation steps
• Breaking down complex projects into phases and tasks
• Tracking progress with automatic checkpoint updates
• Adapting plans based on blockers or changing requirements

Usage: /plan [optional: path to architecture document]

Output: Creates EXECUTION_PLAN.md with phases, tasks, checkpoints, and progress tracking.

Workflow: Use /brainstorm first to design the solution, then /plan to create the execution roadmap.

/execute

Execute implementation plans phase-by-phase with progress tracking and automatic checkpoints. Use this skill when:

• Implementing the tasks defined in EXECUTION_PLAN.md
• Need systematic, phase-by-phase execution with approval gates
• Want automatic progress tracking via TodoWrite
• Need graceful error handling with pause-and-ask behavior

Usage: /execute [optional: phase number or 'resume']

Features:

• Phase-by-phase execution with user approval between phases
• Automatic TodoWrite integration for real-time progress visibility
• Pauses on errors to ask for guidance
• Verifies success criteria before marking tasks complete
• Keeps EXECUTION_PLAN.md synchronized with actual progress
• Runs final verification checks upon completion

Complete Workflow: /brainstorm → ARCHITECTURE.md → /plan → EXECUTION_PLAN.md → /execute → Implementation

/review

Comprehensive code review with failure scenario analysis, security checks, and prioritized fix suggestions. Use this skill when:

• Validating code quality after implementation
• Identifying security vulnerabilities and error handling gaps
• Finding performance inefficiencies and testing gaps
• Ensuring architecture compliance
• Need to prioritize which issues to fix first

Usage: /review [optional: specific files or directories]

Categories Analyzed:

• Security vulnerabilities (SQL injection, XSS, exposed secrets, etc.)
• Error handling gaps (missing try-catch, unhandled edge cases)
• Performance inefficiencies (N+1 queries, blocking I/O, memory leaks)
• Code quality issues (duplication, complexity, maintainability)
• Testing gaps (missing coverage, untested edge cases)
• Architecture violations (deviations from ARCHITECTURE.md)

Process:

1. Reviews both new code from execution and entire project
2. Categorizes findings by severity (Critical/High/Medium/Low)
3. Analyzes failure scenarios for each issue
4. Consults with you to prioritize which fixes to address
5. Adds prioritized fixes as new phase in EXECUTION_PLAN.md

Complete Workflow: /brainstorm → /plan → /execute → /review → Fix execution → Production-ready

Projects

1. Salesforce NL Chat

projects/salesforce-nl-chat/

Query Salesforce data using natural language and get results as formatted tables.

Quick start:

cd projects/salesforce-nl-chat
pip install -r requirements.txt

Then in Claude Code:

/salesforce-query show me all opportunities closing this quarter

Features:

• Natural language to SOQL translation
• Dynamic schema discovery from your Salesforce org
• Support for Accounts, Opportunities, Contacts, Leads, Cases
• Automatic pagination (up to 2000 records)
• Secure (credentials never stored)

2. Pacman

projects/pacman/

Classic Pacman game implementation.

Adding New Projects

To add a new project:

1. Create a new folder under projects/:

   mkdir projects/my-new-project

2. (Optional) Add project-specific skills:

   mkdir -p projects/my-new-project/.claude/skills/my-skill

3. Add project files and documentation

Working with Skills

Generic Skills (Available Everywhere)

Place in .claude/skills/ at the root level. These skills are available when working anywhere in the repository.

Project-Specific Skills

Place in projects/<project-name>/.claude/skills/. These skills are only available when working within that project's directory.

Getting Started

1. Clone this repository

   git clone <repo-url>
   cd VibeCodeProjects

2. Use the complete development workflow

   /brainstorm <your problem>    # Design the solution → ARCHITECTURE.md
   /plan                          # Create execution plan → EXECUTION_PLAN.md
   /execute                       # Implement phase-by-phase
   /review                        # Code review + prioritize fixes
   /execute [phase]               # Implement fixes → Production-ready!
   

3. Work on a specific project

   cd projects/salesforce-nl-chat
   # Project-specific skills like /salesforce-query are now available

Contributing

When adding new projects:

• Keep them self-contained in projects/ folder
• Include a README.md in the project folder
• Document any dependencies
• Consider if skills should be generic (root level) or project-specific