/portal:research

[Describe your mod concept]

/portal:research

Concept: A racing game with lap tracking and position display

Features:
- Checkpoint detection
- Lap counting
- Vehicle spawning
- Position leaderboard

Constraints:
- No weapons
- Single vehicle type only

# Pattern Research: [Concept Name]

## Summary
[Brief overview of recommended approach]

## Recommended Patterns

### 1. [Pattern Name]
**Path**: `patterns/[category]/[file].md`
**Relevance**: [Why this pattern applies]

**Key Functions**:
| Function | Purpose |
|----------|---------|
| mod.FunctionName() | [description] |

**Code Snippet**:
```typescript
// Source: patterns/[category]/[file].md
[20-50 lines]

---

## Agent Spawn Configuration

```yaml
agent: portal-researcher
definition: agents/portal-researcher.md
subagent_type: portal-researcher

input:
  - Mod concept description
  - Optional: specific features
  - Optional: constraints

output:
  - Pattern summary with snippets
  - NO full pattern files
  - NO SDK definitions

context_impact: low-moderate
  - Returns ~200-500 lines
  - Only snippets, not full files

You are the Portal Researcher Agent. Your instructions are in:
Battlefield Portal SDK/agents/portal-researcher.md

Read your instructions, then research patterns for the following concept:

---
[USER PROVIDED CONCEPT]

Features (if specified):
[FEATURES LIST]

Constraints (if specified):
[CONSTRAINTS LIST]
---

Return ONLY the research summary as specified in your instructions.
Do NOT include full pattern files or SDK definitions.
Maximum 5 patterns, 20-50 line snippets each.

/portal:research

Concept: Lap-based racing where players drive through checkpoints
Features: lap counting, position tracking, finish detection
Constraints: no weapons

# Pattern Research: Racing Mod

## Summary
A racing mod built on checkpoint detection, vehicle spawning, and input restrictions.

## Recommended Patterns

### 1. Checkpoints (`gameplay/checkpoints.md`)
**Relevance**: Core lap tracking logic with distance-based detection
...

### 2. Vehicles (`gameplay/vehicles.md`)
**Relevance**: Vehicle spawning and player seating
...

### 3. Input Control (`player/input-control.md`)
**Relevance**: Disable weapons during race
...

## Implementation Order
1. Game Lifecycle - Initialize checkpoint positions
2. Vehicles - Spawn vehicles on player deploy
3. Input Control - Disable weapons
4. Checkpoints - Core race loop

## Gaps
- Position tracking requires custom sorting logic

## Builder Input
- patterns/core/game-lifecycle.md
- patterns/gameplay/checkpoints.md
- patterns/gameplay/vehicles.md
- patterns/player/input-control.md

/portal:research

Concept: Team deathmatch with cash rewards and weapon purchases

Features:
- Kill rewards
- Buy menu between rounds
- Weapon upgrades

Constraints:
- No vehicles
- 5v5 only

# Pattern Research: Economy Deathmatch

## Summary
A round-based TDM with cash tracking from economy pattern and round transitions for buy phases.

## Recommended Patterns

### 1. Economy (`gameplay/economy.md`)
...

### 2. Rounds (`gameplay/rounds.md`)
...

### 3. Equipment (`player/equipment.md`)
...

### 4. Scoring (`gameplay/scoring.md`)
...

## Implementation Order
1. State Management - Cash tracking per player
2. Scoring - Kill detection and rewards
3. Rounds - Buy phase transitions
4. Equipment - Weapon purchase logic

## Gaps
- Buy menu UI requires custom widgets implementation

## Builder Input
- patterns/core/state-management.md
- patterns/gameplay/economy.md
- patterns/gameplay/rounds.md
- patterns/gameplay/scoring.md
- patterns/player/equipment.md