Using Virillio Code
Prompting and context
Give the agent a clear outcome and the material it needs to get there.
On this page
Write a useful request
Explain the outcome, the relevant area, and how you will judge success. Add constraints such as preserving the current design, avoiding new dependencies, or asking before deployment.
The search input loses focus after each keystroke.
Find the cause and fix it without changing the visual design.
Reproduce the bug, add a useful regression check, and explain the result.Mention what you have already tried. Exact error messages are more useful than “it is broken,” but remove secrets and personal data from anything you share.
Add files and attachments
Use @ in the prompt for context suggestions. Use Add images and files to attach supporting material. Choose only what is relevant: a screenshot for a layout problem, an error log for a failure, or the file containing the behavior.
A model’s supported input types vary. If an image or document is rejected, check the selected model’s capabilities rather than assuming every connected model can read it.
Steer the conversation
Follow up with the specific part that needs changing. If a task has become ambiguous, ask the agent to restate the goal before continuing. For a large change, split discovery, planning, implementation, and review into clear checkpoints.
When the agent misses a detail
Point to the relevant file or passage, ask it to inspect the current version, and state what conclusion should be revisited. Starting a fresh session can help separate a new task from a long history, but provide the decisions it needs again.