1.8 KiB
1.8 KiB
description, applyTo
| description | applyTo |
|---|---|
| Instructions for documenting prompts and file changes in docs/prompt.md | docs/prompt.md |
Writing Prompts to docs/prompt.md
Purpose
Document all AI prompts and track which files were modified as a result of each prompt.
Structure Requirements
Date Organization
- Use German date format:
DD.MM.YYYY(e.g.,11.03.2026) - Create a level 2 heading (
##) for each date - Dates should be in chronological order
- If the current date doesn't exist, create a new subheading for it
Prompt Entry Format
Each prompt entry should follow this structure:
- Prompt text: Write the actual prompt as a bullet point while rewriting it so it's nicer to read but still closely resembles the original (
-) - Separator: Add
<br><br>after the prompt text - File changes header: Add the line
Folgende Dateien wurden in diesem Prompt verändert: - File list: List all affected files as indented sub-bullets (4 spaces +
-)- Include file paths relative to the project root
- Add notes in parentheses if relevant (e.g., "neu erstellt", "keine Änderungen")
Example Format
## 11.03.2026
- [Prompt text here]<br><br>
Folgende Dateien wurden in diesem Prompt verändert:
- path/to/file1.ts
- path/to/file2.dart (neu erstellt)
- path/to/file3.ts (keine Änderungen, bereits vorhanden)
Guidelines
- Always add new prompts under the correct date heading
- Always include the affected files list, even if no files were changed
- Use relative file paths from the project root
- Be specific about what changed (created, modified, deleted)
- Keep the prompt text concise but descriptive
- Maintain chronological order within each date section
File Location
All prompt documentation goes into: docs/prompt.md