Meta-Project Context Builder — Unified Prompt (for Cursor / Claude)

# Meta-Project Context Builder — Unified Prompt (for Cursor / Claude)

> **Purpose**  
> Build a **Meta-Project Context Builder** for a multi-repo workspace.  
> You will scan each project to understand architecture, dependencies, and patterns, then generate:
> - `ARCHITECTURE.md` and `DEPENDENCIES.md` per project (inside `/ai` folder)  
> - `.cursor/rules/{projectName}.mdc` and `CLAUDE.md` per project (identical content)  
> - `WORKSPACE_OVERVIEW.md` (inside `/ai` folder) for the whole workspace

⚠️ **Note:** Examples are **illustrative**. Replace all example data with **real project details** discovered from code analysis.

---

## 0) Workspace Input

- **Workspace root:** `{WORKSPACE_ROOT}` (e.g., `./projects` or a monorepo).  
- Treat each **top-level folder** (and `apps/*`, `packages/*` in monorepos) as a project.  
- Detect project boundaries via manifests (e.g., `package.json`) and framework configs.

---

## 1) Workflow Overview

1. **Analyze each project**:
   - Purpose and responsibilities
   - Tech stack and frameworks
   - Directory layout and key entry points
   - Inputs/outputs and core data flows
   - Internal & external dependencies
   - Public surface: components, endpoints, events
2. **Generate AI-organized outputs**:
   - All **documentation files** (`ARCHITECTURE.md`, `DEPENDENCIES.md`) go in `/ai` folder in each project.
   - Workspace-level overview file: `/ai/WORKSPACE_OVERVIEW.md` at workspace root.
3. **Generate AI helper files for LLMs**:
   - `.cursor/rules/{projectName}.mdc`  
   - `CLAUDE.md` at project root  
   - These files contain **rules and best practices only**, no repeated context.

---

## 2) Project File Structure

For each project `{projectName}`, produce: