Total 50,330 skills, Documentation & Writing has 1450 skills
Showing 12 of 1450 skills
Generate reference documentation entry by entry for the public surface of libraries (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental differences from guidedoc: guidedoc teaches you how to use things, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When users say "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are found after feature-acceptance.
Write or update external guide documents for the project —— dev-guide (for contributors / integrators / downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push when feature-acceptance is completed.
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
Polish and elevate MBA thesis/dissertation to the quality of national outstanding thesis. Provides comprehensive improvements in academic language, argument structure, logical rigor, innovation highlights, and formatting. Input: Markdown-formatted thesis text. Output: Polished full text. This service is also triggered when the user mentions terms such as "thesis polishing", "MBA thesis", "outstanding thesis", "thesis polish", "dissertation improvement", "academic polishing".
One-stop skill for the project architecture center — draft new architecture documents, refresh existing architecture documents, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to the latest code status)/ `check` (view only, generate issue list). The `check` mode has three sub-goals: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `easysdd/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down the structure of this module", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when it is found in the feature-design / feature-acceptance / implement phase that an architecture action needs to be performed first before proceeding.
Write or update external guide documents for the project —— dev-guide (for contributors/integrators/downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push at the end of feature-acceptance.
Complete coaching skills for Taiwanese nursing staff to write evidence-based nursing reports (evidence-based reading reports, evidence-based case analyses), designed specifically for the N1–N4 nursing advancement system and the review formats of the Taiwan Nurses Association and Taiwan Evidence-Based Nursing Association. This skill must be triggered when users mention terms such as "evidence-based nursing report", "evidence-based case analysis", "evidence-based reading report", "N2 report", "N3 report", "N4 report", "nursing advancement report", "nursing promotion", "PICO", "5A Steps", "CASP Appraisal", "nursing EBP", "EBN", "evidence-based nursing", "evidence-based care", "evidence level", "literature appraisal", or when any nursing staff asks about promotion writing, transforming clinical problems into evidence-based topics, evidence-based literature search strategies, CASP appraisal forms, Oxford evidence levels, APA 7th edition format, applying evidence-based interventions to cases, challenging nursing routines, dispelling nursing myths, etc. Even if users casually say "I need to write a report", "I want to advance to N3", "Help me find a topic", "Help me set up PICO", "How to appraise this literature", this skill should be actively activated to provide complete structures, sentence patterns, and writing strategies with the highest review pass rate.
Explain code as a scannable blog post
Design and write hands-on tutorials with progressive disclosure, exercises, and troubleshooting sections. Use when creating learning content, workshops, or step-by-step guides.
Use when the user needs to turn a real software engineering / computer science project and an existing thesis draft into a submission-ready undergraduate thesis manuscript. Trigger for requests such as "根据项目把论文改成定稿", "按学校模板排版成最终版", "复制初稿后生成定稿 Word", "为定稿降查重", "根据PaperPass报告降AIGC", "继续在手改初稿上改", "恢复原来的图表和数据库说明", or when academic-paper-strategist has already produced an evidence-backed rewrite plan. Outputs a cleaned manuscript, final DOCX workflow, and a separate rework report.
Synthesize a PRD (Product Requirements Document) for a big new feature. Synthesis (not interview) — uses existing project context and explicit ADRs. Asks before gh issue create. Use when scoping a substantial new feature in PRD shape (e.g., before a sprint).
Generate a self-contained HTML slide deck (SlideDeck + Slides with keyboard nav) from a topic or outline. Use whenever the user asks for "slides", "a deck", "a presentation", a "walkthrough", or a 5+ step recap. Requires the `hyperscribe` skill to be installed (provides the renderer engine).