david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Enhance technical verification processes and documentation for improved accuracy in engineering advice

Browse Source
This commit is contained in:
David Delagneau
2026-04-17 11:45:37 -06:00
parent 30b6ad5827
commit 9b019953f7
14 changed files with 137 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
AGENTS.md
View File

@@ -24,6 +24,7 @@ The detailed operating rules live in:
- `vault/03-context/systems/index.md`
- `vault/03-context/workstreams/index.md`
- `vault/03-context/process/communication.md`
- `vault/03-context/process/technical-verification.md`
- `vault/03-context/process/ai-to-ai-prompting.md`
- `vault/03-context/process/workspace-model.md`
- `vault/03-context/process/memory-promotion-rules.md`
@@ -73,8 +74,11 @@ These are also loaded through `opencode.json`.
- Keep changes concise and auditable.
- When the topic is architectural or historical, prefer updating the relevant file under `vault/03-context/systems/`, `vault/03-context/workstreams/`, or `vault/03-context/process/` instead of overloading `vault/03-context/project.md`.
- When the user asks Swift, SwiftUI, iOS architecture, testing, or debugging questions, use `vault/03-context/ios/` and the local OpenCode iOS skills before answering.
- When the user asks about programming concepts, dependency tooling, package managers, CI/build tooling, testing frameworks, or practices that may be outdated or opinion-sensitive, verify against primary/current documentation before making strong claims.
- For CocoaPods, podspecs, private specs repos, trunk/CDN behavior, Swift Package Manager, Xcode, Swift, Apple frameworks, and similar project-linked tooling, do not rely only on memory.
- When the user asks for a prompt for another AI, GitHub Copilot, or the Fidelity development machine, use `vault/03-context/process/ai-to-ai-prompting.md` and generate a self-contained prompt.
- If a Swift/iOS recommendation depends on current Apple APIs, Xcode behavior, or framework migration guidance, verify against official Apple or Swift documentation before making strong claims.
- Be aware that this is an agentic workspace. If a recurring gap appears in answers, propose and when appropriate apply a workspace improvement to commands, agents, skills, prompts, or process notes.
## Communication