vkr-builder: Skill for Claude Code

Writing thesis Markdown

The full specification is docs/llm-format/README.md (Russian) / Markdown format rules. This is the working subset: get these right and lint stays quiet.

Where content lives

• One logical section per file under the profile's markdown_dir; the order is markdown_files in config.yaml. A new file only takes effect once it is listed there.
• _bundle.md is generated by merge and deleted after the build. Never edit it, never commit it, never reference it in an answer — the file the author edits is the one named in a finding's location.
• Output Markdown only. No HTML except the <!-- @suppress --> directive.

Headings

# 1 Название главы
## 1.1 Подраздел
### 1.1.1 Пункт

• No period after the chapter number.
• Structural sections keep their canonical Russian names in caps: # СПИСОК СОКРАЩЕНИЙ И УСЛОВНЫХ ОБОЗНАЧЕНИЙ, # ТЕРМИНЫ И ОПРЕДЕЛЕНИЯ, # ВВЕДЕНИЕ, # ЗАКЛЮЧЕНИЕ, # СПИСОК ИСПОЛЬЗОВАННЫХ ИСТОЧНИКОВ, # ПРИЛОЖЕНИЕ А.
• Appendix letters skip I, O and Cyrillic Ё З Й О Ч Ь Ъ.
• A heading with no body text under it is a finding (empty-section).

Numbered objects: always a key, never a number

![схема](pipeline.png)
Рисунок {pipeline} - Конвейер обработки

Таблица {req} - Требования
| Параметр | Значение |
|---|---|
| A | B |

Листинг {split} - Разбиение блока
```python
def f(): ...

- Figure caption goes **immediately after** the image, no blank line.
- Table and listing captions go **immediately before** their block.
- Separator after the key is a **spaced** ` - ` or ` – `.
- Keys are short, lowercase, unique per kind.
- Numbering is assigned at build time; inside an appendix it restarts as
  `Б.1`, `Б.2`.
- A listing can come from a real file instead of pasted code — the caption
  stays the same, the fence is replaced by one line:

  ```markdown
  Листинг {split} - Разбиение блока
  @listing md.py:582-607