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

3
.opencode/skills/ios-swift-answering/SKILL.md
View File

@@ -13,7 +13,7 @@ Use this skill for Swift, SwiftUI, iOS architecture, concurrency, testing, or de
1. Identify whether the question is general Swift/iOS or Fidelity-specific.
2. Read `vault/03-context/ios/current-practices.md` for currentness rules.
3. Read `vault/03-context/ios/project-swift-guidance.md` when the answer may affect XFlow, Fid4, XFlowViewMaker, FTFrameworks, feature flags, or consumer validation.
4. If the answer depends on current Apple APIs, Xcode versions, or migration guidance, verify with official Apple/Swift documentation before making strong claims.
4. If the answer depends on current Apple APIs, Xcode versions, dependency tooling, package-manager behavior, testing frameworks, or migration guidance, verify with official/primary documentation before making strong claims.
5. Separate:
- current best practice
- project-safe recommendation
@@ -24,4 +24,5 @@ Use this skill for Swift, SwiftUI, iOS architecture, concurrency, testing, or de
- Be direct and senior-engineer practical.
- Avoid generic architecture advice when project constraints matter.
- Do not assume deployment target, Xcode version, or framework migration status.
- Do not characterize CocoaPods, SPM, podspec repos, trunk/CDN behavior, CI/build behavior, or testing framework practices as good or bad practice without corroborating current primary docs when the recommendation matters.
- Mention tradeoffs and validation path when relevant.