Specify boundaries and observable outcomes

Describe the intended behavior, trigger, and expected result, then list the directories this task may change. Record the branch, existing workspace changes, and files owned by concurrent work so the assistant can preserve them. For a cross-service issue, trace the shortest path from the entry point to storage rather than uploading the entire repository by default.

Include applicable repository rules such as package management, authorization for data writes, and public error sanitization. Mark uncertain facts for verification instead of filling gaps with an outdated architecture narrative. Credentials, production configuration, and real user data do not belong in the packet.

Select materials by dependency and retain provenance

Start with the entry file, directly called interfaces, relevant types, and associated tests. Add configuration templates only where needed. Paths and versions are more useful than anonymous pasted code. For long files, include the relevant function alongside its signature, inputs, outputs, and error behavior so a snippet does not misrepresent the implementation.

Supply a reproducible, non-sensitive fixture and explicit acceptance commands. Separate installation, build, and test requirements, noting which actions use external services or incur charges. Record missing dependencies and unavailable environments honestly. A check that was not run must not appear as a passing result.

Expand context in response to evidence

Ask the assistant to identify missing materials, then provide them along specific dependencies. Keep the original boundary visible so investigation does not turn into unrelated refactoring. If the issue crosses additional directories, record the reason and revised scope before deciding how to stage the implementation.

Review the final diff against the initial acceptance criteria and verify the assumptions supplied in the packet. Save useful guidance in the appropriate repository location and remove confirmed disposable copies. More context is not automatically better; check actual input usage and the selected configuration’s current limits separately.

Sources & further reading

An owned publication maintained by NexoToken. Product references reflect the publisher’s commercial interest and are not independent certification.