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.
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
---
|
|
name: ios-swift-answering
|
|
description: Answer Swift, SwiftUI, and iOS programming questions using current Apple guidance while adapting recommendations to Fidelity/XFlow project constraints.
|
|
compatibility: opencode
|
|
---
|
|
|
|
## When To Use
|
|
|
|
Use this skill for Swift, SwiftUI, iOS architecture, concurrency, testing, or debugging questions.
|
|
|
|
## Workflow
|
|
|
|
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.
|
|
5. Separate:
|
|
- current best practice
|
|
- project-safe recommendation
|
|
- assumptions to confirm
|
|
|
|
## Output Rules
|
|
|
|
- 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.
|
|
- Mention tradeoffs and validation path when relevant.
|