folder_structure.md•13.4 kB
# VibeCoding System Folder Structure
## Root Directory Structure
```
vibeCoding-template/
├── .vibecoding/ # ✅ Core VibeCoding configuration (IMPLEMENTED)
│ ├── config/ # ✅ Configuration files
│ │ └── vibe.config.json # ✅ Main configuration
│ ├── context/ # ✅ Persistent context storage
│ ├── conversations/ # ✅ Conversation history
│ └── prompts/ # ✅ AI Prompt System (IMPLEMENTED)
│ ├── core/ # ✅ Core system prompts
│ ├── services/ # ✅ Service-specific prompts
│ ├── workflows/ # ✅ Workflow prompts
│ └── README.md # ✅ Prompt system documentation
│
├── vibe-services/ # ✅ MCP Service Collection (IMPLEMENTED)
│ ├── context-manager/ # ✅ Context Management Service
│ │ ├── index.ts # ✅ MCP server implementation
│ │ ├── package.json # ✅ Service dependencies
│ │ └── tsconfig.json # ✅ TypeScript config
│ ├── code-generator/ # ✅ Code Generation Service
│ │ ├── index.ts # ✅ MCP server implementation
│ │ ├── package.json # ✅ Service dependencies
│ │ └── tsconfig.json # ✅ TypeScript config
│ ├── dependency-tracker/ # ✅ Dependency Tracking Service
│ │ ├── index.ts # ✅ MCP server implementation
│ │ ├── package.json # ✅ Service dependencies
│ │ └── tsconfig.json # ✅ TypeScript config
│ ├── test-validator/ # ✅ Testing & Validation Service
│ │ ├── index.ts # ✅ MCP server implementation
│ │ ├── package.json # ✅ Service dependencies
│ │ └── tsconfig.json # ✅ TypeScript config
│ ├── doc-generator/ # ✅ Documentation Service
│ │ ├── index.ts # ✅ MCP server implementation
│ │ ├── package.json # ✅ Service dependencies
│ │ └── tsconfig.json # ✅ TypeScript config
│ └── deployment-manager/ # ✅ Deployment Service
│ ├── index.ts # ✅ MCP server implementation
│ ├── package.json # ✅ Service dependencies
│ └── tsconfig.json # ✅ TypeScript config
│
├── dist/ # ✅ Built Services (GENERATED)
│ └── vibe-services/ # ✅ Compiled MCP services
│ ├── context-manager/ # ✅ Built context manager
│ │ └── index.js # ✅ Executable MCP server
│ ├── code-generator/ # ✅ Built code generator
│ │ └── index.js # ✅ Executable MCP server
│ ├── dependency-tracker/ # ✅ Built dependency tracker
│ │ └── index.js # ✅ Executable MCP server
│ ├── test-validator/ # ✅ Built test validator
│ │ └── index.js # ✅ Executable MCP server
│ ├── doc-generator/ # ✅ Built doc generator
│ │ └── index.js # ✅ Executable MCP server
│ └── deployment-manager/ # ✅ Built deployment manager
│ └── index.js # ✅ Executable MCP server
│
├── src/ # ✅ Core Application Source (IMPLEMENTED)
│ ├── index.ts # ✅ Main entry point
│ ├── core/ # ✅ Core Components
│ │ └── orchestrator.ts # ✅ VibeCoding Orchestrator
│ ├── services/ # ✅ Service Integration
│ │ └── mcp-integration.ts # ✅ MCP service integration
│ ├── cli/ # ✅ CLI Implementation
│ │ └── index.ts # ✅ CLI commands
│ ├── types/ # ⚪ Empty directory (types integrated elsewhere)
│ └── utils/ # ✅ Utility Functions
│ ├── project-utils.ts # ✅ Project management utilities
│ ├── documentation.ts # ✅ Documentation generation
│ └── prompt-manager.ts # ✅ Prompt Management System
│
├── 0_discovery/ # ✅ Phase 0: Discovery
│ ├── conversations/ # User conversations
│ ├── clarifications/ # Requirement clarifications
│ └── requirements/ # Gathered requirements
│
├── 1_design/ # ✅ Phase 1: Design
│ ├── architecture/ # Architecture documents
│ ├── api-contracts/ # API specifications
│ └── flow-diagrams/ # System flow diagrams
│
├── 2_implementation/ # ✅ Phase 2: Implementation
│ ├── src/ # Source code
│ ├── tests/ # Test files
│ └── scripts/ # Utility scripts
│
├── 3_validation/ # ✅ Phase 3: Validation
│ ├── test-reports/ # Test execution reports
│ ├── quality-metrics/ # Code quality metrics
│ └── benchmarks/ # Performance benchmarks
│
├── 4_deployment/ # ✅ Phase 4: Deployment
│ ├── environments/ # Environment configs
│ ├── ci-cd/ # CI/CD pipelines
│ └── monitoring/ # Monitoring configs
│
├── knowledge-base/ # ✅ Knowledge Accumulation
│ ├── patterns/ # Reusable patterns
│ ├── solutions/ # Problem solutions
│ └── retrospectives/ # Project retrospectives
│
├── design_templates/ # ✅ Original design templates
├── scripts/ # ✅ Utility Scripts
│ ├── build-all.ps1 # ✅ Build all services
│ └── test-prompts.js # ✅ Prompt system validation
│
├── .vscode/ # ✅ VSCode configuration
├── .cursorrules # ✅ Cursor IDE rules
├── .gitignore # ✅ Git ignore patterns
├── package.json # ✅ Project dependencies
├── package-lock.json # ✅ Dependency lock file
├── tsconfig.json # ✅ TypeScript configuration
├── README.md # ✅ Main project documentation (CONSOLIDATED)
├── VIBECODING_TOOLS_REFERENCE.md # ✅ Complete tool reference manual (NEW)
├── VIBECODING_COMMAND_REDESIGN.md # ✅ UX-based command redesign system (NEW)
├── mcp-config-examples.json # ✅ MCP configuration examples collection (NEW)
├── IDE_SETUP_GUIDE.md # ✅ Complete IDE setup guide
├── CURSOR_MCP_CLARIFICATION.md # ✅ Cursor MCP usage guide
├── MCP_SETUP_GUIDE.md # ✅ MCP service setup guide
├── DEPLOY_MCP_GUIDE.md # ✅ Deployment completion guide
├── folder_structure.md # ✅ This file
└── LICENSE # ✅ MIT License
```
## File Descriptions
### Configuration Files
- **`package.json`**: Node.js project configuration and dependencies ✅
- **`tsconfig.json`**: TypeScript compiler options ✅
- **`.vibecoding/config/vibe.config.json`**: Central configuration for all VibeCoding services ✅
- **`.vibecoding/prompts/`**: Complete AI prompt system with specialized prompts ✅
### Core Components
- **`src/index.ts`**: Main application entry point ✅
- **`src/core/orchestrator.ts`**: Main orchestrator that coordinates all services ✅
- **`src/cli/index.ts`**: Command-line interface implementation ✅
- **`src/services/mcp-integration.ts`**: Integration layer for MCP services ✅
- **`src/utils/project-utils.ts`**: Project management utilities ✅
- **`src/utils/documentation.ts`**: Documentation generation utilities ✅
- **`src/utils/prompt-manager.ts`**: Centralized prompt management and loading system ✅
### MCP Services ✅ ALL IMPLEMENTED
Each service in `vibe-services/` follows the MCP server pattern:
- **Independent TypeScript implementation** ✅
- **Own package.json for dependencies** ✅
- **Communicates via MCP protocol** ✅
- **Built to dist/ directory for execution** ✅
#### Available Services:
1. **context-manager**: Project clarification, persistent context, and progress tracking ✅
2. **code-generator**: AI-driven code generation with template fallback ✅
3. **dependency-tracker**: Smart dependency analysis and security scanning ✅
4. **test-validator**: Automated test generation and quality analysis ✅
5. **doc-generator**: PRD creation and intelligent documentation ✅
6. **deployment-manager**: Automated CI/CD and infrastructure setup ✅
### Development Phases ✅
Each numbered directory (0-4) represents a development phase:
- **0_discovery**: Requirement gathering through conversations ✅
- **1_design**: Architecture and API design artifacts ✅
- **2_implementation**: Actual code implementation ✅
- **3_validation**: Testing and quality assurance ✅
- **4_deployment**: Deployment and monitoring setup ✅
### Knowledge Base ✅
Automatically captures and stores:
- **patterns**: Reusable design patterns discovered ✅
- **solutions**: Solutions to common problems ✅
- **retrospectives**: Lessons learned from each project ✅
### Documentation ✅
Comprehensive documentation for all aspects:
- **README.md**: Main project documentation (consolidated from multiple sources) ✅
- **VIBECODING_TOOLS_REFERENCE.md**: Complete tool reference manual with all 6 services ✅
- **VIBECODING_COMMAND_REDESIGN.md**: UX-based command redesign system (77% shorter commands) ✅
- **mcp-config-examples.json**: MCP configuration examples collection for various scenarios ✅
- **IDE_SETUP_GUIDE.md**: Complete IDE setup guide with troubleshooting ✅
- **CURSOR_MCP_CLARIFICATION.md**: Cursor-specific MCP usage guide ✅
- **MCP_SETUP_GUIDE.md**: MCP service configuration guide with advanced customization ✅
- **DEPLOY_MCP_GUIDE.md**: Deployment completion confirmation ✅
## Usage Flow
1. **Initialize**: `npm install && npm run build` creates dist structure ✅
2. **Develop**: Use MCP services through IDE integration ✅
3. **Progress**: System automatically manages phase progression ✅
4. **Knowledge**: Patterns and solutions are captured automatically ✅
5. **Deploy**: Final deployment configurations in phase 4 ✅
## Build Process ✅
```bash
# Install dependencies
npm install
# Build all MCP services
npm run build
# Test services
npm run mcp:context-manager
npm run test:prompts
# Deploy to IDE
# See IDE_SETUP_GUIDE.md for detailed instructions
```
## Integration Points
- **MCP Protocol**: All services implement standard MCP server interface ✅
- **TypeScript**: Full type safety across all components ✅
- **IDE Integration**: Ready for Cursor, Claude Desktop, VSCode, etc. ✅
- **AI Providers**: Support for OpenAI, Anthropic, Gemini ✅
- **Template System**: Rich template library with AI enhancement ✅
## Status Summary
✅ **IMPLEMENTED & WORKING**:
- All 6 MCP services built and functional
- Core project management utilities
- Documentation generation
- TypeScript type system
- Build process and deployment
- IDE integration guides
- AI prompt system with specialized prompts
- Configuration management system
⚪ **PLACEHOLDER/EMPTY**:
- `src/types/` directory (types integrated elsewhere)
🎯 **READY FOR USE**:
The system is fully functional for conversation-driven development with all MCP services operational.
## Cleanup Summary
### Files Removed During Cleanup:
- **Debug files**: `DEBUG_RESOLUTION_REPORT.md`, `debug-tools-count.cjs`, `debug-tools-count.js`, `quick-fix-tools.cjs`
- **Process documentation**: `CLEANUP_SUMMARY.md`, `TOOL_REDUCTION_PLAN.md`
- **Redundant guides**: `QUICK_START.md`, `VibeCoding_User_SOP.md`, `SOP_Manual.md`
- **Development docs**: `development_guideline.md`, `REDESIGNED_SERVICES_ARCHITECTURE.md`
- **Template files**: `mcp-config-template.json`, `PROMPT_SYSTEM_USAGE.md`
### Files Consolidated:
- **README.md**: Now contains consolidated information from multiple sources
- **Architecture information**: Integrated into main README
- **Quick start guide**: Merged into README
- **API reference**: Consolidated in README
### Current File Count:
- **Root documentation files**: 9 (down from 20+)
- **Reduction**: 55% fewer documentation files
- **Maintainability**: Significantly improved
- **UX Enhancement**: New command system reduces input by 77%
This cleanup resulted in a much cleaner, more maintainable project structure with reduced redundancy and improved user experience.