Loading...
Loading...
Found 52 Skills
Draft or update architecture documents under `easysdd/architecture/` — describe what a subsystem/module looks like currently, how it is divided, and how external interfaces operate, to provide pre-positioning input for subsequent feature-design. Information sources include code + user materials (oral accounts, scattered documents, compound deposits, existing decisions), and the output can be reverse-validated by anchoring to specific `file:line`. Two modes: new (draft a new architecture document from scratch), update (refresh an existing document based on the latest code status and new user materials). Single-target rule — only modify one document at a time. Trigger scenarios: user says "fill in an architecture doc", "draft an architecture document", "update the architecture directory", "write down the structure of this module", or when it is found that "something that should be in the architecture is missing" during the feature-design / feature-acceptance phase.
Write/refactor the NSFC main text section (II) Research Content, and synchronously organize the Characteristics and Innovations and Three-Year Annual Research Plan, outputting three extraTex files that can be directly applied to LaTeX templates. Suitable for scenarios where users need to write/revise research content, research objectives, key scientific issues, technical routes, innovation points, three-year plans/milestones, etc.
This skill should be used when the user wants to generate Chinese patent application forms (专利申请表), or mentions "patents", "inventions", "专利", "申请表", or wants to protect technical innovations. It automatically searches prior art via SerpAPI before drafting.
Automatically generate HarmonyOS design documents including architecture design documents and functional design documents based on PRD documents. It analyzes the existing code structure of OpenHarmony before generation to ensure compatibility with the current architecture. Chapter 2 of the architecture design document must be Competitor Solution Analysis, which should be placed after the Requirement Background. Applicable to user requests: (1) Generate architecture design document, (2) Generate functional design document, (3) Generate design document from PRD, (4) Create system architecture design, (5) Write functional specification, (6) Analyze OH code structure. Keywords: architecture design, functional design, design doc, competitor solution analysis, OpenHarmony code analysis, architecture design, functional design, design document generation, OH code analysis, analyze codebase, competitor analysis
Generate and update structured documentation from project data sources. Supports initial generation and modification of existing documents. Use this skill when users request creating, generating, updating, or modifying documentation.
Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"
Generate various legal service documents (litigation plans, consultation reports, non-litigation plans, proposals, communication reports, etc.) based on case materials or communication records. This skill shall be used when users need to organize case materials, consultation records or communication content into professional legal documents.
Generate LaTeX exam cheatsheets from course materials (PDF/PPTX/MD/images). Use when user says "generate cheatsheet", "make a cheat sheet", "create exam reference sheet", "condense notes", or has course materials to turn into a compact LaTeX review sheet for exams.
Convert Markdown files and strings into DOCX documents using @mohtasham/md-to-docx. Use when a user needs Markdown to Word conversion, CLI-based file conversion, options-driven styling/alignment/font family, TOC/page break handling, underline/strikethrough formatting, multi-section documents with per-section headers/footers, or programmatic conversion in Node/browser code.
Generate comprehensive monthly knowledge management reports by analyzing team Yuque activity data including group stats, member contributions, knowledge base health, and document trends. For team use — requires team Token with statistic:read permission.
Generate a resumable handoff document from an in-progress conversation, review, debugging session, or investigation. Dispatches co-located subagents to extract original instructions and Q&A context, capture evidence-backed insights, optionally validate claims from tracking files, and assemble a cold-start-ready handoff file plus structured working artifacts. Use when the user says "create a handoff doc", "save this for later", "document what we found", "update the resumption file", or wants a fresh agent to resume later without relying on chat history.
Analyze requirements during the functional design and problem diagnosis stages to develop executable solutions, and output user-facing and AI-facing action documents separately.