legible

Build a step-by-step animated explainer as one offline HTML file - the top rung of Karpathy's format ladder, after text, diagrams and HTML pages. Use only when the user asks for an animation, a video-like or step-by-step explanation, "покажи по шагам", "анимацию", runs /legible:animate, or presses the Анимация button on the session board. Do not build one unasked.

Answer with a diagram first and only a few sentences of text, when the content is about structure, flow, sequence, state, dependencies or comparison. Use when the user asks to draw, diagram, visualize, show a schema or a map, says "покажи схемой" or "нарисуй", or when a text answer would need more than about 150 words to describe how parts connect.

Choose the cheapest answer format that still gives understanding, on Karpathy's format ladder - one sentence, ASD-STE100 text, a table, a diagram, an HTML page or an animated explainer - before writing a long answer. Use when an answer is going to be long, when the user says they do not understand, asks "как лучше показать", "what's the best way to explain", or when the content is mostly structure, comparison or process.

Write English in ASD-STE100 Simplified Technical English at a chosen strictness - 80% of the way to ASD-STE100 by default, 50% or 100% on request. Use when the user asks for ASD-STE100, STE, Simplified Technical English, "80% of the way to ASD-STE100", or for plain, simple, clear or controlled English; when the user asks to clean up, simplify or rewrite text in plain English (a PR description, docs, a summary, a status update, an error message); and when you write text that a busy reader or another agent must parse fast.

Пиши по-русски в «упрощённом техническом русском» (plain-ru) с измеримой строгостью — plain-ru-50, plain-ru-80 по умолчанию, plain-ru-100. Use when the user writes in Russian and asks for простой, понятный, ясный, технический текст, «без воды», «без канцелярита», «как STE, но по-русски», and when you write Russian summaries, docs, explanations or board text that a person must read fast.

Check that the user understood an explanation with three short questions, then re-explain in a different format where the answer was wrong. Use when the user asks to check their understanding, says "проверь меня", "check me", "quiz me", runs /check-me, or accepts the offer at the end of a visual explanation.

Build a one-off visual explanation for a complex topic - an overview-first, drill-down explanation with diagrams, rendered natively in the session board pane, or as a single HTML file only when the user asks for HTML. Use when the user asks to explain how something works in depth, wants an explainer, an interactive explanation, "объясни наглядно", "сделай визуализацию", or when a topic has several interacting parts that text and one diagram cannot carry.