david.delagneau
e92c07b8b1
- Introduced a primary agent for the Fidelity AI Workspace to maintain context and support daily engineering tasks. - Created commands for loading workspace context, drafting updates for Jeff, and logging daily notes. - Implemented translation and standup generation commands to enhance communication clarity. - Developed a compaction plugin to preserve essential workspace context during sessions. - Established a structured approach for managing project knowledge, communication rules, and decision-making processes. - Updated README and project structure to reflect new workflows and usage guidelines.
Fidelity AI Workspace
AI-native companion workspace for daily iOS engineering on Fidelity.
This repository is not the product codebase. It is the operational context layer used from this machine to keep project state current, capture communication from Mattermost, prepare standups, and draft clear updates for Jeff in polished US English.
Purpose
- Keep Fidelity context current outside the main development machine
- Turn fragmented daily work into reusable AI-ready context
- Support standups, manager updates, Jira notes, and debugging summaries
- Improve communication quality without losing technical accuracy
Operating Model
You work on Fidelity from a different machine.
This workspace is used to:
- record what happened during implementation and debugging
- sync relevant communication from Mattermost
- preserve current project context between sessions
- draft messages for Jeff with the right tone and scope
- translate rough notes into concise native-sounding English
Core principle:
Context must be updated before asking AI to write.
Project Scope
Fidelity iOS ecosystem:
- Fid4
- XFlowSDK
- FTFrameworks
- REST migration replacing GraphQL over time
- Discourse and AO issues that require careful classification
Structure
/ai
Runtime context for AI support.
AGENTS.md-> behavior rules for AI agentscontext/-> stable knowledge about Fidelity and team communicationstate/-> current focus, active issues, and communication needslogs/-> daily work record
/prompts
Reusable prompts for:
- standups
- Mattermost updates
- manager communication
- issue clarification
/workflows
Repeatable working guides for:
- daily context sync
- flow debugging
- external issue analysis
/knowledge
Reference material for:
- XFlow behavior
- communication rules
- Fidelity-specific debugging heuristics
/scripts
Helpers for future automation around context generation and communication drafting.
Daily Usage
Start of day
Read:
ai/state/current.mdai/context/project.mdai/context/people/jeff.md- latest file under
ai/logs/
During the day
Capture:
- implementation progress from the main development machine
- Mattermost conversations that change scope or priorities
- debugging findings
- open questions, blockers, and follow-ups
Write updates in:
ai/logs/YYYY-MM-DD.md
Before sending a message
Confirm:
- context
- current observation
- requested or implied action
- whether the issue is external behavior or regression
- whether the flow is authenticated or non-authenticated
End of day
Update:
- today log
- current state
- next communication needs for Jeff
Expected Output
This workspace should help produce:
- high-signal standups
- clearer Mattermost updates
- concise supervisor communication
- better issue framing
- more reliable AI-generated English
OpenCode Entry Point
This workspace is designed to work well with the OpenCode VS Code extension.
Recommended usage:
- Open this repository as its own VS Code workspace.
- Start OpenCode from the integrated terminal at the repository root.
- Begin each session with
/fidelity-context. - As new information appears during the day, update context before asking for drafting help.
Project commands live under .opencode/commands/ and are intended to:
- load the baseline Fidelity context
- draft standups
- draft Jeff updates
- convert rough notes into daily log updates
This keeps AI output tied to the latest workspace state instead of relying on chat memory alone.