feat: Add iOS and Swift context files and guidelines for answering programming questions
This commit is contained in:
@@ -16,6 +16,9 @@ The detailed operating rules live in:
|
||||
- `ai/AGENTS.md`
|
||||
- `ai/context/index.md`
|
||||
- `ai/context/project.md`
|
||||
- `ai/context/ios/index.md`
|
||||
- `ai/context/ios/current-practices.md`
|
||||
- `ai/context/ios/project-swift-guidance.md`
|
||||
- `ai/context/systems/index.md`
|
||||
- `ai/context/workstreams/index.md`
|
||||
- `ai/context/process/communication.md`
|
||||
@@ -53,6 +56,8 @@ These are also loaded through `opencode.json`.
|
||||
- Prefer correcting canonical context over appending contradictory notes.
|
||||
- Keep changes concise and auditable.
|
||||
- When the topic is architectural or historical, prefer updating the relevant file under `ai/context/systems/`, `ai/context/workstreams/`, or `ai/context/process/` instead of overloading `ai/context/project.md`.
|
||||
- When the user asks Swift, SwiftUI, iOS architecture, testing, or debugging questions, use `ai/context/ios/` and the local OpenCode iOS skills before answering.
|
||||
- If a Swift/iOS recommendation depends on current Apple APIs, Xcode behavior, or framework migration guidance, verify against official Apple or Swift documentation before making strong claims.
|
||||
|
||||
## Communication
|
||||
|
||||
|
||||
Reference in New Issue
Block a user