mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-04 01:40:45 +08:00
b00113d212
- Updated embedding_manager.py to include backend parameter in model configuration. - Modified model_manager.py to utilize cache_name for ONNX models. - Refactored hybrid_search.py to improve embedder initialization based on backend type. - Added backend column to vector_store.py for better model configuration management. - Implemented migration for existing database to include backend information. - Enhanced API settings implementation with comprehensive provider and endpoint management. - Introduced LiteLLM integration guide detailing configuration and usage. - Added examples for LiteLLM usage in TypeScript.
3.1 KiB
3.1 KiB
Write Mode Protocol
Prompt Structure
PURPOSE: [development goal]
TASK: [specific implementation task]
MODE: [auto|write]
CONTEXT: [file patterns]
EXPECTED: [deliverables]
RULES: [templates | additional constraints]
Operation Boundaries
MODE: write
- READ: All CONTEXT files and analyze content
- CREATE: New files (documentation, code, configuration)
- MODIFY: Existing files (update content, refactor code)
- DELETE: Files when explicitly required
Restrictions: Follow project conventions, cannot break existing functionality
Constraint: Must test every change
Execution Flow
MODE: write
- Parse all 6 fields (PURPOSE, TASK, MODE, CONTEXT, EXPECTED, RULES)
- Read CONTEXT files, find 3+ similar patterns
- Plan implementation following RULES
- Execute requested file operations
- Validate changes
- Report file changes
Core Requirements
ALWAYS:
- Study CONTEXT files - find 3+ similar patterns before implementing
- Apply RULES exactly
- Test continuously (auto mode)
- Commit incrementally (auto mode)
- Match project style exactly
- List all created/modified files at output beginning
NEVER:
- Make assumptions without code verification
- Ignore existing patterns
- Skip tests (auto mode)
- Use clever tricks over boring solutions
- Break backward compatibility
- Exceed 3 failed attempts without stopping
Three-Attempt Rule: On 3rd failure, stop and report what attempted, what failed, root cause
| Error Type | Response |
|---|---|
| Syntax/Type | Review → Fix → Re-run tests |
| Runtime | Analyze stack → Add handling → Test |
| Test Failure | Debug → Review setup → Fix |
| Build Failure | Check messages → Fix incrementally |
Output Format
Format Priority
If template defines output format → Follow template format EXACTLY
If template has no format → Use default format below
Task Implementation
# Implementation: [TASK Title]
## Changes
- Created: `path/to/file1.ext` (X lines)
- Modified: `path/to/file2.ext` (+Y/-Z lines)
- Deleted: `path/to/file3.ext`
## Summary
[2-3 sentence overview]
## Key Decisions
1. [Decision] - Rationale and reference to similar pattern
2. [Decision] - path/to/reference:line
## Implementation Details
[Evidence-based description with code references]
## Testing
- Tests written: X new tests
- Tests passing: Y/Z tests
## Validation
✅ Tests: X passing
✅ Build: Success
## Next Steps
[Recommendations if any]
Partial Completion
# Task Status: Partially Completed
## Completed
- [What worked]
- Files: `path/to/completed.ext`
## Blocked
- **Issue**: [What failed]
- **Root Cause**: [Analysis]
- **Attempted**: [Solutions tried - attempt X of 3]
## Required
[What's needed to proceed]
## Recommendation
[Suggested next steps]
Code References
Format: path/to/file:line_number
Example: src/auth/jwt.ts:45 - Implemented following pattern from src/auth/session.ts:78
Quality Checklist
- All tests pass
- Build succeeds
- All EXPECTED deliverables met
- Code follows existing patterns
- File changes listed at beginning