Total 52,056 skills, Documentation & Writing has 1488 skills
Showing 12 of 1488 skills
Use only when explicitly asked to write or edit prose. Not for code comments, commit messages, or inline docs.
This skill should be used when the user needs to optimize a resume for software engineering, product management, or technical roles. Use when tailoring a tech resume to emphasize engineering contributions, open-source work, system design, or technical leadership for software and product positions.
Creates comprehensive Technical Design Documents (TDD) following industry standards with mandatory sections, optional sections, and interactive gathering of missing information.
기존 기능의 암묵지를 명세서로 변환하여 as-is Context Pack(주제별 문서 폴더)을 생성하는 스킬. "기능 문서화", "기존 기능 분석", "as-is 정리", "docs/기능별설명 생성" 키워드로 트리거. 신규 기능 Spec이 필요하면 peach-gen-spec을 사용한다.
Logic continuity check for short video scripts. Identify risk points where viewers might swipe away: logical coherence between paragraphs, information density within paragraphs, and fluency of spoken lines. After diagnosis, proactively ask if the user wants marked-up revisions by default. Trigger methods: /dbs-script-flow, /逻辑延续, "Check logic continuity", "Check if the logic is broken", "Help me check if this script flows smoothly", "Where will viewers swipe away"
Use this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, adding sidebar announcement cards, and ensuring everything follows project standards. Use when the user mentions adding changelog entries, documenting new features, creating release notes, or announcing product updates.
API documentation specialist for OpenAPI/Swagger specifications. Use when documenting REST or GraphQL APIs.
Convert video scripts into colloquial expressions more suitable for actual recording, remove formal written language, and enhance naturalness and approachability. Use this skill when the user mentions terms like "video script", "recording", "colloquial", "more natural", "like speaking", or "too formal/written-style".
Strunk's Writing Rules for enhancing document quality. Applicable to all texts intended for human readers: documents, reports, comments, commit messages, etc.
Diagnose what any story needs regardless of its current state. This skill should be used when a writer is stuck, evaluating story problems, when narrative feels broken, or when someone asks 'what's wrong with my story?'. Keywords: story, diagnosis, stuck, narrative, plot, character, worldbuilding, revision.
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
Best practices for writing AI research papers. Use when the project involves writing a research paper in AI field.