Total 50,368 skills, Documentation & Writing has 1451 skills
Showing 12 of 1451 skills
This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items.
TSDoc standards for TypeScript/JavaScript code. Automatically invoked when writing, reviewing, or editing any TSDoc comments, code documentation, or API documentation. (project)
Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles.
Creating an outline of a piece of writing according to a strategy of Ayn Rand art of non-fiction/fiction
Manage RFC-style specifications with validation, and dynamic generation of history, index, and namings files. Use when validating RFC documents, checking taxonomy compliance, or generating specification indices and terminology references.
Use when reviewing React documentation for structure, components, and style compliance
Write a systematic review protocol into `output/PROTOCOL.md` (databases, queries, inclusion/exclusion, time window, extraction fields). **Trigger**: protocol, PRISMA, systematic review, inclusion/exclusion, 检索式, 纳入排除. **Use when**: systematic review pipeline 的起点（C1），需要先锁定 protocol 再开始 screening/extraction。 **Skip if**: 不是做 systematic review（或 protocol 已经锁定且不允许修改）。 **Network**: none. **Guardrail**: protocol 必须包含可执行的检索与筛选规则；需要 HUMAN 签字后才能进入 screening。
Expert knowledge of academic writing standards for peer-reviewed papers, including citation integrity, style compliance, clarity, and scientific writing best practices. Use when reviewing or editing academic manuscripts, papers, or research documentation.
Create Architecture Decision Records (ADR) - Layer 5 artifact documenting architectural decisions with Context-Decision-Consequences format
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications
Build long-form book manuscripts from outline through revision. Use when users ask for chapter-by-chapter outlines, chapter drafts, illustrative stories, research integration, exercises, transitions, case studies, conclusions, or chapter quality reviews.
Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in .ex files.