Total 50,327 skills, Documentation & Writing has 1450 skills
Showing 12 of 1450 skills
Writing clear, discoverable software documentation following the Eight Rules and Diataxis framework. Use when creating README files, API docs, tutorials, how-to guides, or any project documentation. Automatically enforces docs/ location, linking requirements, and runnable examples.
Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.
Solo(단일 페르소나), Crew(다중 페르소나), Adaptive(컨텍스트 전환) 모드를 위한 글쓰기 프로토콜. 섹션 매핑과 페르소나 조율 전략을 정의한다. 콘텐츠 생성 워크플로우를 결정하거나 다중 페르소나 콘텐츠를 조율할 때 사용한다.
Use when changes are ready to ship and you need to communicate what changed, who it affects, and any required actions without exposing internal-only details.
Author, refactor, and troubleshoot Typst slide decks built with Touying
Guides PRD, ADR, Design Doc, and Work Plan creation with templates and decision matrix.
Create or update repository README.md files with concise, human-skimmable structure and verified metadata. Use when writing or refreshing README content, adding or correcting badges, documenting stack and deployment/services, and explicitly reporting testing coverage (unit, integration, e2e api, e2e web) plus CI execution status.
Persistent decision log that creates a read-write feedback loop: read previous decisions before starting work, respect or supersede them, and write new Y-statement records as you go. Activates during any task involving architectural, structural, or design decisions - choosing libraries, designing schemas, creating modules, making tradeoffs, selecting patterns. Also activates when DECISIONS.md already exists in the project. Do NOT activate for trivial changes like typos, renames, or formatting.
Write unambiguous specifications using EARS (Easy Approach to Requirements Syntax) patterns. Provides 6 sentence templates that eliminate ambiguity: Ubiquitous, Event-driven, State-driven, Unwanted behavior, Optional feature, and Complex. Use when: "EARS", "specification writing", "write specs", "仕様を書く", "EARS記法", "仕様を明確化", "requirements specification", "unambiguous specification".
Edit existing text to remove AI-generated writing patterns. Detects and fixes: inflated symbolism, promotional language, em dash overuse, rule of three, AI vocabulary, negative parallelisms, conjunctive phrases. USE WHEN: "humanise this", "remove AI patterns", "make this sound natural". NOT for creating new narrative content — use story-explanation for that.
Chapter 5 (기타 참고자료) 작성 가이드 - 템플릿 및 요구사항 통합
Review and edit copy for grammar, style, and clarity. Works with project style guides or uses sensible defaults. Use when reviewing marketing copy, blog posts, documentation, emails, or any business writing that needs polish.