david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
---
|
|
description: Answer Swift or iOS programming questions with Fidelity/XFlow context
|
|
---
|
|
|
|
Answer the user's Swift/iOS programming question using current iOS practices and this workspace's Fidelity context.
|
|
|
|
Read:
|
|
|
|
@project-knowledge/03-context/ios/index.md
|
|
@project-knowledge/03-context/ios/current-practices.md
|
|
@project-knowledge/03-context/ios/project-swift-guidance.md
|
|
@agent-memory/integrations/technical-verification.md
|
|
@project-knowledge/03-context/project.md
|
|
@project-knowledge/03-context/systems/index.md
|
|
@project-knowledge/03-context/workstreams/index.md
|
|
@project-knowledge/01-current/work-items.md
|
|
|
|
User question:
|
|
|
|
$ARGUMENTS
|
|
|
|
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, 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.
|
|
|
|
Return:
|
|
|
|
1. Recommendation
|
|
2. Project-specific caveats
|
|
3. Validation or follow-up checks
|