david.delagneau
374991a568
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md - Updated opencode.json to remove references to deleted files. - Revised profile.md to clarify the status of legacy paths and communication evidence. - Adjusted prompts to reflect new file paths and improve clarity. - Enhanced daily logs with focus, work-items, and blockers properties. - Updated work-item notes to include systems, workstreams, people, and related properties. - Improved context maintenance guidelines to ensure accurate and durable project knowledge. - Refined base filters to exclude template files and ensure only relevant notes are displayed. - Updated daily templates to ensure proper formatting and consistency. - Modified workflows to align with the new vault structure and improve context synchronization.
1.1 KiB
1.1 KiB
description
| 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:
@vault/03-context/ios/index.md @vault/03-context/ios/current-practices.md @vault/03-context/ios/project-swift-guidance.md @vault/03-context/project.md @vault/03-context/systems/index.md @vault/03-context/workstreams/index.md @vault/01-current/work-items.md
User question:
$ARGUMENTS
Instructions:
- Use the
ios-swift-answeringskill if available. - Use
swiftui-xflow-reviewif the question touches SwiftUI, XFlow, UIKit bridge removal, modal presentation, lifecycle, or backend-driven UI. - Use
ios-testing-strategyif the question touches tests or validation. - If current Apple API behavior matters, verify against official Apple or Swift 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:
- Recommendation
- Project-specific caveats
- Validation or follow-up checks