Total 30,538 skills, Documentation & Writing has 1017 skills
Showing 12 of 1017 skills
고유한 저자 페르소나를 구성하기 위한 특성 DNA 라이브러리. 목소리 패턴(격식체, 대화체, 서사체, 기술체), 전문성 영역(아키텍처, 구현, 산업, 교육), 관점 스타일(분석적, 경험적, 비판적, 비전적), 어조 특성(권위적, 공감적, 도발적, 양육적)을 포함한다. 페르소나를 정의하거나 커스터마이징할 때, 저자 특성을 이해할 때, 콘텐츠 전반에 일관된 특성을 적용할 때 사용한다.
快速拉齐受众、目的、语气和 CTA 的邮件写作 SOP，覆盖新建邮件与回复线程两种常见场景。
Write Press Release / FAQ documents. Use when proposing new products or features using Amazon's working backwards method. Covers PR/FAQ format.
Provides templates, standards, and best practices for writing clear, comprehensive technical documentation
Publish documentation and books with GitBook including spaces, collections, variants, Git sync, collaboration, and API integration
Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.
Style guide templates for content creation. Used by /majestic:style-guide:new command.
Run /check-docs, then fix the highest priority documentation issue. Creates one fix per invocation. Invoke again for next issue. Use /log-doc-issues to create issues without fixing.
Run /check-docs, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-docs instead if you want to fix issues immediately.
Automatically search, crawl, and rewrite technical content to generate Chinese popular science articles suitable for WeChat Official Accounts. It covers AI large models, GitHub open-source tools, and technical topics. Use this when users say 'Write an article about XXX', 'Help me research XXX', or 'Generate an official account article'.
Produces executive-quality strategic documents in The Economist/HBR style. Use when writing strategy memos, market analysis, business cases, customer research reports, or any document for Product, Design, and Business leaders. Customer-led, evidence-based, narrative-driven.
Build comprehensive ARCHITECTURE.md files for any repository following matklad's canonical guidelines. This skill should be used when creating codebase documentation that serves as a map for developers and AI agents, auditing existing repos for architectural understanding, or when users ask to 'document the architecture', 'create an architecture.md', or 'map this codebase'. Produces bird's eye views, ASCII/Mermaid diagrams, codemaps, invariants, and layer boundaries.