Vibe Work's built-in plugin: how the agent uses the app's session tools.
Read for web pages, forms, app clicks, searches or your running app in Vibe Work's browser.
Read this before you build or restyle a page to look like an existing site or app (capture its design system first and build from the tokens), when you need a page's structure, logo, images or fonts as files, a whole page saved as Markdown, text, HTML or a full-page picture, or a before and after comparison of your own change.
Use to inspect, clean, analyse or chart data in CSV, TSV, Excel (.xlsx) or JSON files - findings, tables and charts written up as a handbook report page - when the user asks to analyse data, find trends, compare numbers or make charts.
Use for thorough research on a question, a market, a technology or a landscape - when the user asks to research, investigate, compare options or write a cited brief or report from many sources.
Read this before you commit, push, open a pull request, fetch, pull, merge, rebase or reset in Vibe Work, when checks or a review on a pull request need fixing, before you say a change is done, or when a git command answered "Not run". It says which git steps are yours and which are the user's buttons.
Read this first for any coding, feature, fix, research or other task with more than one step (such work starts with a plan page that you keep current), and before you write or change a plan, decision, request, research note, report, roadmap, changelog, guide or prototype, or when the user asks for a handbook, a mockup, or a page where they pick, tick, rank or answer. Vibe Work shows the project handbook (docs/handbook/) next to the chat.
Read this before you make or change an image (a picture, an illustration, an icon, a mockup image or a diagram-like visual) with Vibe Work's image_generate tool, or when the user asks to draw, generate or edit an image.
Read this when the user asks about their own documents, files they uploaded, their knowledge base or libraries, or when an answer may be in documents the user keeps in Vibe Work's Libraries.
Use to prepare for a meeting or call - a one-page brief on the goal, the people, the history, open items, an agenda and the questions to ask - when the user mentions an upcoming meeting, a calendar item or asks to prep for a call.
Read this to show, check or debug this session's web app in Vibe Work's Browser tab (start its server, take a screenshot, read console errors).
Read this before starting, reusing, stopping or restarting a server, watcher or long-running command in Vibe Work, or when a port is busy. It gives the exact tool calls.
Read this when a command needs an API key, token or password (a deploy, an API call, a CLI login), or when a web page shows a new key the user wants to keep.