document-data-flowlisted

# Document Data Flow Create or update `docs/pages/data-flow.md` — a reference document tracing how data moves between the major components of the project. ## Context - Repo root: !`git rev-parse --show-toplevel 2>/dev/null || pwd` ## Working directory All paths in this skill (`docs/pages/data-flow.md`, any existing architecture docs you Read first) are relative to **Repo root** from Context. The cwd may be a subdirectory — prefix every Read/Edit/Write/Grep/Glob call with the Repo root value. Bare paths are cwd-relative and will silently create/read files in the wrong place. ## When to run - After adding a new data pipeline or processing stage - After changing message protocols or communication patterns between components - After modifying serialization boundaries, API contracts, or adding new message types - After introducing a new architectural layer or external integration ## Workflow ### Step 1: Discover the project architecture Explore the codebase to identify: - The major components or layers (e.g. API server, worker, database client, frontend, CLI) - How components communicate (HTTP, WebSocket, message queue, function calls, IPC, events) - Shared types, schemas, or interface definitions - Entry points and data sources (user input, external APIs, scheduled jobs, file uploads) - Key modules, their responsibilities, and which files implement each component Use `Glob` and `Grep` to locate configuration files, route definitions, message handlers, type definitions,