david.delagneau
374991a568
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md - Updated opencode.json to remove references to deleted files. - Revised profile.md to clarify the status of legacy paths and communication evidence. - Adjusted prompts to reflect new file paths and improve clarity. - Enhanced daily logs with focus, work-items, and blockers properties. - Updated work-item notes to include systems, workstreams, people, and related properties. - Improved context maintenance guidelines to ensure accurate and durable project knowledge. - Refined base filters to exclude template files and ensure only relevant notes are displayed. - Updated daily templates to ensure proper formatting and consistency. - Modified workflows to align with the new vault structure and improve context synchronization.
1.7 KiB
1.7 KiB
name, description, compatibility
| name | description | compatibility |
|---|---|---|
| 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. | opencode |
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:
vault/02-work-items/for ticket-specific contextvault/03-context/systems/for component contextvault/03-context/workstreams/for recurring constraintsvault/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
- 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.