Total 53,177 skills, Documentation & Writing has 1507 skills
Showing 12 of 1507 skills
Create comprehensive developer onboarding documentation including setup guides, README files, contributing guidelines, and getting started tutorials. Use when onboarding new developers or creating setup documentation.
Write internal communications using company formats. Use when writing status reports, leadership updates, company newsletters, FAQs, incident reports, project updates, or any internal communications.
Act as an active writing partner who contributes content alongside the human writer. Use when the writer wants a collaborator who generates prose, dialogue, alternatives, and builds on their ideas. Applies Story Sense frameworks while actively contributing to the creative work. Contrasts with story-coach which never writes.
Generate technical design documents with proper structure, diagrams, and implementation details. Default language is English unless user requests Chinese.
Writing Assistant - Triggered when users say "I want to write XX", "Help me sort out topics", "How to form a framework", "Help me organize my thoughts". Automatically select the optimal path based on the clarity of the user's viewpoint: take the "Framework → Content" path for clear viewpoints, and take the "Mining → Topic Selection → Framework → Content" path for vague viewpoints.
Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials, or concept explanations.
ASCII architecture diagrams for ADRs via graph-easy. TRIGGERS - ADR diagram, architecture diagram, ASCII diagram.
Convert content generated by general writing Skills into formats and styles suitable for publishing on Zhihu. Zhihu favors content styles with professional depth, clear logic, and well-supported arguments.
Write structured notes for each paper in the core set into `papers/paper_notes.jsonl` (summary/method/results/limitations). **Trigger**: paper notes, structured notes, reading notes, 论文笔记, paper_notes.jsonl. **Use when**: survey 的 evidence 阶段（C3），已有 `papers/core_set.csv`（以及可选 fulltext），需要为后续 claims/citations/writing 准备可引用证据。 **Skip if**: 还没有 core set（先跑 `dedupe-rank`），或你只做极轻量 snapshot 不需要细粒度证据。 **Network**: none. **Guardrail**: 具体可核对（method/metrics/limitations），避免大量重复模板；保持结构化字段而非长 prose。
Creating and maintaining CLAUDE.md project memory files that provide non-obvious codebase context. Use when (1) creating a new CLAUDE.md for a project, (2) adding architectural patterns or design decisions to existing CLAUDE.md, (3) capturing project-specific conventions that aren't obvious from code inspection.
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications