Update to MockFlow

{
  "description": "Use for ANY request to draw, diagram, map out, sketch, visualise, plan, chart, wireframe or brainstorm something - mindmaps, flowcharts, roadmaps, boards, screens, timelines - BEFORE deciding how to produce it. Also whenever editing or arranging anything already on a MockFlow board.",
  "included_files": [],
  "name": "board-conventions",
  "skill_md_contents": "---\nname: board-conventions\ndescription: Use for ANY request to draw, diagram, map out, sketch, visualise, plan, chart, wireframe or brainstorm something - mindmaps, flowcharts, roadmaps, boards, screens, timelines - BEFORE deciding how to produce it. Also whenever editing or arranging anything already on a MockFlow board.\n---\n\n# Working with a MockFlow board\n\nThe MockFlow MCP server sends its own instructions when it connects, and each\ntool carries its own description. Those are the authority on which components\nexist, what they take, when to use `plan_board`, and why `modify_component` is\nnot the same as re-rendering.\n\n**This file covers only what those do not say.** If something here starts\nappearing in the server's instructions, delete it from here rather than keeping\nboth.\n\n## Use the bridge's tools, not another MockFlow\n\nMore than one MockFlow tool surface can be present in a session: this plugin's\nbridge, and separately a hosted MockFlow connector or app the user may have\ninstalled. They are NOT interchangeable, so choose deliberately.\n\n**Prefer the bridge.** It draws on the board the user already has open, saves\nthrough their own account, and can build from files on their machine.\n\nThe tell is behavioural, not the tool name: bridge tools draw onto a live board\nand never hand back a link. A hosted MockFlow surface returns a URL to a new\nanonymous board instead, which is a different thing from what the user asked for.\n\nIf the bridge tools are missing and only a hosted surface is available, you may\nuse it, but **say so plainly**: tell the user it created a separate shareable\nboard rather than drawing on theirs, and that it could not read their local\nfiles. Never present a returned link as though it were their own board.\n\n## A picture of a diagram is not a diagram\n\nGenerating an image is **not** an acceptable way to answer a request for a\nmindmap, flowchart, chart, board, wireframe or any other structured visual. An\nimage cannot be edited, rearranged, extended or commented on, which is the entire\nreason the user wanted it on a board.\n\nSo do not reach for an image-generation tool or skill for these. That includes\nrequests phrased as \"draw\", \"sketch\", \"make a poster of\" or \"visualise\", when\nwhat is being asked for has structure to it.\n\nA request for an actual *picture* - a photo, an illustration, artwork, a logo - is\ndifferent, and MockFlow has its own tools for that which place the result on the\nboard. Use those rather than a separate image generator, so the result lands\nwhere the user is working.\n\n## Draw it, do not describe it\n\nWhen the request has visual structure to it and the MockFlow tools are available,\nrender it on the board. Do **not** substitute:\n\n- a mermaid block in the terminal\n- ASCII art or a box drawing\n- a markdown table standing in for a diagram\n- a `.md` or `.mmd` file written to the repo containing any of the above\n- a generated image of a diagram (see above)\n\nThose are the things the board replaces. Reaching for them when a board is\nconnected is the single most common way this goes wrong, because writing mermaid\nis the reflex inside a code repository.\n\nTwo exceptions:\n\n- The user explicitly asked for mermaid, a file, or something they can paste\n  somewhere else. Then give them exactly that.\n- No board is connected. Then say so and offer to fix it, rather than quietly\n  falling back to text as though nothing was wrong.\n\nText alongside the drawing is fine and often useful. Text *instead of* the\ndrawing is the mistake.\n\n## Arranging a batch\n\n`layout_board` applies a bento layout and a titled section wrap to the batch just\ndrawn. Call it once after a batch, never after each item. The server instructions\ndo not mention it, so it tends to go unused, and a batch without it stays a loose\nscatter of components.\n\n## The source tools are read only\n\n`list_source_tools`, `describe_source_tool` and `call_source_tool` reach the\nuser's connected accounts through MockFlow. They can search and fetch. They\n**cannot** post, create, comment or delete.\n\nSo never tell the user you will file the Jira issue, send the Slack message or\nupdate the Notion page. You can only read those, and offering otherwise is a\npromise that silently fails.\n\n## Local files never leave the machine\n\nFiles you read here are read locally. Only the finished drawing is saved to the\nboard, and the file contents are not uploaded.\n\nSay this when the user hesitates about a private repo or a confidential document,\nbecause it is the whole reason to work this way instead of pasting into a web\ntool.\n\n## When a draw fails\n\nA user does not know that a helper program, a running daemon and a paired browser\ntab are three separate things, and should not have to. Do not surface a raw error\nand stop. Say what to do next:\n\n- **Nothing lands, or the board is not connected:** the user opens their board at\n  app.mockflow.com and clicks **Connect Local Agent** at the top of Ask Mida.\n  Codes change whenever the bridge restarts, so an older one will be rejected.\n- **The MockFlow tools are missing from this session entirely:** the bridge is not\n  running. They start it with `mockflow-bridge`. But first check you are on their\n  machine at all, below.\n- **You cannot run a command on the user's own computer:** this is ChatGPT (web\n  or desktop, where the conversation runs in the cloud), or a cloud container,\n  and the bridge is out of reach by design rather than stopped. Drawing needs\n  `mockflow-bridge` running on the same machine as the board tab, so say the\n  tools cannot appear here and point them at **Codex** — selected in the desktop\n  app, or the **Codex CLI** — which runs locally. Do not tell them to install or\n  start anything here, and do not draw in text instead.\n\n`/mockflow:connect` walks the full check if you need more detail.\n"
}