Add or modify an access permission in a cardona-core-service backoffice — a new PermissionType enum key, its access-management group entry, and its English label on the roles screen. Use this whenever the user wants to add/register a permission, grant access to a section, wire a `backoffice-*` access key, or edit the permissions config — even phrased as "add access for X", "new permission key", "дай доступ к разделу", "добавь пермишен". Also the first stage when creating a whole new section, but it stands alone: reach for it any time only a permission needs to change, without touching routes, menu, or pages.
Create a whole new CRUD section in a cardona-core-service backoffice, end to end — permissions, route, menu, list page, and create/update form. Use for "add a new section", "create section X", "make a list page with create/edit for Y", "заведи новый раздел", "новый раздел с CRUD". This is the orchestrator: it runs the focused sub-skills in order (backoffice-permissions → section-list → section-form) with a confirmation gate between stages. If the user only needs one piece (just a permission, just a list, just a form), use that sub-skill directly instead.
Add a create/update form to an EXISTING list section in a cardona-core-service backoffice — the create/update routes and pages, the form model class, `useForm`/`sectionConfig`, `SectionForm.vue`, plus the remove modal. Use when the user wants to make a section editable: "add create/edit to X", "make Y creatable", "add a form to the list", "add create and update pages", "сделай раздел редактируемым", "добавь форму создания". Also Stage 5 of building a full section. It extends the `useSection.ts` and `@model` that the list already produced — it does not create a section from scratch (use `section-list` first for that).
Create a list page (BaseList) for a section in a cardona-core-service backoffice — the route (list-only), the menu item, the list model, `useSection.ts` with `useList`, and `list/index.vue`. Use whenever the user wants a list/table view without a create/edit form: "make a list-only section", "add a list page for X", "show a table of Y", "раздел только со списком", "список без формы". Also Stage 4 (+ its route & menu) when building a full section. Produces a working, navigable list with real API data; the create/update form is a separate step (`section-form`).
Generate a QA-facing Impact Analysis for a completed task in the Cardona backoffice — from a git diff of ANY changed files, tell the QA/DevOps engineer exactly WHERE and WHAT to test. Covers app pages (menu path + URL), shared components/models/stores (regression surface), the cardona-core-service dependency (diff its changes too), AND infrastructure — Docker, nginx, Helm charts, GitLab CI, Vite/build config, env, deps. Use this skill whenever a task is finished and someone asks "what should QA test", "impact analysis", "QA report", "regression surface", "affected areas", "где тестировать", or "что проверять после этой задачи" — even without the words "impact analysis". The report text MUST be written in Ukrainian; talk to the user in Russian.
Writing unit tests for the cardona-core-service project. Use this skill whenever the user asks to write tests, create spec files, add unit tests, cover a component/helper/composable/store with tests, or generate any *.spec.ts file. Also trigger when the user says "test this", "add coverage for", or shares a component and asks what tests to write. Do NOT trigger for implementing features, fixing bugs, refactoring, or explaining code.