- Skills
- 16
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
oshnilia 的 Skills 16
take
Take a ticket from the project's Obsidian board into work - pick it, turn it into the task brief, set its status. Use when the person asks to take, start or pick up a ticket or task from the Obsidian board, asks what is next on the board ("возьми тикет", "что дальше по доске"), names a card or a note of the bound board, or runs /obsidian-tasks:take.
setup
Bind this project to a task board in an Obsidian vault (a Kanban plugin board or a Bases board), or create one, and choose how Claude reaches the vault - its folder, the Obsidian CLI or an Obsidian MCP server. Use when the person asks to connect an Obsidian board or vault to the project, to change the board, or to check the binding ("подключи доску из Obsidian", "настрой obsidian-tasks"), or runs /obsidian-tasks:setup.
rules
The rules for this project's Obsidian task board - keep the ticket's status, write the closing report, file new tickets for what is out of scope. The start hook prints them when the project is bound to a board; load them when you work with a ticket and they are not in your context.
take
Take a ticket from the project's Notion board into work - pick it, turn it into the task brief, set its status. Use when the person asks to take, start or pick up a ticket or task from Notion, asks what is next on the board ("возьми тикет", "что дальше по доске"), gives a link to a ticket on the bound board, or runs /notion-tasks:take.
setup
Bind this project to a Notion task board, or create a new board, and save the binding in the project. Use when the person asks to connect Notion tasks or a Notion board to the project, to change the board, or to check the binding ("подключи доску Notion", "настрой notion-tasks"), or runs /notion-tasks:setup.
rules
The rules for this project's Notion task board - keep the ticket's status, write the closing report, file new tickets for what is out of scope. The start hook prints them when the project is bound to a board; load them when you work with a ticket and they are not in your context.
visual-explainer
Build a one-off visual explanation for a complex topic - an overview-first, drill-down explanation with diagrams, rendered natively in the session board pane, or as a single HTML file only when the user asks for HTML. Use when the user asks to explain how something works in depth, wants an explainer, an interactive explanation, "объясни наглядно", "сделай визуализацию", or when a topic has several interacting parts that text and one diagram cannot carry.
teach-back
Check that the user understood an explanation with three short questions, then re-explain in a different format where the answer was wrong. Use when the user asks to check their understanding, says "проверь меня", "check me", "quiz me", runs /check-me, or accepts the offer at the end of a visual explanation.
plain-russian
Пиши по-русски в «упрощённом техническом русском» (plain-ru) с измеримой строгостью — plain-ru-50, plain-ru-80 по умолчанию, plain-ru-100. Use when the user writes in Russian and asks for простой, понятный, ясный, технический текст, «без воды», «без канцелярита», «как STE, но по-русски», and when you write Russian summaries, docs, explanations or board text that a person must read fast.
plain-english
Write English in ASD-STE100 Simplified Technical English at a chosen strictness - 80% of the way to ASD-STE100 by default, 50% or 100% on request. Use when the user asks for ASD-STE100, STE, Simplified Technical English, "80% of the way to ASD-STE100", or for plain, simple, clear or controlled English; when the user asks to clean up, simplify or rewrite text in plain English (a PR description, docs, a summary, a status update, an error message); and when you write text that a busy reader or another agent must parse fast.
format-router
Choose the cheapest answer format that still gives understanding, on Karpathy's format ladder - one sentence, ASD-STE100 text, a table, a diagram, an HTML page or an animated explainer - before writing a long answer. Use when an answer is going to be long, when the user says they do not understand, asks "как лучше показать", "what's the best way to explain", or when the content is mostly structure, comparison or process.
diagram-first
Answer with a diagram first and only a few sentences of text, when the content is about structure, flow, sequence, state, dependencies or comparison. Use when the user asks to draw, diagram, visualize, show a schema or a map, says "покажи схемой" or "нарисуй", or when a text answer would need more than about 150 words to describe how parts connect.
animated-explainer
Build a step-by-step animated explainer as one offline HTML file - the top rung of Karpathy's format ladder, after text, diagrams and HTML pages. Use only when the user asks for an animation, a video-like or step-by-step explanation, "покажи по шагам", "анимацию", runs /legible:animate, or presses the Анимация button on the session board. Do not build one unasked.
lean
The lean rules and the switch between levels. Use when the user types /lean, asks for another lean level (lite, full, ultra), or asks to turn lean on or off.
lean-review
Review for over-engineering only - what to delete, what the standard library or platform already does, abstractions with one user. A diff by default; the whole repository for an audit. Use when the user asks "is this over-engineered", "what can we delete", "review for bloat", "audit this repo for over-engineering", "find what to simplify", or types /lean-review. A report; it changes nothing.
lean-debt
List every `lean:` shortcut comment in the codebase as one debt ledger, so a deliberate shortcut does not quietly become permanent. Use when the user asks "what did lean defer", "list the shortcuts", "lean debt", "what did we mark to do later", or types /lean-debt. A report; it changes nothing.