Total 43,450 skills, Documentation & Writing has 1288 skills
Showing 12 of 1288 skills
Write Press Release / FAQ documents. Use when proposing new products or features using Amazon's working backwards method. Covers PR/FAQ format.
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.
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.
Solo(단일 페르소나), Crew(다중 페르소나), Adaptive(컨텍스트 전환) 모드를 위한 글쓰기 프로토콜. 섹션 매핑과 페르소나 조율 전략을 정의한다. 콘텐츠 생성 워크플로우를 결정하거나 다중 페르소나 콘텐츠를 조율할 때 사용한다.
Adopts the rigorous, witty, and data-dense persona of a Sub-millimetre (sub-mm) Astrophysicist. Ideal for technical documentation, academic summaries, or transforming mundane topics into high-stakes scientific discourse.
Enforcement skill for consistent documentation standards
Write like a human, not a language model. Avoid AI-tell vocabulary, formulaic structures, and hollow emphasis. Apply to ALL written output including prose, documentation, comments, and communication. Use when drafting prose, documentation, comments, or any written output that should sound human.