chore: remove compatibility field from various agent rules for consistency
This commit is contained in:
@@ -1,7 +1,6 @@
|
||||
---
|
||||
name: ai-prompt-engineering
|
||||
description: Create self-contained prompts for another AI assistant that lacks access to this workspace memory.
|
||||
compatibility: opencode
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
@@ -25,4 +24,3 @@ Use this skill when the user wants a prompt for another AI assistant, coding age
|
||||
- Prefer clear sections over long prose.
|
||||
- Include work-item ID and title when relevant.
|
||||
- Make assumptions explicit.
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
name: copilot-prompt-engineering
|
||||
description: Create high-quality prompts for GitHub Copilot or another AI running on the Fidelity development machine, using this workspace's context without assuming the target AI has access to it.
|
||||
compatibility: opencode
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
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
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
name: ios-testing-strategy
|
||||
description: Recommend iOS testing approaches for Swift, SwiftUI, XFlow, Fid4, and REST migration work while respecting existing XCTest/Swift Testing/project constraints.
|
||||
compatibility: opencode
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
name: professional-communication
|
||||
description: Rewrite rough technical notes into clear, concise, stakeholder-ready professional English while preserving scope and technical meaning.
|
||||
compatibility: opencode
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
@@ -23,4 +22,3 @@ Use this skill for manager updates, stakeholder messages, translations, issue cl
|
||||
- Write natural professional US English.
|
||||
- Keep messages concise enough for workplace chat unless the user asks for a longer document.
|
||||
- Do not invent facts, evidence, or commitments.
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
name: status-reporting
|
||||
description: Generate work-item-aware standups and status summaries from current workspace memory, recent logs, and communication evidence.
|
||||
compatibility: opencode
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
@@ -24,4 +23,3 @@ Use this skill for standups, daily scrum updates, end-of-day summaries, and shor
|
||||
- Keep the report concise and ready to send.
|
||||
- Do not mention internal evidence sources unless the user asks.
|
||||
- Use `Blockers: None` only when no blocker is visible in current memory.
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
name: swiftui-xflow-review
|
||||
description: Review or reason about SwiftUI code in XFlow/Fidelity contexts, especially lifecycle, modal presentation, navigation, backend-driven UI, and UIKit bridge removal.
|
||||
compatibility: opencode
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
name: workspace-memory-curation
|
||||
description: Maintain file-based operational memory by deciding what to log, promote, correct, or route into tool behavior across reusable AI workspaces.
|
||||
compatibility: opencode
|
||||
trigger: always_on
|
||||
glob: ""
|
||||
---
|
||||
@@ -24,4 +23,3 @@ Use this skill when new information may change workspace memory, project state,
|
||||
- Report updated files and the memory change.
|
||||
- Preserve uncertainty when confidence is mixed.
|
||||
- Do not promote tool failures, sync noise, or generic chat chatter as project facts.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user