Simplify the developing-with-holoviz workflow instruction

docs/how-to/customize-ai-instructions.md

@@ -10,7 +10,7 @@ Every section can be customised:
 | Section | What it covers |
 | --- | --- |
 | `intro` | The one-line description of what the server does |
-| `workflow` | How `show`, `screenshot`, `edit`, and `evaluate` relate, and that validation is automatic |
+| `workflow` | How `show`, `screenshot`, `edit`, and `evaluate` relate, that validation is automatic, and when to defer to the `developing-with-holoviz` skill |
 | `file_policy` | Not writing visualization code out to files |
 | `library_selection` | Which plotting libraries the AI should reach for |
 | `rendering` | Panel reactive patterns, and clients that link out instead of embedding |

src/panel_live_server/templates/prompts/instructions.md.j2

@@ -2,6 +2,9 @@
 {% block intro %}Panel Live Server executes Python code snippets and renders the resulting visualizations as live, interactive web pages.{% endblock %}
 
 {% block workflow %}WORKFLOW:
+Before writing hvPlot, HoloViews, or Panel code, call the `developing-with-holoviz`
+skill if it is installed, even in addition to a general chart/design skill. Not
+needed for Bokeh, ECharts, or deck.gl, which this prompt already covers.
 `show(code, name, method)` renders a visualization and gives it to the user.
 `screenshot(code=...)` renders one and returns the picture to YOU only — nothing
 reaches the chat and nothing is added to the user's feed.