# Roblox Pre-Action Plan

`PRE_ACTION_COMPLETE: false`

## 1. Task Classification

- Task type:
- Genre:
- Audience:
- Scale:
- Multiplayer assumptions:
- Monetization intent:

## 2. Relevant Roblox Concepts

- Concepts:
- Services:
- Classes:
- Gameplay patterns:

## 3. Reference Sources Consulted

- Canonical Roblox docs:
- Implementation references:
- Dataset/corpus support:

## 4. Canonical Terms To Use

- Term standardization:
- Naming vocabulary:
- Vocabulary source: `docs/reference/canonical-vocabulary.md`

## 5. Risks and Uncertainties

- Unsafe assumptions:
- Required validation:
- Likely pitfalls:

## 6. Proposed Modular File Tree

```text
client/
server/
shared/
systems/
features/
ui/
config/
assets/
tests/
```

## 7. Category Ownership

- Client:
- Server:
- Shared:
- Systems:
- Features:
- UI:
- Config:
- Assets:
- Tests:

## 8. Naming Convention

- Folder naming:
- Module naming:
- Remote/event naming:
- Config naming:

## 9. Implementation Phases

1.
2.
3.

## 10. Validation Checkpoints

- Docs verified:
- Architecture reviewed:
- File tree approved:
- Implementation gate:

`PRE_ACTION_COMPLETE: true` only after all sections are filled.