mcpField
A
aiediting

aiediting

github.com/alexfisenkovその他09 回インストール今日更新
リポジトリ

aiediting について

説明はまだありません

インストール

コマンドをコピーしてターミナルで実行します。

$npx skills add https://github.com/alexfisenkov/aiediting --skill aiediting

インストール後、Claude Code で/aieditingを入力して読み込まれたか確認します。

README(原文)English

プロジェクトの README より

この README の日本語訳はまだありません。以下は英語の原文です。日本語の紹介はページ上部をご覧ください。

AIEditing

AIEditing is a workshop. It exists to create a format skill — монтаж-<the person's word> — or to refine one that exists. It interviews the person, looks at frames of their own footage, builds a design system with them, edits a trial of their source to show (one piece, or where the format has paths a short probe of each and then the chosen one in full), reworks it until they say «да», and then builds and installs the format skill globally. From then on the format skill does the editing; the workshop is not needed again until something should change. A person who asks for no questions gets all of this from one message: the finished video first, the skill installed with it.

The workshop is the base of how a video can be edited. Narrow skills come out of it: for a niche, a task, the person's own design system. Where a format can go more than one way, it offers the ways, shows each on the person's video, and builds only what they chose. It stays open: any installed монтаж-* can be changed here later, together with the person, even one built by hand or by someone else, and what no profile describes stays with that skill (phases/refine.md). A way the catalog lacks goes into it for the next person.

What the workshop never does — in every phase, whatever is asked: it never publishes, uploads or sends anything, never voices, never generates video, music or images. Its only edits are these trials, shown on the dashboard and kept in the workshop folder, with one exception: what the overlay kit renders needs a working folder outside it, ~/.local/share/overlay-kit/…, because rendering from a cloud-synced folder hangs; without questions, the built skill edits the whole recording into its issue folder instead. The same holds for every format skill it builds: «смонтируй как <слово> <путь>» → a folder with the video, .srt and a short report. Nothing else.

Reading this skill

This file is the order and the rules that never lose. Each phase's rules are in its own file, read when that phase starts and not before — one at a time; a file opened early stays in the context for the rest of the session.

Stage idReadProduces
startphases/start.mdthe dashboard open; «новый» or «доработка» chosen
formatsphases/formats.mdone draft profile per format, listed or the person's own
sourcesphases/sources.md1–3 sources, their frames and layout on the dashboard
interviewphases/interview.md + prompts/question-round.mdthe profile answered, round by round; the paths of the format offered
designphases/design.mddesign/ of the skill, chosen variants
trialphases/trial.mda probe of each path and their choice, where the format has paths; a trial clip the person said «да» to; every remark in the profile
buildphases/build.mdмонтаж-<слово> built, its tools installed on «да», installed globally
—phases/refine.md — instead of formats and sources, when refining
—phases/resume.md — instead of start, when .aiediting-work/state.js is unfinished
—phases/no-questions.md — instead of all of them, when the person asked not to be askeda finished video and the skill installed

Their words choose the path. The person asked not to be asked (the signal is at the top of that file) → phases/start.md, §1, then phases/no-questions.md, in place of every phase but the ones it names. Everything below that says «asked» or «да» reads there as that phase says; the limits on publishing, generating, paying and keys do not move.

After a compaction re-read .aiediting-work/state.js, the draft profile.json of the format in work, and the file of the current phase. Nothing else. With noQuestions in state.js that is phases/no-questions.md, its решения.md, and the method of the step you are in.

The words the person sees

Instructions here are English; the person is spoken to in their language — Russian unless they write in another one. One word per stage, on the dashboard and in the chat: Старт · Форматы · Исходники · Интервью · Дизайн · Пробный монтаж · Сборка. The thing being made is «скилл формата» or «скилл монтажа», named монтаж-<слово> with the person's own word.

The tool

Every event is one call: python "<skillDir>/tools/ae.py" <command> — init, no-questions, stage, ask, answered, formats, profile, variant, frames, layout, design-example, samples, choose, trial, show, hear, kit, verdict, build-skill, install-skill, list-skills, backup-skill, restore-skill, doctor, finish. The command list with arguments is at the top of tools/ae.py. phases/start.md says how to find <skillDir>. You never edit state.js or the dashboard by hand. Where there is no python, as on many Macs, use python3; where it is the Microsoft Store stub on Windows, use py -3.

Rules that never lose

  1. A key is never asked for, echoed or written. Which recogniser, whether an account exists — yes. The key itself — never: the person puts it into their environment or .env by the variable name.
  2. A fact about the person is never invented — the output folder, the brand glossary, the music library: asked, or left as a visible gap in the profile.
  3. Nothing is installed without «да». doctor --install <id> --yes only after the person agreed to that tool, by its pin from catalog/tools.json. Only tools the interview chose; heavy ones (the whisper model) are offered with their size. Steps marked not_built in catalog/steps.json are not offered. Asking for no questions is that «да» for the chosen steps' tools, and each is named at the end.
  4. Examples are always on the person's own video. No source of the needed kind → ask for one; without it the question is asked in words, without an example.
  5. Every remark on the format goes into the profile (ae.py profile taste), and only AIEditing changes a profile — a format skill writes remarks into its report and suggests «запусти AIEditing — доработка».
  6. The previous version is kept. Installing over a skill moves the old one to the reserve; restore-skill brings it back in one command.
  7. The format skill holds only what was chosen — steps, tools and design; nothing «на всякий случай».
  8. A format with paths is never built without a choice. The person chooses after seeing the probes on their own video; asking for no questions makes it your choice, named in the last message.

Files

.aiediting-work/                 in the folder where the workshop was started
├── state.js  dashboard.html  index.html  serve.pid  serve.log
├── frames of the person's sources: `ae.py frames` prints their paths
└── монтаж-<слово>/
    ├── profile.json             the draft profile — data only, no keys
    ├── design/                  tokens, fonts, samples/ (chosen variants)
    ├── variants/<element>/      design variants shown side by side
    └── trials/01/ …             trial pieces, вопросы.json / ответы.json, out/
overlay-kit/                     in this skill: the method and tools of the `graphics` and `reedit` steps, copied into formats that use them
~/.agents/skills/монтаж-<слово>/ the installed format skill; pointer in ~/.claude/skills/
~/.agents/skills/.aiediting-backups/  previous versions

Updating AIEditing

Never mid-session. «Обнови AIEditing» → npx skills update aiediting -g, then a new session. Format skills are separate folders with their own copy of the runtime: updating or removing AIEditing never breaks them; a refinement rebuilds them on the new version.

コメント