feat: Enhance technical verification processes and documentation for improved accuracy in engineering advice
This commit is contained in:
@@ -9,6 +9,7 @@ Read:
|
||||
@vault/03-context/ios/index.md
|
||||
@vault/03-context/ios/current-practices.md
|
||||
@vault/03-context/ios/project-swift-guidance.md
|
||||
@vault/03-context/process/technical-verification.md
|
||||
@vault/03-context/project.md
|
||||
@vault/03-context/systems/index.md
|
||||
@vault/03-context/workstreams/index.md
|
||||
@@ -23,7 +24,7 @@ Instructions:
|
||||
- Use the `ios-swift-answering` skill if available.
|
||||
- Use `swiftui-xflow-review` if the question touches SwiftUI, XFlow, UIKit bridge removal, modal presentation, lifecycle, or backend-driven UI.
|
||||
- Use `ios-testing-strategy` if the question touches tests or validation.
|
||||
- If current Apple API behavior matters, verify against official Apple or Swift documentation before making strong claims.
|
||||
- If current Apple API, Swift, CocoaPods, SPM, Xcode, CI/build, or testing behavior matters, verify against official/primary documentation before making strong claims.
|
||||
- Contextualize the answer to Fidelity only when it materially changes the recommendation.
|
||||
- Separate current best practice from project-safe recommendation when they differ.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user