19 lines
911 B
Markdown
19 lines
911 B
Markdown
|
# Story: System Prompt & Persona
|
||
|
|
|
||
|
|
## User Story
|
||
|
|
**As a** User
|
||
|
|
**I want** the Agent to behave like a Senior Engineer and know exactly how to use its tools
|
||
|
|
**So that** it writes high-quality code and doesn't hallucinate capabilities or refuse to edit files.
|
||
|
|
|
||
|
|
## Acceptance Criteria
|
||
|
|
* [ ] Backend: Define a robust System Prompt constant (likely in `src-tauri/src/llm/prompts.rs`).
|
||
|
|
* [ ] Content: The prompt should define:
|
||
|
|
* Role: "Senior Software Engineer / Agent".
|
||
|
|
* Tone: Professional, direct, no fluff.
|
||
|
|
* Tool usage instructions: "You have access to the local filesystem. Use `read_file` to inspect context before editing."
|
||
|
|
* Workflow: "When asked to implement a feature, read relevant files first, then write."
|
||
|
|
* [ ] Backend: Inject this system message at the *start* of every `chat` session sent to the Provider.
|
||
|
|
|
||
|
|
## Out of Scope
|
||
|
|
* User-editable system prompts (future story).
|