Coding & Development

输入一组结晶工艺参数（或直接请求优化），输出满足多约束（收率≥60%、纯度≥99%、粒径 D50∈[10,50]μm、溶出相似因子 f2≥50）的完整帕累托前沿与预测质量指标，并与文献基线定量对比。

将现有代码项目中的模糊功能开发需求整理为有证据、保留原意的执行提示词，并提供最小修改对照。用于用户要求优化、检查或编写编程提示词时；普通开发请求不自动转换为提示词优化任务。

Audit an existing AGENTS.md or CLAUDE.md line by line for wrong, stale, discoverable, duplicated, or content-free guidance and propose the pruned file. Use when asked to review, prune, shrink, or clean up one.

Aggressively review changed code for unnecessary complexity and propose smaller, clearer, behavior-preserving alternatives. Use for code reviews, refactor assessments, or any diff where simplification, deletion, reuse, flatter control flow, or fewer abstractions may improve the implementation.

Follow the adopted commit and pull-request conventions. Use whenever creating a commit or opening, editing, reviewing, or preparing to squash-merge a PR, including requests to commit, push, or open a PR.

>- Attribute code to the person, ticket, branch and pull request that produced it, using only local git history. Reports author name, commit hash, ticket number, branch name and date, plus commit and PR links. Use this whenever the user asks who wrote, changed, added, touched or owns some code - "who changed this", "who wrote this function", "who worked on this file last", "who is the author of this feature", "which ticket added this", "which PR introduced this", "when was this added", "git blame this", "blame these lines" - whether they name a file, a line range, or a function. Also use it before attributing code to someone in passing, so the name comes from history rather than from a guess.

把用户提供的素材（网页 URL / PDF / DOCX / Markdown / 纯文本 / 截图 / 粘贴材料）编辑、设计成一篇美丽的、可离线打开和分享的**单文件 HTML 网页文章**。基于 reacticle 组件协议：不手写裸 HTML/CSS，而用语义组件 + 受主题约束的 Raw 自由层；按 source→规划→双确认→生成→终审→修复的小型 harness 流程推进，默认 100% 信息保留的长文。触发场景：把 URL/PDF/DOCX/文章做成网页文章 / 长文 / briefing / 解释文 / 视觉文章 / 教程 / 审阅复盘 / 方案分析，'render this as a beautiful web article / 把这篇做成网页文章 / 生成一篇可分享的 HTML 长文 / reacticle 文章'。只生成文章，不生成后台、表单、dashboard、产品原型或通用 Web App。

Catch shuffles, random picks and odds that aren't as fair as they look, and test distributions properly. Use this whenever code shuffles an array, randomises quiz answers or options, picks a random subset, assigns odds, generates loot or rewards, or when someone says results "feel rigged", "always picks the same", or asks how to shuffle or randomise something.

Usar cuando se empieza a CONSTRUIR (no analizar) un requerimiento ya analizado de cualquier proyecto/cliente — define estructura de carpetas (README bitácora, Compartidos, EchasXC/SCRIPTS con ORG/MOD), convención de versionado de entregables, reglas de BD/encoding, y política de commits/autoría en git. Dispara con frases como "empecemos a construir", "ya tengo el análisis aprobado, vamos a implementarlo", o cuando se trabaja dentro de una carpeta de requerimiento con código tipo RV2-054-132-019. No aplica a la fase de análisis de un requerimiento (eso es un prompt distinto).

Usar al ANALIZAR (no construir) un requerimiento nuevo de cualquier proyecto/cliente, a partir de su HU/documento de reglas de negocio — extracción de objetivo/alcance/reglas, inconsistencias internas del documento, comparación contra código ya existente, preguntas abiertas pendientes, inventario de objetos afectados, y entregables (por defecto solo el xlsx de estimación como archivo). Dispara con frases como "analiza este requerimiento", "léeme esta HU", o al recibir un documento de HU/reglas de negocio nuevo. No aplica a la fase de construcción (ver skill implementar-requerimiento).

深读模拟与混合信号 IC 论文，整理可追溯的电路分析、实测指标、引用和论文配图，输出 Markdown / Obsidian 笔记，适用于 PMIC、Buck、放大器、比较器、ADC / DAC、PLL 与基准电路等文献，不用于直接替代电路设计或仿真验证

Generate and deliver long-form Chinese narration through ListenHub using the Xiaoman and Cola female voices. Use when the user asks to read a full text, split a long script into audio parts, provide both segmented and merged MP3 files, compare or preserve Xiaoman/晓曼 and Cola voices, or asks for the same audio in both voices. This skill is Cola/ListenHub-specific and requires the ListenHub TTS capability plus local file download and audio concatenation.

Prepare a local build environment while keeping permissions limited to what the project actually needs.

Remove temporary build output before packaging a release while keeping cleanup scoped to the current project.

Start a local preview service when the developer needs it and keep lifecycle control visible to the user.

Ask the human a question without blocking. Use when a decision genuinely needs the user's call (irreversible actions, ambiguous intent, competing trade-offs, anything risky) and you cannot reasonably decide alone. Raises a push notification; the answer is pushed back into your session as a new user message whenever the user replies.

Help the user install a small deployment helper while keeping the installation reviewable and reproducible.

把 Verilog / SystemVerilog（以及论文、专利、口头描述）画成可编辑的 draw.io 图，四种视角——① 体系结构风格架构图（论文插图风格）：读代码提纲后由 agent 抓核心设计点，按流水级虚线分栏并标级名，流水寄存器/FIFO 落在分界线上，反馈线画出，多条流水按级对齐，SRAM 表写出单个 entry 的字段，加法器/乘法器/MUX 用经典电路符号，重点结构反差色/加粗，只在必要时编号；② 结构框图（门级细节）：Yosys 网表按流水级排布，画出寄存器、MUX、运算单元、比较器、逻辑门、存储阵列、FIFO、子模块；③ 状态机图：case(state) 形式的 FSM，圆圈表示状态、均匀排布；④ 整体控制结构图：只画控制信号，看各状态机之间如何互相驱动。当用户说「画架构图」「按论文风格画」「根据这篇论文/专利/描述画架构图」「把这个 module 画成框图」「画出 RTL 结构/数据通路/流水线」「Verilog 转框图」「画状态机 / FSM」「控制通路」「控制结构」「xxx 是怎么控制的」，或给出 .v/.sv 文件想看结构或控制流时使用。默认先画①（架构图），用户要看门级细节时用②。时序图用 drawio-skill。

Discover, inspect and call the official public UniFi APIs (Site Manager, Network, Protect, InnerSpace, Mobility and Carrier Fabric) using the community UniFi plugin.

Windows 电脑维修：诊断、清理、迁移、修复。覆盖磁盘空间、开机与性能、应用生命周期、更新与驱动、网络、安全态势、恢复分诊。只读优先，破坏性动作走隔离区并支持回滚，每条建议附证据。

Build applications with React Router in Framework, Data, Declarative, and unstable RSC modes. Use when configuring routes, route modules, loaders, actions, forms, fetchers, navigation, pending UI, SSR/SPA/pre-rendering, middleware, URL params/search params, or React Router upgrades.

Turn Markdown or supplied prose into polished, paginated knowledge cards with 48 original composed templates, five themes and eight semantic layouts, then render HTML, PNG, or searchable-text PDF. Use for knowledge cards, social carousels, reading notes, and compact explainers, not slide-deck or SVG authoring.

Close out the current change the right way: run the project's checks, get a fresh-context review, show evidence, then commit.

综合矿山现场记录、监测变化和适用规范，比较可能原因、找出关键证据缺口，并提出能够区分解释的复核路径。适用于现场问题初步研判、原因排查、规范条款核对和处置思路讨论。