david.delagneau
1ad707373a
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
2.3 KiB
2.3 KiB
name, description, trigger, glob
| name | description | trigger | glob |
|---|---|---|---|
| copilot-prompt-engineering | 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. | always_on |
When To Use
Use this skill when the user wants a prompt for another AI assistant, GitHub Copilot, or the Fidelity development machine.
Workflow
- Identify the target task type:
- investigation
- implementation plan
- code change
- review
- test strategy
- story/PR drafting
- Pull only the relevant context:
workspaces/fidelity/project-knowledge/02-work-items/for ticket-specific contextworkspaces/fidelity/project-knowledge/03-context/systems/for component contextworkspaces/fidelity/project-knowledge/03-context/workstreams/for recurring constraintsworkspaces/fidelity/project-knowledge/03-context/ios/for Swift/iOS guidance
- Make the prompt self-contained.
- Tell the target AI what to inspect before acting.
- State constraints, non-goals, and validation expectations.
Fidelity Prompting Rules
- Write the final prompt in English unless the user explicitly requests another language.
- Default to first-person wording so the user can paste the prompt directly into Copilot.
- Keep the prompt short unless the user asks for more detail.
- For follow-up prompts in the same AI session, assume recent shared context and avoid repeating which side made the previous changes unless it matters for the task.
- Include Jira ID and approved title when available.
- For REST work, say REST is behind a feature flag and GraphQL is fallback unless confirmed otherwise.
- For XFlow work, say behavior may depend on entry point, auth state, backend config, and consumer integration.
- For AO/Discourse issues, say external report vs regression must be separated.
- For SwiftUI/XFlow work, mention lifecycle, modal presentation, UIKit bridge, feature flag, and Fid4 validation if relevant.
Output Rules
- Return only the prompt unless the user asks for explanation.
- Keep the prompt concise but complete.
- Prefer sections over paragraphs.
- Do not invent file paths unless the workspace context explicitly names them.
- If exact files are unknown, ask Copilot to locate them first.