Notes are the project's attention board: reminders, preferences, undeveloped ideas, and explicitly requested checklists. Keep each note focused on something still worth seeing.
#Add and edit a note
- Open Sticky Notes from the project tool palette.
- Use New note.
- Write a short title on the first line.
- Add only the context needed for future action.
- Choose an optional color and finish editing.
- Check the board after saving.
A useful note is “Review the mobile empty state” with the relevant context. A long transcript or command log is difficult to act on and belongs elsewhere.
The editor supports common formatting such as bold, italic, strikethrough, and code. Use color to group notes in a way that helps you scan the board.
#Use a checklist
Switch to the native checklist control when you need items that can be checked independently. Keep each item stable and specific: “Check narrow search layout” is easier to verify than “Polish UI.”
Check items as they are completed. If another person or agent edits the checklist, reopen the latest note before changing its items.
Ask the assistant explicitly when you want a working checklist. It should update that checklist rather than create several competing progress boards.
#Close completed attention items
Close a note when what it asks for is done. Closing removes it from the active board while preserving a recoverable record. Use Reopen on a closed note if it needs attention again. This is different from replacing the text with a completion report.
The human Notes browser can offer Delete permanently for a closed note with a separate confirmation. Choose that only when you intend permanent deletion. Assistant note-closing tools do not silently turn completion into permanent deletion.
For a confirmed open Issue, a short title and Issue link can serve as the reminder. Keep reproduction steps, acceptance criteria, progress, and verification in the Issue, then close the linked note when no action remains.
#Choose a lasting home
Use Issues for actionable bugs or improvements, Project Logs for durable task results, and repository files for project reference material. In a Mate workspace, Knowledge holds maintained reference documents.
Do not keep a note open solely because a completed task was lengthy. The active board works best when it asks for current attention.
If a save fails or a checklist changed elsewhere, reconnect and inspect the current note before retrying. Avoid creating a duplicate to work around a stale edit.