ワンクリックでManusで任意のスキルを実行

section-creator

スター5

フォーク0

更新日2026年7月16日 08:25

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

upstars-global

upstars-global/cardona-core-service

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Create a New Section (orchestrator)

The target is a Vue 3 + TS + Pinia + Vuetify backoffice built on cardona-core-service. A full CRUD section spans permissions, routing, menu, a list page, and a create/update form. That work is split across three focused, independently-usable skills; this skill orchestrates them into one guided flow for a brand-new section.

Each sub-skill also stands alone — if the task is only one of these, skip the orchestration and invoke that skill directly:

backoffice-permissions — add the access key + localized label.
section-list — the list route (list-only), menu item, list model, useList, list/index.vue.
section-form — create/update routes + pages, form model, useForm, SectionForm.vue, remove modal.

How to run it — stage by stage

Work strictly one stage at a time. After each stage, stop, report what changed, run yarn typecheck && yarn lint, and wait for the user's confirmation before the next. Do not do everything at once — each stage produces something the user should verify, and later stages depend on the exact names chosen earlier.

Permissions — load the backoffice-permissions skill and follow it. Adds the PermissionType key + group entry + en.json label. → confirm → stop.
List (route + menu + list) — load the section-list skill and follow it. Registers a list-only route via a hand-written module file (src/plugins/2.router/modules/<section>.ts) — not a generator entry, because the generator can't do list-only — plus the menu item and the BaseList page. It captures the real API JSON mid-way, so expect a pause to get the Network response + Figma from the user. → confirm → stop.
Create/Update — load the section-form skill and follow it. It upgrades the routing (if the section fits sectionRouterGenerator, it deletes the module file and adds a single generator entry giving list+create+update; otherwise it appends create/update routes to the module and tells the user why), creates the create/update pages, and extends the useSection.ts and @model/<name>.ts that Stage 2 produced (adds useForm/sectionConfig/<Name>Form). → confirm → done.

The confirmation gate matters because the sub-skills also need mid-flow input from the user (permission key from backend, real list JSON, Figma, sample Read/Create payloads) — surface those requests at each stage rather than guessing.

Pre-flight — collect upfront

Gather these before Stage 1 so the stages flow without repeated round-trips (each sub-skill re-states what it needs, but having them ready helps):

Section name (camelCase) — e.g. vipSeasons. Drives route names (VipSeasonsList/Create/Update), menu to, folder.
Permission key (backoffice-<...>) — comes from the backend. Do not guess.
Menu group — existing group (Gamification, Players, Promo, Settings, …) + the neighbor to sit next to.
Pages folder — src/pages/<folder>/, usually the menu group.
Page set — usually full CRUD (List + Create + Update). A single standalone page → section-list with isSingleRoute; a card detail → withCard.
entityName — backend hyphen format (e.g. 'Vip-ServiceSeason-Vip-Status'). Ask, don't guess.

Naming conventions

camelCase section: vipSeasons · PascalCase route: VipSeasonsList · kebab URL: /vip-seasons · permission enum: BackofficeSeasonVipStatus = 'backoffice-season-vip-status' · entityName backend hyphen: 'Vip-ServiceSeason-Vip-Status'.

Partial / non-standard cases

List-only section (no form) — run only Stage 1 + Stage 2 and stop. A common shape.
Add a form to an existing list — skip straight to section-form.
Only a permission — just backoffice-permissions.

このリポジトリの他の Skills

同じリポジトリ

backoffice-permissions

upstars-global/cardona-core-service

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.

2026-07-165

section-form

upstars-global/cardona-core-service

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).

2026-07-165

section-list

upstars-global/cardona-core-service

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`).

2026-07-165

impact-analysis

upstars-global/cardona-core-service

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.

2026-07-135

write-tests

upstars-global/cardona-core-service

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.

2026-06-185

name

section-creator

description

Create a New Section (orchestrator)

Each sub-skill also stands alone — if the task is only one of these, skip the orchestration and invoke that skill directly:

backoffice-permissions — add the access key + localized label.
section-list — the list route (list-only), menu item, list model, useList, list/index.vue.
section-form — create/update routes + pages, form model, useForm, SectionForm.vue, remove modal.

How to run it — stage by stage

Permissions — load the backoffice-permissions skill and follow it. Adds the PermissionType key + group entry + en.json label. → confirm → stop.
List (route + menu + list) — load the section-list skill and follow it. Registers a list-only route via a hand-written module file (src/plugins/2.router/modules/<section>.ts) — not a generator entry, because the generator can't do list-only — plus the menu item and the BaseList page. It captures the real API JSON mid-way, so expect a pause to get the Network response + Figma from the user. → confirm → stop.
Create/Update — load the section-form skill and follow it. It upgrades the routing (if the section fits sectionRouterGenerator, it deletes the module file and adds a single generator entry giving list+create+update; otherwise it appends create/update routes to the module and tells the user why), creates the create/update pages, and extends the useSection.ts and @model/<name>.ts that Stage 2 produced (adds useForm/sectionConfig/<Name>Form). → confirm → done.

Pre-flight — collect upfront

Gather these before Stage 1 so the stages flow without repeated round-trips (each sub-skill re-states what it needs, but having them ready helps):

Section name (camelCase) — e.g. vipSeasons. Drives route names (VipSeasonsList/Create/Update), menu to, folder.
Permission key (backoffice-<...>) — comes from the backend. Do not guess.
Menu group — existing group (Gamification, Players, Promo, Settings, …) + the neighbor to sit next to.
Pages folder — src/pages/<folder>/, usually the menu group.
Page set — usually full CRUD (List + Create + Update). A single standalone page → section-list with isSingleRoute; a card detail → withCard.
entityName — backend hyphen format (e.g. 'Vip-ServiceSeason-Vip-Status'). Ask, don't guess.

Naming conventions

camelCase section: vipSeasons · PascalCase route: VipSeasonsList · kebab URL: /vip-seasons · permission enum: BackofficeSeasonVipStatus = 'backoffice-season-vip-status' · entityName backend hyphen: 'Vip-ServiceSeason-Vip-Status'.

Partial / non-standard cases

List-only section (no form) — run only Stage 1 + Stage 2 and stop. A common shape.
Add a form to an existing list — skip straight to section-form.
Only a permission — just backoffice-permissions.