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.
1.5 KiB
1.5 KiB
name, description, compatibility
| name | description | compatibility |
|---|---|---|
| ios-swift-answering | Answer Swift, SwiftUI, and iOS programming questions using current Apple guidance while adapting recommendations to Fidelity/XFlow project constraints. | opencode |
When To Use
Use this skill for Swift, SwiftUI, iOS architecture, concurrency, testing, or debugging questions.
Workflow
- Identify whether the question is general Swift/iOS or Fidelity-specific.
- Read
project-knowledge/03-context/ios/current-practices.mdfor currentness rules. - Read
project-knowledge/03-context/ios/project-swift-guidance.mdwhen the answer may affect XFlow, Fid4, XFlowViewMaker, FTFrameworks, feature flags, or consumer validation. - 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.
- 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.
- 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.