AlemTuzlak

Use when writing, editing, or organizing documentation, when planning what docs a feature needs, and whenever planning or implementing a new feature or change in a repo (docs ship with the code). Triggers on "write docs for X", "document this feature", "add a guide", "update the docs", "reorganize the docs", "plan feature X", "implement X", or /docs.

Use when the user wants to write, draft, or author an RFC (Request for Comments) / technical design doc for a feature, change, or architectural decision. Interactively interviews the user, grounds the proposal in the actual codebase, presents 2-3 concrete API/code-snippet approaches to choose from, then writes a review-ready RFC. Triggers on "write an RFC", "draft an RFC", "RFC for X", "design doc for X", or /rfc.

Use when the user wants to create presentation slides, a slide deck, a technical talk, or a conference talk for a topic or library — built on Slidev. Interviews the user, deep-researches and code-grounds the topic FIRST, applies presentation-craft best practices, generates a Slidev deck, self-verifies it in a headless browser, and ends with the dev server running and the deck open in the browser with zero manual steps. Triggers on "make a presentation", "make slides", "build a deck", "presentation about X", "technical talk", "conference talk", "slidev deck", "build slides for X", "present <library>".

Use when the user wants to generate a rendered promotional video (not just a script) for a PR, feature, or product change — produces a HyperFrames HTML composition, iterates with `npx hyperframes preview`, and outputs mp4 + poster for X/LinkedIn/social.

Use when the user wants to turn a raw talking-head / screen-share recording into a finished, edited, annotated video plus a full content package. Removes silences, flags mistakes for the user to cut, transcribes, adds transcript-synced overlays (code, on-screen code highlights, word highlights, lists, comparisons, diagrams, section labels, punch-in zooms), renders with original audio, then generates blog/socials/YouTube content. Triggers on "produce a video", "edit my video", "annotate my recording", "/produce-video".

Use when the user wants to transcribe a video or audio file to text with word-level timestamps — spins up a self-contained local Whisper (whisper.cpp) Docker service bundled in this skill and returns transcript.txt, transcript.srt, and word-level transcript.words.json. Also used as a building block by /produce-video. Triggers on "transcribe this video", "get a transcript", "transcribe-video".

Use when the user wants to write a blog post about a feature, product change, PR, git diff, or any technical topic - accepts marketing briefs, PRs, git refs, codebase paths, or freeform descriptions as input

Use when the user wants to create social media posts or launch copy for a feature, product change, PR, or announcement - generates platform-specific copy for Twitter/X, LinkedIn, and other platforms

Write Markdown/MDX code fences that type-check, and debug ones that fail when they look correct. Load when authoring doc examples or fixing Kiira errors. Covers fence metadata (`ignore`, `validate`, `fixture`, `name`, `group`, `package`), grouping multi-fence walkthroughs and `defaultGroup: "file"`, fixtures for needed scope, `ts`->`tsx` mistags, unused-symbols and relative imports ignored by default, and never silencing a valid error with `ignore`.

Gate CI on Markdown doc errors and keep examples current. Load when wiring `kiira check` into CI, choosing a reporter, or interpreting exit codes. Covers exit codes (0 clean, 1 doc errors, 2 config/runtime failure), the `github`/`json`/`pretty` reporters, the `AlemTuzlak/kiira@v1` composite action, plain exit-code-gated steps for any runner, `--entry` overriding `include`, and `--static`/`--raw` for clean log capture.

Use Kiira's live type-checking in VS Code. Load when setting up the editor experience, configuring extension settings, or debugging why diagnostics don't update. Covers on-change/on-save diagnostics mapped to the fence line, the four commands (Check Current File, Check Workspace, Open Virtual File For Snippet, Restart Kiira Server), settings (enable, configPath, debounceMs, checkOnChange, checkOnSave, showGeneratedDiagnostics), quick fixes, and that the extension reads the same kiira.config.ts as the CLI.

Set up Kiira on a project's docs. Load when installing kiira, running the first `kiira check`, scaffolding with `kiira init`, or deciding whether a `kiira.config.ts` is needed. Covers installing where the API types resolve, the only required option (`include`), the ts/tsx/js/jsx fence format in .md/.mdx, and the automatic `tsconfig.docs.json` preference.

Make Kiira resolve the real API in monorepos and multi-framework docs. Load when docs import internal `@scope/*` workspace packages, when fences use Solid/Preact/Vue JSX, or when seeing TS7026 / unresolved workspace imports. Covers `packageMode` workspace vs packed, why hand-written tsconfig `paths` are unnecessary, per-glob `overrides` (last match wins), and `jsxImportSource` plus `kiira check --fix` writing the override.