nix

Summarize the current diff per file as markdown: a `## <filepath>` heading per changed file followed by a prose summary of its changes. Triggers: /changes, "summarize the diff", "what changed per file", "per-file summary of changes", "суммаризируй дифф", "что изменилось по файлам". Skip for reviewing quality or bugs (use /code-review) and for raw diff output (plain `git diff`).

Compress an expository note into readable prose backed by a certified Glossary via a standalone CLI — abstractive idea-compression, not extractive trimming. Re-expresses the note as flowing prose (carrying the thesis and the relations among terms) above an optional `## Workflow` checklist of the note's actionable directives and a definitions-only `## Glossary` table, collapsing restatements to one entry each and keeping only operational tokens verbatim; a different model fidelity-grades the glossary definitions and the workflow steps against the source and surfaces anything that did not translate. Replaces /cut. Use on /distill, "distill this", "compress this note", "make a glossary of this note", "tighten this into its ideas", "summarize as a glossary", "compress this guide/procedure into steps", "this note is too long/verbose", «дистиллируй», «сократи в глоссарий», «выжимка», «сделай глоссарий», «сократи гайд в шаги»; route whole-repo glossary maintenance to /glossary.

Route the current context to one expert persona and return that lens's candid second opinion. Auto-classifies to the best-fit persona, or name one explicitly. Runs the persona as a spawned subagent so its reasoning stays out of the main context. Roster spans engineering, product, go-to-market, and craft. Out of scope: generating new designs (use /design), arguing both sides (use /debate), stress-testing one plan (use /probe), scoring confidence in a claim (use /grade). Invoke explicitly with /opinion.

Personal knowledge management in an Obsidian vault. Use whenever the user wants to save, find, review, or organize knowledge, even without saying "vault". Triggers: saving links/articles as references, distilling concepts into cards, writing original notes, searching or quizzing saved content, listing active projects ("what am I working on"), explicit /vault commands, weekly-log operations (backlog/бэклог, planning, completing tasks, sleep). Excludes direct file edits not routed through /vault (editing a .md file in a code repo that is not a vault artifact), Obsidian app features (kanban, canvas, plugins, .base), web search. Skip for session save/resume ("wrapping up", "where did we leave off") — use /track.

Orchestrate a multi-step task by delegating to fresh subagents, keeping the orchestrator session small. Triggers: /work <task>, "orchestrate this", "delegate this work". Skip one-shot questions, single-file edits, and the ambient "let's work on X" / "start working on X" phrasing.

Test an existing thing's behavior against a falsifiable claim and capture the result as a standalone Markdown record in the current working directory. Self-contained — no vault, no external templates, no project linking. Triggers: /experiment, "run an experiment", "test this claim", "verify whether", "does X actually", "check if X works", "is X true", "falsifiable claim".

Read or save a per-repo track — the rolling handoff file in `<repo-root>/.tracks/track-<slug>.md`. Triggers on explicit `/track` and `/track save` commands. Also triggers on session save/checkpoint phrases: "wrapping up", "save what we did", "log what we accomplished", "save our progress", "end of session", "save session", "we finished X and still need to do Y". Triggers on resume phrases: "what was I working on", "where did we leave off", "continue where I left off", "pick up the track". Track creation, status changes, Decisions/Backlog/Log edits, atomic write to disk all live here. Self-contained: no vault, no external config, no extra tools — just the repo working tree.

Rewrite negative instructions as positive directives and remove hedging language. Use when user invokes /affirm or asks to make instructions direct, remove hedging, flip negatives to positives, or strengthen language in skill files, docs, or prompts. Works on inline text, files, or conversation context. Target instruction and directive text only; route general prose editing to /distill.

Draft a per-stakeholder status update from real work artifacts, or diagnose a stakeholder complaint as a state-gap vs a target-gap before you react. Drafts, never sends. Reads git/track/weekly-log; writes only each stakeholder's last_drafted in context.md. Out of scope: sending, scheduling, internal session logs (use /track). Invoke explicitly with /brief.

Stage and commit changes with a conventional commit message. Triggers: /commit, "commit", "коммит", "закоммить", "сохрани изменения". Covers new commits only; amend, rebase, and push fall outside scope.

The fal.ai worker for the /imagen hub; use directly only to pin the provider. Triggers: /imagen-fal, explicit mentions of "Kling", "BiRefNet", "fal.ai image", or "use fal". Skip for non-image tasks, text-in-image prompts (route to imagen-nanobanana), and ambiguous image requests (those route through the /imagen hub). Trigger only on explicit fal/Kling/BiRefNet mentions or direct invocation.

The Google Nano Banana (Gemini) worker for the /imagen hub; use directly only to pin the provider. Triggers: /imagen-nanobanana, explicit mentions of "Nano Banana", "Gemini image", or "use Nano Banana". Edit or restyle existing images by passing them as --source. Skip for non-image tasks and for ambiguous image requests (those route through the /imagen hub).

Router hub for image generation. Triggers: /imagen, "generate an image", "create a picture", "make an image", «нарисуй», «сгенерируй картинку». Dispatches to either imagen-nanobanana (Google Nano Banana / Gemini, direct API) or imagen-fal (Kling O1 + BiRefNet via fal.ai) based on prompt characteristics; invoke the worker skills directly only when you need to pin a provider.

Search tool for modern web development best practices. MANDATORY: Execute first for all HTML/CSS and clientside JS tasks. Web APIs evolve faster than training data, so check the local guides before implementing. Trigger immediately for: - UI/Layout: Modals, dialogs, popovers, Glassmorphism/backdrop-filters, anchor positioning, container queries, `:has()`, `:user-valid`. - Scroll/Motion: View Transitions, Scroll-driven animations, scroll parallax/reveals. - Performance: CWV (LCP, INP), content-visibility, Fetch Priority, image optimization. - System/APIs: Local filesystem access, WebUSB, WebSockets sync, WebAssembly widgets. - Frameworks: Adapting layout/styles in React, Vue, Angular. - General Frontend: Forms, autofill, advanced inputs, custom scrollbars, modern component states, etc. DO NOT trigger for: - Backend: Database SQL, ORMs, Express API routes. - Pipelines: CI/CD deployment, Docker, Actions. - Generic: Local scripts (Python/Go tools), ESLint, Git.

Force four declarations (question, throwaway/retained, time-box, capture) before generating any prototype code. Select a method (spike, tracer bullet, walking skeleton, Wizard of Oz, prompt-as-prototype) from the declarations, run the workflow, produce a capture artifact (decision memo, ADR, eval set, or RFC). Triggers: /prototype, "prototype X", "spike", "throwaway", "PoC", "proof of concept", "is X feasible", "explore Y approach", "tracer bullet", "walking skeleton", "vibe-code this", "quick demo of"; Russian: «прототип», «спайк», «прощупать», «по-быстрому накидать». Skip on feature work with a known design, bug fixes, refactors, or production code paths; prototypes resolve open questions, not closed ones. Also skip when testing an existing behavior against a falsifiable claim without building new code (use /experiment).

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Teach the user a new skill or concept, within this workspace.

The fal.ai worker for video generation; produces a Kling-rendered MP4 as the master output (always kept). Pass --webm to also encode a VP9 WebM loop alongside it (default 640px wide, ~1–3 MB for a 5s clip). Targets Kling v1.6 by default (standard tier); pass --pro for the pro tier. No router hub exists today; invoke this skill directly. Triggers: /vidgen-fal, "generate a video", "make a looping video", explicit mentions of "fal video", "Kling video". Skip for image-only tasks and non-video generation requests. Skip when the user supplies a reference image wanting image-to-video — this script is text-to-video only.

Write or read an ephemeral handoff: a short-lived markdown packet that carries work-state between agents or sessions through a mktemp file path. Triggers: /handoff, "write a handoff", "hand this to the next session", capturing state before you /clear or compact context. Templates: brief (delegator→worker), result (worker→delegator), continuation (session→successor). For durable cross-session memory use /track; for orchestration use /work.

Draft a per-stakeholder status update from real work artifacts, or diagnose a stakeholder complaint as a state-gap vs a target-gap before you react. Drafts, never sends. Self-contained — no vault, no external config, no extra tools: reads the git repo containing cwd and the roster in `<repo-root>/.brief/context.md`; writes only each stakeholder's `last_drafted` there. Out of scope: sending, scheduling. Invoke explicitly with /brief.

Use this skill to recover the user's own prior thinking (opinions, positions, definitions, past decisions, reasoning) from their personal vault before answering, via `vault-query consult`. Trigger whenever the user asks for their own judgment: "what's my take on X", "how do I usually frame or define Y", "what have I already reasoned or decided about Z", their stance on a design fork, or planning work they've deliberated before. This holds even when the surface topic is code or engineering; the signal is the request for the user's view, not the subject matter. The tool abstains silently when nothing fits, so consulting is cheap. Limit triggering to tasks where the user's opinion is sought; mechanical execution (running commands, editing, refactoring, debugging code, file operations, routine boilerplate setup, even when phrased "how do I usually") and conversational/meta turns fall outside scope. Manually invocable as /consult <task>.

Scaffold a vault project folder and link the current repo via .vault.config.json. Use on /project-setup or "set up a new project".

Test an existing thing's behavior against a falsifiable claim and capture the result as a structured record in the vault. Triggers: /experiment, "run an experiment", "test this claim", "verify whether", "does X actually", "check if X works", "is X true", "falsifiable claim". Skip when building a new artifact (use /prototype), interrogating plan logic (use /probe), or rating confidence in a recommendation (use /grade).

Codemod-first refactor pattern. Use when a refactor touches more than 20 files, when renaming across packages, when changing a function signature used everywhere, or when migrating between library versions.

Structured debate exploring a topic through Defender/Skeptic roles. Use when user invokes /debate or wants to analyze a claim from multiple angles with systematic argumentation. Also use when the user asks for pros and cons, devil's advocate, "argue both sides", steelman/strawman, "is X really better than Y", "convince me", or "arguments for and against". Route to /design when the goal is to generate new concrete solutions from scratch.

Generate multiple radically different designs for a module, interface, or system using parallel subagents. Triggers: /design, "design it twice", "what are my options for", "compare architectures". Skip when comparing existing options (use /debate) or stress-testing one plan (use /probe).

Create a git branch with a conventional <prefix>/<slug> name, cut from an up-to-date default branch. Triggers: /git-branch, "new branch", "create a branch", "start a feature branch", "новая ветка", "создай ветку", "заведи ветку". Skip for switching to an existing branch (plain `git checkout`).

Bootstrap and maintain a project glossary as a 2-column Markdown table. Triggers: /glossary, "build a glossary", "document the jargon", "define project terms". Use proactively when the user discusses ambiguous domain terminology.

Grade a decision/recommendation/claim on a 1-10 confidence scale. Use on /grade or "rate confidence in X". Skip when the user wants both sides argued rather than a single confidence score (use /debate). Skip when the goal is stress-testing a plan for holes (use /probe). Skip when the claim is empirically testable by running a command (use /experiment).

Demand a sufficient reason for each element (code, plan step, or action) and recommend cutting whatever cannot earn its place. Use on /justify: defaults to the working-tree diff, "justify actions" audits the recent action transcript, or pass a file path or plan to audit that. Also triggers on: "does this need to be here", "is this justified", "what can we cut", "does this carry dead weight", "audit this diff", "is this code/step/action necessary". To stress-test a plan's decisions use /probe; for code cleanups that assume the code should stay use /simplify.

Проверка текста на логические ошибки по Виноградову/Кузьмину: законы логики, правила доказательства, определения и деления. Use to check reasoning, find fallacies, audit an argument. Triggers: /logic-check, "проверь логику", "check the reasoning". Output language matches input (RU/EN).

Convert files to Markdown via Microsoft's markitdown (uvx). Use for PDFs, DOCX, PPTX, XLSX, images, audio, HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs. Triggers: /markitdown, "convert this file to markdown", "extract text from this PDF", "read this DOCX", "transcribe this audio". Skip for PDF manipulation (merge, split, rotate, fill forms, create) — use pypdf/reportlab; web page scraping — use firecrawl; DOCX editing or form-filling; files Claude can read natively.

Create pull requests. Triggers: /pr, "create pr", "open pr", "draft pr", "сделай PR", "оформи PR", "пулл реквест". Skip for inspecting an existing PR's state, comments, or CI; those are plain `gh` commands (see Reference).

Systematically interrogate a plan or design until every decision branch is resolved. Use when user invokes /probe or wants to stress-test a plan, poke holes in a design, find weaknesses in a proposal, get grilled on their approach, or asks "what am I missing". For open-ended comparisons, use debate instead. Probe requires a concrete plan as input.

Convert freeform workflow text into structured pseudocode for SKILL.md files. Triggers: /pseudocode, "write pseudocode", "convert to pseudocode", "make this a skill", or converting a SKILL.md prose procedure into a pseudocode block. Skip when the goal is to create or iterate on a skill holistically (use skill-creator).

Test-driven development for agentic coding: one failing test, one implementation, repeat. Triggers: /tdd, "write tests first", "test-driven", "TDD", "red green refactor", "write a failing test". Skip when testing an existing behavior against a falsifiable claim (use /experiment); skip for a feasibility spike with no known design (use /prototype).

Read or save a per-project rolling work log at `41 projects/<project>/track-<slug>.md`. Triggers: `/track`, save phrases ("wrapping up", "save session", "end of session"), resume phrases ("what was I working on", "where did we leave off"). Non-track artifacts (cards/notes/references) route to /vault.

Interact with Basecamp via CLI: projects, todos, cards, messages, schedule, files. Use for any Basecamp action.

AI-driven structured-data extraction returning JSON via Firecrawl. Routed to from /firecrawl.

Search, scrape, fetch, crawl, map, download, or interact with web pages via the Firecrawl CLI. Use whenever the user provides a URL, asks to fetch/scrape/grab/pull online content, searches the web, or downloads a site. Hub that routes to firecrawl-{search,scrape,crawl,map,download,agent,instruct}.