A developer must always state the full file path when creating or changing a file. The developer must also list all full paths at the end of a conversation. This helps the user track changes and copy information easily.
By Pawan Nayar · from the LLOS AI Learning record
A developer must always state the full file path when creating or changing a file.
The developer must also list all full paths at the end of a conversation. This helps the user track changes and copy information easily.
When a developer creates or changes a file, the developer must state its full path. The developer must list all full file paths at the end of the conversation. The user needs these paths to copy them to other discussions. For Batch API calls, a developer should always test with a small number first. Then the developer can increase the number. When using asynchronous operations, a developer must use `as_completed(tasks)` for parallel processing. A semaphore does not provide true parallelism. A developer should never write directly to a production file. Write to a temporary file first. Then replace the original file using `os.replace()`. Before writing a script that creates data, a developer must read the script that uses the data. This confirms the data format is correct. The `sleep` command is not allowed. Commands that take longer than 5 seconds must run in the background. Monitoring should only show the last three lines of output. If a session is long, the developer must tell the user. The developer should give the user a prompt to re-read all relevant files. At the end of a session, the developer must update the `MEMORY.md` file. The developer adds all new or changed file paths to the "Key File Paths" section.
A developer modifies a configuration file. The developer states the full path `/app/config/settings.json` in the response. At the end of the work, the developer lists `/app/config/settings.json` with all other changed files. This allows the manager to quickly see all affected files.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
A developer should not create new ways to do things. The existing process works well.
An AI model must state the full path every time it creates or changes a file. The AI model must list all full paths at the end of a conversation.
A central API coordinator manages all requests to external services. This coordinator checks for a kill switch to stop all activity.
A developer must read six foundational documents. These documents ensure a shared understanding of the AI model's grammar.
A developer must always state the full file path when creating or changing a file. The developer must also list all full paths at the end of a conversation. This helps the user track changes and copy information easily.