On this page
Context and attachments
Add focused files, folders, images, and PDFs so a task starts with useful project context.
Good context is specific enough to explain the task without adding unrelated material. RevampKey can inspect the repository and use files, folders, images, and PDFs that you provide with the task.
Start with the smallest useful selection
Reference the files or folders that define the behavior, tests, and constraints you want considered.
Add an image or PDF when it clarifies the request
Use visual material for a layout, visual state, error, or document that words alone would leave ambiguous. Explain what the task should learn from it.
Check the visible attachment list before sending
You can select files, drag them into the current task, or paste them where the current interface supports that action. Remove unrelated items before continuing.
What each input is good for
| Input | Useful for | What to remember |
|---|---|---|
| Files and folders | Code, tests, configuration, and nearby examples | Choose the smallest set that explains the change. |
| Images | Layouts, visual states, and error references | Up to 5 MB per image; describe the intended result in text. |
| PDFs | Reference documents and exported specifications | Up to 25 MB per PDF; the task list does not provide an image preview. |
A PDF can still be part of the task even when the attachment list does not show an image preview. Include the relevant page or section in your description so the requested outcome remains clear without relying on the preview.
Describe which behavior the files constrain and what the visual or document should help the task understand.
What if an attachment is too large or the list is full?
Remove unrelated items first, then reduce the file size or choose a more focused reference. If the visible error remains unclear, include its wording when you contact support.
Report a documentation problem or contact the RevampKey team.
Continue with Projects and workspaces to choose folders, or read Codebase Structure when the task needs structural context rather than another file attachment.