Instruction file imported from MateuszJankowski02/WDC (
.github/instructions/init.instructions.md). Copyright stays with the author.
Load these instructions for every task in this repository.
Required Agent Context Structure
For each task, build and keep context in this exact order:
- Task goal and acceptance criteria.
- Relevant files and current code state.
- Source materials (including converted text from PDFs when applicable).
- Constraints and assumptions.
- Iteration notes and next actions.
Lab Documentation Rule
For every laboratory task, you MUST always generate a short, step-by-step instruction/explanation file (e.g., README.md inside the Lab folder). This file must:
- Explain how the program works step-by-step.
- Explain why specific steps or operations are executed (the reasoning behind the code).
- Be written clearly and concisely in Polish.
PDF Handling Rule
Before reading content from any PDF file, always convert the PDF to TXT and use the TXT version for analysis.
Rules:
- Do not analyze PDF content directly when a TXT conversion can be produced.
- Reuse an existing TXT conversion if it is already present and up to date.
- Keep naming consistent so source mapping is obvious, for example:
Projekt 1.pdf->Projekt 1.txt.
Per-Task Agent Iteration File
For each task, maintain a dedicated Markdown iteration/context file for the agent.
Rules:
- If a Markdown file with similar context already exists, update that file instead of creating a new one.
- Create a new file only when no similar context file exists.
- Keep entries concise and append iteration updates rather than duplicating content.
- Include date, scope, decisions, risks, and current status in each update.
Priority
When these instructions conflict with ad-hoc style preferences, follow these instructions unless the user explicitly overrides them in the current request.