メニュー
Register a kickstart-generated or adopted repo in a Backstage software catalog using the deterministic `kickstart export backstage` verb, then fill in the human judgment fields. Use when asked to add a scaffolded or adopted project to Backstage.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Cut, tag, and verify a kickstart release. Use when asked to release, tag, bump, or ship a new kickstart version, or to retag the current release line after a same-version fix.
Run kickstart's scaffold-shape and generated-make-test evals after generator, layout, or template wiring changes, and report results by failure class.
Use the installed kickstart binary whenever an agent is asked to create or scaffold a service, project, frontend, library, CLI, system, or other starter repo.
Update kickstart-cli.org content - release notes, version metadata, and command examples - and verify the changes against the tests that enforce them. Use when asked to update the website, changelog page, or showcased examples.
SOC 職業分類に基づく
| name | backstage-catalog |
| description | Register a kickstart-generated or adopted repo in a Backstage software catalog using the deterministic `kickstart export backstage` verb, then fill in the human judgment fields. Use when asked to add a scaffolded or adopted project to Backstage. |
Use this skill when asked to add a kickstart-generated (or adopted) repo to a Backstage catalog. The mechanical mapping is owned by the deterministic verb — never hand-derive it; this skill supplies the judgment the verb deliberately does not.
kickstart export backstage <repo>. It derives catalog-info.yaml
from .kickstart/scaffold.json: derived fields (apiVersion, kind,
metadata name/tags/techdocs annotation, and for systems the System entity
plus child Components) sit inside # kickstart:begin/end fences and
refresh on every run; spec.type, spec.lifecycle: experimental, and
spec.owner: group:default/unknown are emitted once as anonymous
defaults and then belong to the user.catalog-info.yaml is refused by the verb —
migrate it by moving its human fields outside a fresh export's fences.spec.owner: ask the user; replace the group:default/unknown
sentinel with the real owning group.spec.lifecycle: keep experimental unless the user states otherwise.metadata.description: add a one-liner if the README gives a better
one than none.apiVersion,
kind, metadata.name, spec.type, spec.lifecycle, spec.owner
(the verb warns on missing required lines — resolve warnings before
reporting done).Report the file path, created/updated/unchanged, the owner and lifecycle chosen, and any scaffold fields that had no catalog equivalent.