Files
mission-control/AGENTS.md
teernisse df26eab361 docs: add AGENTS.md and progress screenshots for agent swarm coordination
Adds documentation for agent coordination when working on Mission Control.
Screenshots capture the UI state at key development milestones.

AGENTS.md includes:
- Project overview and core principle (THE ONE THING)
- Architecture diagram showing IPC flow and CLI integration
- Key file reference table
- Agent coordination: team name, beads workflow, communication
- Current development status (Phase 0-1 complete, Phase 2 in progress)
- Development commands for running tests and dev servers
- Visual verification instructions using Playwright MCP
- Critical constraints: CLI over libraries, trait-based mocking, TDD, no any

Screenshots:
- mission-control-current.png: Current app state
- mission-control-focus-view.png: Focus view with THE ONE THING
- mission-control-phase1-complete.png: Phase 1 milestone capture

These files help multiple agents coordinate on the project and understand
the current implementation state.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-26 09:55:10 -05:00

113 lines
2.9 KiB
Markdown

# AGENTS.md - Mission Control Agent Swarm
## Project Overview
Mission Control is an ADHD-centric personal productivity hub built with Tauri 2.0 + React 19. It unifies GitLab activity (via `lore` CLI) and beads task tracking (via `br` CLI) into a single native interface.
**Core principle:** Surface THE ONE THING you should be doing right now.
## Architecture
```
Frontend (React 19 + Vite) Backend (Tauri/Rust)
| |
|---- IPC (invoke) ----------->|
| |
| CLI Traits (mockable)
| |
| lore --robot (GitLab)
| br (beads tasks)
| bv --robot-* (triage)
```
## Key Files
| Path | Purpose |
|------|---------|
| `src/App.tsx` | Main React component |
| `src-tauri/src/lib.rs` | Tauri app setup |
| `src-tauri/src/data/lore.rs` | Lore CLI trait + types |
| `src-tauri/src/data/beads.rs` | Beads CLI trait + types |
| `src-tauri/src/commands/mod.rs` | Tauri IPC commands |
| `PLAN.md` | Full implementation plan |
| `CLAUDE.md` | Project-specific Claude instructions |
## Agent Coordination
### Team Name
`purrfect-beaming-lynx`
### Beads Task Management
Use `br` and `bv` for task coordination:
```bash
# Get triage recommendations
bv --robot-triage | jq '.triage.quick_ref.top_picks'
# List all beads
br list --json
# Claim a task
br update <bead-id> --status in_progress
# Complete a task
br close <bead-id> --reason "Completed: <summary>"
# Show bead details
br show <bead-id> --json
```
### Communication
Use SendMessage tool for agent-to-agent coordination:
- Message teammates directly by name
- Use broadcast sparingly (only for critical team-wide issues)
- Check task list after completing each task
### Current Status
**Completed:**
- Phase 0: Test infrastructure (Vitest, Playwright, Rust mocks)
- Phase 1 partial: Tauri scaffold, React shell, CLI traits
**In Progress:**
- Phase 2: Bridge + Data Layer (wiring CLI to Tauri commands)
**Blocked:**
- Phase 3-7: Depend on Phase 2 completion
## Development Commands
```bash
# Run dev (frontend + backend)
npm run tauri:dev
# Frontend only
npm run dev
# Run tests
npm run test # Vitest
npm run test:e2e # Playwright
cargo test # Rust
# Lint
npm run lint
cargo clippy -- -D warnings
```
## Visual Verification
Playwright MCP tools can connect to `http://localhost:1420` for UI inspection:
- `browser_navigate` - Load pages
- `browser_snapshot` - Get accessibility tree
- `browser_take_screenshot` - Visual verification
## Critical Constraints
1. **CLI over libraries** - Shell out to `lore`/`br`/`bv`, don't import them
2. **Trait-based mocking** - All CLI interactions via traits for testability
3. **TDD** - Write failing test first, then implement
4. **No `any`** - Use `unknown` with type guards in TypeScript
5. **jj for VCS** - Use jj, not git (see global CLAUDE.md)