Przejdź do treści
Biblioteka skilli
Marketing i treści · Planowanie

start

/start

Ustala, na jakim etapie są samouczki aplikacji, i wykonuje następny krok, od pierwszej konfiguracji po gotowy pakiet, pytając tylko o decyzje i zgody.

Repozytorium
walkcast ↗
Licencja
MIT
Ostatnia zmiana repozytorium
29.10.2026

Ocena i bezpieczeństwo

84/ 100Klasa: dobry
Format9 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 29.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Ustala, na jakim etapie są samouczki aplikacji, i wykonuje następny krok, od pierwszej konfiguracji po gotowy pakiet, pytając tylko o decyzje i zgody.

Argumenty

/start [optional: what you'd like, e.g. 'only the admin tasks']
Oryginalny opis (EN)

Start here, or pick up where you left off. Works out where this app's tutorials stand and takes the next step, from first setup to the finished bundle, pausing only for questions and the user's approvals. Use when the user wants tutorial videos or SOPs for their app, asks what to do next, or comes back after a break or after the app changed.

Jak działa

  1. 1. See where things stand
  2. 2. Take the next step, and keep going
  3. 3. The look, once
  4. 4. After the app changes
  5. 5. When everything is done
Sekcje z nagłówków SKILL.md, w oryginale · 59 linii, 655 słów
Podgląd SKILL.md
---
description: Start here, or pick up where you left off. Works out where this app's tutorials stand and takes the next step, from first setup to the finished bundle, pausing only for questions and the user's approvals. Use when the user wants tutorial videos or SOPs for their app, asks what to do next, or comes back after a break or after the app changed.
argument-hint: "[optional: what you'd like, e.g. 'only the admin tasks']"
---

# Start, or carry on

Take the user from wherever they are to finished tutorials, one stage at a time, and keep going until something needs them. They shouldn't have to know the stage names.

## 1. See where things stand

Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/status.mjs"` from the project root. It changes nothing. It prints:
- the state of each plan item: tour, storyboard, approval, video, SOP
- the look settings, plus `suggestions` for any that are missing
- whether the bundle is current
- `app_commits_since_storyboard`
- `next`: the stage to run, the tutorial ids it's for, why, and whether it's waiting for the user

Tell the user in a sentence or two where things stand, in plain words. For example: "The plan is approved and 3 of the 5 storyboards are approved; next I'll storyboard the other two."

On a fresh start (`next.stage` is discover and there's no config), explain the whole process in a few lines first:
1. Claude maps the app's features from the code and the running app.
2. It proposes a set of videos and SOPs; **you approve the plan**.
3. It replays each one in the app with a screenshot per step; **you approve the storyboards**.
4. It narrates, records and renders the videos, checks them, and gathers everything into one folder to share.

Mention what they'll be asked for early on: a test account for each role, and a way to reset the demo data.

## 2. Take the next step, and keep going

Run the stage in `next` by following its skill (`/tutorials:<stage>`), with the ids from `next.ids` and anything the user asked for in $ARGUMENTS. When the stage finishes, run status.mjs again and go straight on to the next stage. Don't wait to be asked, and don't make the user type commands. Stop only when:
- **A stage needs the user:** a question only they can answer, or the plan or storyboards waiting for approval (`next.waiting_for_user`). Say exactly what's waiting and where to look (`tutorials/plan.md`, or the `storyboard.html` files, offering to open them), then wait. When they answer, carry on from there.
- **`next.stage` is null:** everything is done.
- **Something fails that you can't fix.** Say what you tried.

Never approve a plan or a storyboard on the user's behalf.

Before a long step, say what's about to happen and roughly how long it takes:
- The first narration installs the voice engine: about 1.2 GB, a few minutes, once.
- Recording takes about as long as each video.
- Rendering takes a minute or two per video.

## 3. The look, once

When produce is next, or when everything is done, offer the `suggestions` from status, all in one message and only once. Each settles with one answer:
- **Brand colors:** `look.mjs` reads them from the app. Set them, then tell the user what you chose.
- **The address in the videos:** `app.display_url`, so they don't show localhost.
- **The narrator:** `voice.mjs --samples` writes a page that plays a few voices.
- **Music:** `music.mjs search` writes a page that plays a few free tracks, or `music: none` to keep it quiet.

Changing any of these after videos exist means rendering them again, which produce does by itself. Say so.

## 4. After the app changes

If everything is done but `app_commits_since_storyboard` is above 0, offer to check the tutorials against the app: run the storyboards again.
- **A tour that still runs** keeps its approval.
- **A tour that fails** shows what changed in the app. Fix the tour, show the user the new storyboard, and have it approved again.
- **Produce** then makes only the videos whose tours changed, and bundle rebuilds the folder.

## 5. When everything is done

Say what exists: how many videos and SOPs, and where the bundle is (`open tutorials/dist/index.html`). Say `/tutorials:start` picks up from here any time, for example after the app changes. Keep it to a few lines.

Wersje

RepozytoriumWynikLicencja
Ta strona · walkcast/walkcast84MIT
tilnoteio/tilnote-blog100MIT
dedujeong/gemba100Apache-2.0
nextwork-projects/ai-video-editor-cooked100MIT
wrg32786/aigent-os100MIT
T-X-R/codex-game-studio100MIT
alienfast/claude100MIT
ratomirjovanovic/pandaward100AGPL-3.0
darioabc/massimo100MIT

Migawka bazy z 13.11.2026 · wersja paczki cd1f1a093f05 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 84bundle
    Zbiera gotowe filmy i procedury do jednego folderu z napisami, rozdziałami, miniaturami, PDF-ami z krokami i stroną indeksową do publikacji.
  • 84discover
    Mapuje funkcje aplikacji widoczne dla użytkownika, czytając kod i eksplorując działający interfejs, a potem zapisuje plik features.yaml.
  • 100status
    Pokazuje, na jakim etapie jest projekt Sentinel CV z dziennika i plików ewaluacji, tylko do odczytu, i proponuje następny krok.
  • 86first-video-tutorial
    Prowadzi przez krok 3 z 4 samouczka i pomaga stworzyć pierwsze wideo.
  • 90help
    Podaje, na jakim etapie jest projekt i jaki krok jest następny, gdy użytkownik nie wie, co robić.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.