feat: Add iOS and Swift context files and guidelines for answering programming questions
This commit is contained in:
27
.opencode/skills/ios-swift-answering/SKILL.md
Normal file
27
.opencode/skills/ios-swift-answering/SKILL.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
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 `ai/context/ios/current-practices.md` for currentness rules.
|
||||
3. Read `ai/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.
|
||||
Reference in New Issue
Block a user