Fix: Repository URL in README and package.json
This commit is contained in:
@@ -0,0 +1,29 @@
|
||||
# Development Log: Progressive Answer Format
|
||||
|
||||
## Purpose
|
||||
Reduce reading burden for long answers by putting the main point before detailed explanation.
|
||||
|
||||
## User Intent
|
||||
The user likes the content quality but feels rushed or overwhelmed when the answer starts with a long detailed explanation. They want the answer to first provide a simple conclusion, then a short summary, then the detailed answer.
|
||||
|
||||
## Implementation Summary
|
||||
- Added progressive disclosure guidance to the base system prompt.
|
||||
- Updated Chronicle Guard prompt order so idea, planning, architecture, and feature answers start with:
|
||||
1. Short conclusion
|
||||
2. Brief summary
|
||||
3. Detailed answer
|
||||
- Kept the rule scoped to substantial answers so tiny replies do not become overly structured.
|
||||
- Added tests to lock the Guard prompt structure.
|
||||
|
||||
## Changed Files
|
||||
- `src/utils.ts`
|
||||
- `src/features/projectChronicle/guardPrompt.ts`
|
||||
- `tests/projectChronicleGuardPrompt.test.ts`
|
||||
|
||||
## Verification
|
||||
- `./node_modules/.bin/tsc --noEmit`
|
||||
- `npm run compile`
|
||||
- `./node_modules/.bin/jest --runInBand`
|
||||
|
||||
## Result
|
||||
Long answers should now be easier to enter: the user can understand the answer from the top section, then read details only if needed.
|
||||
Reference in New Issue
Block a user