trilium/apps/web-clipper-manifestv3/reference/context-aware_prompting_templates.md
Octech2722 1f444ebc69 docs: add comprehensive development workflow documentation
Copilot Integration:
- Streamlined instructions (70% shorter than original)
- Task templates for common operations
- Three-tier usage strategy (free/strategic/manual)
- Optimized for GitHub Copilot Basic tier limits

Development Resources:
- Common task workflows with time estimates
- Feature parity checklist with priorities
- Debugging and troubleshooting guides
- Testing scenarios and checklists
- Code quality standards

Workflow Optimization:
- Efficient Copilot task budgeting
- Real-world implementation examples
- Performance and success metrics
- Project completion roadmap

Reduces repetitive context in prompts.
Maximizes limited Copilot task budget.
2025-10-18 12:21:13 -05:00

24 lines
655 B
Markdown

## For Feature Implementation:
Implement [FEATURE_NAME] from FEATURE-PARITY-CHECKLIST.md.
Legacy reference: apps/web-clipper/[FILE]:[LINES]
Target files: src/[FILES]
Use centralized logging and theme system. Update checklist when done.
## For Bug Fixes:
Fix [ISSUE] in src/[FILE].
Expected behavior: [DESCRIBE]
Current behavior: [DESCRIBE]
Error logs: [IF ANY]
## For Code Understanding:
Explain the [FEATURE] implementation in apps/web-clipper/[FILE].
I need to replicate this in MV3. What's the core logic and data flow?
## For Architecture Questions:
[QUESTION ABOUT SYSTEM DESIGN]
See docs/ARCHITECTURE.md for context on logging/theme systems.