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.
42 lines
1.4 KiB
Markdown
42 lines
1.4 KiB
Markdown
# Fidelity AI Workspace Rules
|
|
|
|
This repository is a companion workspace for Fidelity iOS work, not the product codebase.
|
|
|
|
OpenCode should treat this project as a persistent context layer used to:
|
|
|
|
- keep current project state accurate
|
|
- capture durable information from daily work
|
|
- draft standups and Mattermost messages
|
|
- improve communication for Jeff in natural US English
|
|
|
|
## Always-Loaded Context
|
|
|
|
The detailed operating rules live in:
|
|
|
|
- `ai/AGENTS.md`
|
|
- `ai/context/project.md`
|
|
- `ai/context/people/jeff.md`
|
|
- `ai/state/current.md`
|
|
- `knowledge/workspace-model.md`
|
|
- `knowledge/communication-rules.md`
|
|
|
|
These are also loaded through `opencode.json`.
|
|
|
|
## Required Behavior
|
|
|
|
- Assume the workspace may contain stale context until checked.
|
|
- Before answering questions that depend on current work state, inspect `ai/state/current.md` and the latest relevant log under `ai/logs/`.
|
|
- If the user provides durable new facts, update the appropriate context files instead of leaving the new information only in chat history.
|
|
- If a previous context file is now stale or inaccurate, update that file directly.
|
|
- Prefer correcting canonical context over appending contradictory notes.
|
|
- Keep changes concise and auditable.
|
|
|
|
## Communication
|
|
|
|
When drafting or polishing messages:
|
|
|
|
- use Context, Observation, Action when appropriate
|
|
- clarify auth state when relevant
|
|
- separate external reports from regressions
|
|
- preserve technical meaning while improving English
|