# CollabSpace — Vibe Coding Prompt Package
## Optimized for Claude Code

---

## How to Use This in Claude Code

This folder contains numbered prompt files. Use them one at a time in Claude Code:

### Method 1 — Direct file reference (recommended)
```bash
# In Claude Code terminal or chat:
@prompts/01_project_setup.md
```
Claude Code will read the file and execute it as instructions.

### Method 2 — Read and run
```bash
# Ask Claude Code to read and implement:
"Read @prompts/01_project_setup.md and implement everything in it"
```

### Method 3 — Sequential session
```bash
# Start a session, set context once, then work through prompts:
"Read @specs/stack_context.md first, then implement @prompts/01_project_setup.md"
```

---

## Execution Order

```
PHASE 1 — Foundation (strict order, each depends on previous)
├── prompts/01_project_setup.md
├── prompts/02_domain_models.md
├── prompts/03_signal_state.md
└── prompts/04_hub_service.md

PHASE 2 — Services (strict order)
├── prompts/05_cobrowse_service.md
├── prompts/06_session_api_service.md
└── prompts/07_bridge_service.md

PHASE 3 — Components (can be parallelized across developers)
├── prompts/08_toolbar_component.md
├── prompts/09_session_dashboard.md
├── prompts/10_create_session.md
├── prompts/11_detail_panel.md
├── prompts/12_chat_panel.md
├── prompts/13_cursor_overlay.md
├── prompts/14_invite_flow.md
├── prompts/15_session_card.md
└── prompts/16_config_page.md

PHASE 4 — Wiring
├── prompts/17_routing_guards.md
├── prompts/18_integration_guide.md
└── prompts/19_tests.md

REFERENCE (always available)
├── specs/stack_context.md        ← Paste this at start of every session
├── specs/api_reference.md        ← Backend endpoints + SignalR events
├── specs/design_tokens.md        ← Colors, typography, animations
└── reference/collab_prototype.html ← Interactive UI reference
```

---

## Recommended Claude Code Session Workflow (GB4.7MFE)

```
1. Open new Claude Code session inside gb4.7mfe workspace
2. "Read @features/gbcollabspace/prompts/stack_context.md"   ← GB4.7MFE-specific context
3. "Now implement @features/gbcollabspace/prompts/01_project_setup.md"
4. Review output, fix any issues
5. Commit to git
6. Start next prompt
```

> stack_context.md has been updated to reflect GB4.7MFE conventions (folder structure,
> GbConsoleService, Transloco i18n, auth pattern, path aliases). Always use this version —
> it overrides all generic conventions in the original prompt files.

---

## Parallel Dev Team Setup

| Developer | Prompts |
|-----------|---------|
| Dev 1 | 01 → 02 → 03 → 04 (Foundation) |
| Dev 2 | 05 → 06 → 07 (Services, after Dev 1 done) |
| Dev 3 | 08, 09, 10 (Components A) |
| Dev 4 | 11, 12, 13 (Components B) |
| Dev 5 | 14, 15, 16 (Components C) |
| Any | 17, 18, 19 (After all above) |