# The Collaborative Code Generation Framework - By VibeCodeCleanup.org V1.0

## 1. Project Context

### Project Description
- **Project Name:**
- **Project Overview:** [A brief paragraph explaining the project's purpose and state]

### Memory Injection
- **Reference Files:** [List of files to reference, e.g., `@project_milestones.md`, `@documentation.md`, `user_schema.json`]
- **Project Dependencies:** [List of libraries, frameworks, and versions]

## 2. The Problem Statement

**Objective:**
**Description:** [A detailed, high-level description of the task]
**Current State:** [Optional: Existing code or a description of the current situation]
**Desired Outcome:** [A specific, measurable outcome, e.g., "A Python function that returns a sorted list of unique words from a text file"]

## 3. The Clarification Phase: Pre-Coding Check

**Directive:** Before providing any code, you must first ask me a series of questions to clarify my request. Your goal is to ensure you have a complete understanding of my requirements and constraints.
- **Condition:** You are only to provide a solution after I have answered all of your questions and given you the explicit keyword: ****

## 4. The Request: Step-by-Step Task Breakdown

**Directive:** You will solve this problem using a step-by-step approach. Do not attempt to complete the entire task at once. You will follow a Chain of Thought.
1. **Step 1:** [First specific action, e.g., "Create the main `User` class with properties `id`, `name`, and `email`."]
2. **Step 2:**
3. **Step 3:** [And so on...]

## 5. Technical Requirements & Constraints

**Languages & Tools:**
**Code Style & Standards:** [e.g., "Follow PEP 8," "Use descriptive variable names," "Add docstrings for all functions"]
**Security & Performance:**
**Examples:** [Provide a few examples of desired input/output or existing code snippets]

## 6. Validation & Review

**Directive:** Remember that you are an assistant, not a replacement. All code you provide will be subject to a thorough human review and testing.
**Key Checks:**
- Sanity-check the output for accuracy and logic.
- Validate the code compiles and passes all unit and integration tests.
- Review for security vulnerabilities.

## 7. Refinement & Debugging

**Directive:** If the output is incorrect, I will provide you with the exact error message, a description of the bug, and the intended functionality. You will then provide a fixed version and an explanation of the changes.

**Example Prompt:**
"The code you provided isn't working. The error message is: [paste error message]. The function is supposed to do X, but it is currently doing Y. Can you explain what went wrong and provide the corrected code?"