liueggy

Generates standalone Markdown reference documentation for any Qt/C++ source files — Qt Widgets classes, Qt Quick backends, Qt/C++ modules, plain C++ utilities, structs, free-function headers, and entry points like main.cpp. Use this skill to document any .h or .cpp file: Qt classes, plain C++ code, utility helpers, or application startup files. Triggers on: "document this class", "write docs for my C++", "document main.cpp", "C++ API docs", "document my Qt app", or whenever C++ or header files are provided and documentation is needed. Works with single files, pasted code, or entire project folders. DO NOT use if the user asks for QDoc format output.

Invoke when the user asks to review, check, audit, or look over Qt5 C++ code — or suggest before committing. Runs deterministic linting (60+ rules) then six parallel deep- analysis agents covering model contracts, ownership, threading, API correctness, error handling, and performance. Reports only high-confidence issues (>80/100) with structured mitigations. Read-only — never modifies code.

Extract component metadata from a Figma design system and generate production-ready QML controls. Use this skill whenever someone wants to turn Figma components into QML files — whether they say "generate components from Figma", "create QML controls based on a design system", "convert Figma components to QML", "build the component library", "extract button/input/checkbox from Figma", or anything similar. Requires design-tokens.json and QML design system singletons to already exist (from the token extraction skill). Uses Figma MCP to inspect components one at a time and maps variants, states, sizing, and token usage to idiomatic Qt Quick Controls 2 patterns. Trigger this skill at the component generation step of any QML design-system workflow.

Extract design tokens, text styles, and variables from a Figma design system and produce a design-tokens.json plus ready-to-use QML singletons. Use this skill whenever someone wants to pull their design system out of Figma — whether they say "export tokens from Figma", "get design tokens", "set up my design system", "read our Figma design system", "get Figma variables into QML", "pull our color palette from Figma", "import design tokens", "extract colors/typography/spacing from Figma", or similar. Trigger this skill at the start of any design-system workflow that involves a Figma source.

Use to generate or update Qt5 projects — both qmake (.pro) and CMake. Covers project setup, qmake .pro files, and Qt5 CMake API. When the user does not specify a build system, prefer qmake as the default for Qt5.

Generates standalone Markdown reference documentation for QML components and applications. Use this skill whenever you want to document QML files, create API reference docs for a QML component or module, document a Qt Quick application, or produce developer-facing documentation from .qml source code. Triggers on: "document this QML", "write docs for my QML", "create reference docs", "document QML component", "QML API docs", "document my Qt Quick component", "document my Qt app", or any time one or more .qml files are provided and documentation is needed. Works with single files, pasted code, or entire project folders. DO NOT use if the user asks for QDoc format output.

Use when the user is investigating QML / Qt Quick performance — both vague complaints ("the UI feels laggy", "this is slow", "frames are dropping", "the app stutters") and explicit asks to profile, find hotspots, or optimize bindings, signals, or rendering. Runs qmlprofiler on a 2D QML application, parses the .qtd trace, and analyzes hotspots against the source with frame-time, memory, and pixmap-cache summaries. Does NOT cover Qt Quick 3D (not available in Qt5).

Invoke when the user asks to review, check, audit, or look over Qt5 QML code -- or suggest before committing. Runs deterministic linting (47+ rules) then six parallel deep- analysis agents covering bindings, layout, loaders, delegates, states, and performance. Designed for Qt5 QML code. Reports only high-confidence issues (>80/100) with structured mitigations. Read-only -- never modifies code.

当用户提到知乎、知乎发文、知乎发布文章、知乎草稿、知乎编辑文章、知乎登录后操作、知乎API、知乎直连发布、知乎草稿工具、知乎内容同步、绕过知乎编辑器、知乎批量发布、帮我发一篇知乎测试文章、帮我在知乎上操作网页时使用。

当用户提到 CSDN、CSDN 博客、CSDN 发文、CSDN 发布文章、CSDN 编辑文章、CSDN 登录后操作、查看 CSDN 阅读历史、CSDN 消息、CSDN 创作中心、CSDN 标签、CSDN 草稿、CSDN 私信、CSDN 管理博文、CSDN 搜索文章、阅读 CSDN 文章、总结 CSDN 文章、整理笔记、提取知识点、根据 CSDN 内容做学习笔记、帮我在 CSDN 上操作网页时使用。

当用户提到 Obsidian、Obsidian 笔记、知识库、创建笔记、管理笔记、整理笔记、批量更新、笔记模板、学习笔记、项目文档、知识库分析、笔记结构、自动生成笔记、Obsidian 自动化、笔记维护、标签管理、分类整理、链接修复、资产处理、知识库统计、网页摘抄、Obsidian Canvas、.canvas、Obsidian Bases、.base、wikilink、callout、embed、frontmatter 时使用此技能。专门用于管理和扩展用户的 Obsidian 知识库，实现个性化写作、规范化 Markdown、网页内容清洗摘抄与画布文件支持。

当用户提到 ROS、ROS1、ROS2、catkin、colcon、roscore、topic、service、action、launch、rviz、gazebo、tf、urdf、xacro、slam、nav2、机器人中间件、机器人节点通信、传感器驱动、导航栈、机械臂 ROS 集成，或希望学习、搭建、调试、解释、编写、运行 ROS/ROS 2 工程时使用此技能。也用于创建最小示例节点、工作空间、launch 文件、消息接口示例、诊断通信问题、解释架构与数据流、比较 ROS1 与 ROS2、以及为具体机器人项目设计软件结构。

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

当用户提到 STM32、STM32CubeMX、CubeIDE、HAL、LL、寄存器、GPIO、UART、USART、SPI、I2C、ADC、DAC、TIM、PWM、DMA、EXTI、中断、NVIC、SysTick、RTC、看门狗、Flash、Bootloader、FreeRTOS、裸机、嵌入式 C、外设驱动、板级支持包、时钟树、HardFault、栈溢出、串口收发异常、DMA 不工作、中断不进入、移植、驱动分层、状态机、协议解析、低功耗、调试与排障时使用此技能。也用于生成 STM32 外设初始化模板、驱动框架、模块化代码结构、排障清单、代码审查要点，以及解释 MCU 外设与寄存器工作机制。

用于演示自定义 Minis/OpenMini 技能目录的最小示例。

Use when working on the Firefly mecanum-wheel ROS Noetic robot project, including STM32 serial protocol, eggy_base_driver, bringup, URDF/TF, IMU, odom, battery, and launch/debug workflow.

专用于用户的 Firefly 控制主板开发/运维/调试。触发场景：用户提到 Firefly 板子、控制主板、192.168.31.50、板子 SSH/ADB、ROS Noetic、mihomo 科学上网、GPIO/I2C/UART/串口调试、外设控制、板子开发环境、在板子上安装软件/跑程序/查日志/修复环境时使用。该技能包含板子的连接方式、已安装工具、硬件接口、敏感 GPIO、ROS/mihomo 配置和推荐操作流程。