feat: Enhance AI prompting capabilities with new guidelines and templates for GitHub Copilot

.opencode/commands/copilot-prompt.md

@@ -0,0 +1,41 @@
+---
+description: Generate a high-quality prompt for GitHub Copilot on the Fidelity development machine
+---
+
+Generate a prompt that the user can send to GitHub Copilot or another AI assistant on the Fidelity development machine.
+
+Read:
+
+@prompts/copilot-prompt.md
+@ai/AGENTS.md
+@ai/context/process/ai-to-ai-prompting.md
+@ai/context/index.md
+@ai/context/project.md
+@ai/context/ios/index.md
+@ai/context/ios/project-swift-guidance.md
+@ai/context/systems/index.md
+@ai/context/workstreams/index.md
+@ai/work-items/index.md
+@ai/state/current.md
+@ai/state/work-items.md
+
+Detailed active work item files, if available:
+
+!`if [ -d ai/work-items ]; then for f in ai/work-items/*.md; do case "$f" in *README.md|*index.md) continue;; esac; echo "\n### $f"; cat "$f"; done; else echo "No work item files available."; fi`
+
+User request:
+
+$ARGUMENTS
+
+Instructions:
+
+- Use the `copilot-prompt-engineering` skill if available.
+- Generate a self-contained prompt for the target AI.
+- Include only context relevant to the request.
+- Include Jira ID/title when the task maps to an active work item.
+- Tell Copilot what to inspect before making assumptions.
+- Include constraints, non-goals, expected output, and validation.
+- If the user asks for implementation help but the write scope is unclear, generate an investigation/plan prompt rather than a code-change prompt.
+- Do not mention this workspace unless explaining that the target AI will not have access to it.
+
+Return only the final prompt unless the user explicitly asks for commentary.