bahayonghang

Create single-file, self-contained HTML artifacts for complex, visual, comparison-heavy, reviewable, or shareable work outputs. Use this skill when the user asks for an HTML artifact, browser-viewable report, implementation plan, PR/code review report, architecture explainer, design comparison, research briefing, incident report, status dashboard, temporary structured-data editor, mini deck, or design-system specimen. Prefer this skill for long Markdown-like outputs that benefit from navigation, cards, diagrams, filters, copy/export buttons, or annotated diffs. Do not use it for short answers, simple commands, commit messages, tiny patch summaries, or production UI implementation unless the user explicitly asks for a review artifact.

Modify the Beautiful Mermaid live editor itself rather than writing ordinary Mermaid diagrams. Use when the task mentions the Beautiful Mermaid repo, `editor.ts`, generated `editor.html`, config panel/options, themes or dark mode, zoom, PNG/SVG export, clipboard behavior, sample presets, or renderer wiring for the editor. Do not use for generic Mermaid syntax help or normal Markdown Mermaid authoring.

Audit and improve Claude Code CLAUDE.md guidance files, .claude/rules/ path-scoped rules, and companion code_map.md navigation maps. Use when the user asks to check, audit, update, optimize, or fix CLAUDE.md files; mentions nested CLAUDE.md, additive loading, ancestor/descendant loading, path-scoped rules, @import chains, CLAUDE.local.md, claudeMdExcludes, or code_map.md; or says "优化 CLAUDE.md", "审计 CLAUDE.md", "检查嵌套 CLAUDE.md", "Claude Code 项目指导", "生成 code_map (Claude)". Make sure to use this skill whenever the user wants to manage Claude Code memory files at any layer, even if they only mention CLAUDE.md without explicit audit wording.

Audit and improve Codex AGENTS.md guidance files and companion code_map.md navigation maps in repositories. Use when the user asks to check, audit, update, optimize, or fix AGENTS.md files; asks for Codex project guidance maintenance; mentions nested AGENTS.md conflicts, code maps, stale commands, scoped instructions, sandbox or approval boundaries; or says "优化 AGENTS.md", "审计 AGENTS.md", "检查 nested AGENTS.md", "更新 Codex 项目指导", or "生成 code_map.md".

Review a codebase for architectural friction, rank deep-module refactoring opportunities, and draft RFCs for safer interfaces and boundary-test strategies. Use when the user wants to improve architecture, identify refactoring seams, consolidate tightly coupled modules, deepen shallow modules, redesign an interface around a core concept, replace brittle unit tests with boundary tests, or turn an architecture review into an RFC or issue draft. Chinese trigger phrases also apply: 架构改进, 抽象太浅, 模块拆得太碎, 接口太多, 测试钉死实现细节, 想写架构 RFC, 这块代码改一改, 模块边界乱.

Archive root-level planning files (`task_plan.md`, `findings.md`, and `progress.md`) into a timestamped `.plannings/` directory for the current feature. Use when Codex should run `$archive-planning [feature-name]`, close out an active plan, preserve completed planning context, or replace the deprecated Codex prompt workflow with a deterministic skill script.

当用户想要 brainstorm 一个想法、设计 feature 或 spec 时使用。通过对话探索意图与需求，然后将 spec 文档写入 .brainstorm/ 并 STOP。不会自动接 implementation planning 或任何其他技能。

Analyze a repository and current Codex environment, then recommend Codex CLI, Codex App, AGENTS.md, skills, native subagents, plugins, MCP servers, config/hooks, and optional OMX workflow improvements without modifying files. Use when the user asks to optimize Codex workflows, improve Codex setup, recommend Codex automation, configure MCP/plugins/subagents, analyze AGENTS.md scope needs, or says "优化 Codex 流程", "Codex 工作流推荐", "给 Codex 配 MCP", "配置 Codex plugins", or "配置 Codex subagents".

Query, search, and generate grounded outputs from the approved live layer of an Obsidian vault. Use this skill whenever the user asks what approved notes already say, wants grounded answers, ranked local candidates, archived Q&A reuse, publishable artifacts, or static web exports from `wiki/live/`; says "query kb", "kb-search", "archive this answer", "归档这个回答", "复用旧 Q&A", "写成公众号/thread", "对外内容", "一鱼多吃", "问知识库", or "搜索批准层并回答"; or uses Chinese-LLM-Wiki terms such as `综合页`, `output/analyses`, `中文优先分析`, `原文证据摘录`, or `先读 wiki/index.md 再回答`. This is the canonical read-side skill for approved retrieval, candidate ranking, answer archiving/reuse, creator-facing publishing, and static export. Do not use for generic writing, open web research, deterministic rendering, or governance/maintenance work handled by `kb-render` or `kb-review`.

Fixture companion skill for tests.

Fixture companion skill for tests.

Diagnose and route ambiguous, workflow-level review-gated Obsidian vault requests. Use this skill when the user is talking about an Obsidian vault workflow as a whole, asks which lifecycle step should run next, says things like "what should I run first", "which stage am I in", "LLM Wiki", "Karpathy wiki", "Obsidian IDE", "knowledge compiler", "creator knowledge compiler", "personal knowledge base", "second brain", "archive this answer", "归档这个回答", "存回知识库", "复用归档内容", "清理 archive backlog", "先读 wiki/index.md", "这个知识库下一步该做什么", "现在应该初始化/摄取/编译/审校/检索/发布/渲染/体检哪个步骤", or uses Chinese-LLM-Wiki wording such as `中文优先`, `来源页`, `主题页`, `实体页`, `综合页`, `output/analyses`, `output/reports`, `原文证据摘录`, `先读 wiki/index.md 再判断`, or `先判断该做来源页还是综合页` without making the operation explicit. Prefer the operation-specific skills when the user already clearly means init, ingest, compile, review, query, publish, render, or archive maintenance, and only route through this package entry skill when the workflow step is genuinely ambiguous.

Incrementally compile tracked raw captures into reviewable draft knowledge. Use this skill whenever the user says "compile wiki", "compile kb", "sync drafts", "digest these captures", "turn my clips into drafts", "编译wiki", "更新草稿层", "同步草稿", or wants tracked material under `raw/human/**`, `raw/agents/{role}/**`, bootstrap `raw/*.md`, `raw/**/assets/*`, or `raw/**/data/*` turned into reviewable summaries, topics, concepts, entities, and draft indices. This is also the right skill when Chinese-LLM-Wiki wording such as `来源页`, `主题页`, `实体页`, `综合页草稿`, `整理成来源页`, `补主题页`, or `补实体页草稿` clearly means “build draft pages from raw evidence first.” Do not treat `raw/**/papers/*.pdf` as a normal compile trigger: those paper ingests still belong to `paper-workbench`, and `kb-compile` should only surface or defer them.

Register and normalize raw source intake for an Obsidian knowledge base. Use this skill whenever the user says "kb ingest", "ingest sources", "refresh manifest", "register new raw files", "scan raw library", "同步素材清单", "登记新来源", "更新 manifest", or wants `raw/**` captures recorded into `raw/_manifest.yaml` before compile runs. Treat browser-side collection as an upstream companion lane: if the source is still on the web and not in `raw/` yet, use `web-access` or Web Clipper first, then come here. Do not use it for draft generation, review, query, or maintenance once the source registry is already current.

Initialize, migrate, or repair a review-gated Obsidian knowledge base. Use this skill whenever the user says "kb init", "initialize knowledge base", "repair vault", "migrate an old layout", "add draft/live review gate", "set up briefings", "LLM Wiki", "Karpathy wiki", "Obsidian IDE", "knowledge compiler", "personal knowledge base", "second brain", "初始化知识库", "迁移知识库", "修复知识库结构", "中文优先 wiki", "raw/wiki/output 脚手架", "把这个 vault 搭成中文优先 wiki", or wants a fresh vault or legacy-layout vault brought onto the review-gated contract. Do not use it for normal compile, review, query, or maintenance work once the support layer is already healthy.

Render deterministic outward-facing artifacts from approved knowledge. Use this skill whenever the user says "kb render", "render slides", "render report", "make a canvas", "generate chart brief", "生成幻灯片", "生成报告", "输出 canvas", `把已批准主题做成报告`, or clearly wants a deterministic derivative from approved live pages or already-grounded archived answers. This is the separate shipped skill for slides, reports, charts, and canvas outputs. Do not use it for retrieval, grounded Q&A, static web export, governance reports, or maintenance work.

Contract-first workflow skill for building a brand-new deck from topic, brief, notes, website, PDF, white paper, or brand assets. Use this whenever the user wants a full new PPT, slide deck, pitch deck, board pack, teaching deck, policy briefing, thesis defense, or structured presentation from scratch and expects research, argument structure, page planning, style direction, and delivery artifacts instead of ad-hoc slide drafting. Trigger even on requests like "帮我做一套 PPT", "make a presentation", or "create slides" when the intent is a brand-new deck. Also trigger when the user wants to stop early at `outline_only` or `spec_only` as a staged checkpoint inside a full new-deck project. Do not use this for existing deck edits, critique-only requests, template tweaks, single-slide asks, export-only work, or lightweight outline / story-direction requests that explicitly do not want AIPPT contracts, research, page planning, or delivery artifacts.

Route new board briefing, board deck, board update, executive operating review, management update, management review, or operating review requests here before generic AIPPT. Use this whenever the user needs a net-new board-facing presentation with dense evidence, decision points, and dated operating metrics. Do not use this scene pack for all-hands updates, team sync decks, or edits to an existing board template.

Route new company introduction, company overview, corporate overview, corporate profile, business overview, enterprise product intro, or customer-facing "about us / who we are / what we do" deck requests here before falling back to generic AIPPT. Use this whenever the user wants a brand-new company or product-led intro deck for prospects, partners, procurement, or customer conversations. Do not use this scene pack for hiring decks, single customer case-study decks, product launch keynotes, or edits to existing files.

Route new investor pitch, fundraising deck, pitch deck, VC deck, startup deck, seed/Series A deck, or venture-facing narrative requests here before generic AIPPT. Use this whenever the user wants a new fundraising story from scratch and expects market, traction, team, and ask to be structured for investors. Do not use this scene pack for product launch decks, internal sales pitch materials, existing-deck reviews, or non-fundraising presentation work.

Route new policy briefing, policy update, regulatory update deck, regulatory change deck, compliance change summary, legal update deck, or legal/product policy presentation requests here before generic AIPPT. Use this whenever the user wants a new policy interpretation deck with timelines, impacts, risks, and recommended actions. Do not use this scene pack for email memos, FAQ-only outputs, compliance copy polishing, or non-deck legal writing.

Route new teaching deck, lecture slides, classroom lesson deck, training deck, training slides, course slides, or workshop deck requests here before generic AIPPT. Use this whenever the user wants a new instructional deck with learning goals, examples, practice, and comprehension-oriented pacing. Do not use this scene pack for manuals, worksheet-only outputs, research talks, or single-slide classroom assets.

Route new thesis defense, dissertation defense, oral defense, viva, academic defense, or research defense deck requests here before generic AIPPT. Use this whenever the user wants a new defense narrative with research question, gap, method, results, contribution, and limitations. Do not use this scene pack for paper proofreading, research posters, conference talks, or non-defense writing tasks.

Search and cite from local BibTeX/BibLaTeX .bib libraries, including Zotero exports. Use to find, filter, preview, export, or generate LaTeX/Typst citation snippets by topic, author, year, venue, DOI, arXiv ID, keywords, abstract, fields, or compact filters. Do not use for manuscript writing or polishing.

Submission cover-letter assistant for existing LaTeX manuscripts. Use to generate, optimize, align-check, preflight, and journal-fit-check cover letters against paper evidence and target venue framing. Do not use for editing main.tex, full manuscript audit, or bibliography search.

English LaTeX assistant for existing .tex conference or journal papers. Use for compile, venue formatting, bibliography, grammar, logic, abstract/title, figures, tables, pseudocode, related work, research gaps, adaptation, de-AI polish, translation, and submission readiness. Use latex-thesis-zh for Chinese theses and paper-audit for critique.

中文 LaTeX 学位论文助手，面向已有 .tex 硕博论文项目与高校模板。用于编译诊断、GB/T 7714 参考文献、模板/章节结构、术语一致性、逻辑与文献综述、研究空白、摘要标题、三线表和去 AI 味修改。英文会议期刊论文用 latex-paper-en，审稿式总评用 paper-audit。

Reviewer-style audit and submission gate for academic papers in .tex, .typ, or .pdf. Use for peer-review critique, pre-submission readiness, pass/fail gate decisions, blocker triage, revision roadmaps, journal-style reports, or re-audits. Do not use for source editing, sentence polishing, bibliography search, or compile repair.

Typst paper assistant for existing .typ manuscripts in English or Chinese. Use for compile/export diagnosis, venue formatting, BibTeX or Hayagriva checks, grammar, logic, abstract/title, tables, pseudocode, related work, research-gap framing, adaptation, de-AI polish, translation, and submission readiness. Use LaTeX skills for .tex sources.

Academic-first Draw.io figure skill for papers, theses, IEEE-style diagrams, architecture figures, workflows, roadmaps, formulas, and publication-ready visualizations. Use when users ask to draw, redraw, replicate, edit, or export diagrams for academic papers or technical documents. Creates offline .drawio + .spec.yaml + .arch.json bundles, exports SVG locally, uses draw.io Desktop CLI for embedded SVG/PNG/PDF/JPG, supports style presets, self-check review loops, and diagrams.net URL fallback without requiring MCP.

Desktop-first Draw.io diagram creation, editing, replication, and conversion (redraw, remake, 重画, 绘图, 画图, 做个图) with a YAML design system supporting 6 themes. Use when creating visual diagrams, drawings, figures, schematics, charts, system architecture diagrams, network diagrams, flowcharts, UML, ER diagrams, sequence diagrams, state machines, org charts, mind maps, cloud infrastructure diagrams, research workflows, paper figures, IEEE-style diagrams, technical roadmaps, or diagrams containing formulas, equations, LaTeX, AsciiMath, MathJax, inline math, block math, 公式, 行内公式, or 行间公式. Academic-paper requests should classify the figure as architecture, roadmap, or workflow, then deliver the editable offline bundle plus SVG by default. Accepts Mermaid, CSV, and YAML input; convert to drawio from mermaid to drawio or any structured source. Default to offline/local generation with `.drawio` + sidecars; use an optional live backend only when browser or inline refinement is genuinely needed.

当用户在 Claude Code、Codex 或类似 agent 里，想直接查询、提取、整理或安全更新本机已有的 Zotero 内容时，必须使用这个 skill。重点是 Zotero 里的 metadata、notes、tags、attachments、PDF fulltext、outline、annotations、collections、saved searches、feeds 和 reading workspace，而不是教人背 CLI。Rust `zot` CLI 只是执行层。适用于库内搜索、citation key 查询、批注与 PDF 提取、workspace 建立与检索、saved search 保存、附件下载、semantic index/search、Scite 检查、配置排障，以及明确授权的 Zotero Web API 写操作。不要把它用于泛化找论文、普通总结、引用格式教学、或不落到 Zotero / workspace 的 PDF 处理。