메뉴
Write concise, human-first prose with one sentence per source line. Use whenever generating or substantially rewriting Markdown, AsciiDoc, plain-text documentation, release notes, user-facing explanations, or other hand-maintained prose.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Devolutions/IronRDP --skill prose-writer명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles. Use whenever composing, reviewing, correcting, or checking a commit or PR title, especially when several crates or product surfaces intersect.
Write or substantially revise a Rust crate's README.md as a concise, user-facing design document. Use whenever creating a crate README, documenting a planned crate, or defining a crate's purpose, role, or interface before implementation.
Create and integrate a new Rust crate in the IronRDP workspace. Use whenever adding, scaffolding, or initializing a crate under crates/, including requests that mention cargo new, a new library package, or registering a crate in the architecture.
| name | prose-writer |
| description | Write concise, human-first prose with one sentence per source line. Use whenever generating or substantially rewriting Markdown, AsciiDoc, plain-text documentation, release notes, user-facing explanations, or other hand-maintained prose. |
Lead with what the reader needs to know or do. Use direct sentences, concrete verbs, familiar words, and the shortest phrasing that preserves meaning. Remove throat-clearing, repetition, inflated wording, and details already clear from context. Keep each paragraph focused on one idea and order ideas by reader need rather than implementation history. Preserve necessary nuance, technical terms, warnings, and the document's established voice.
In source formats where newlines render as spaces, start each sentence on its own line and do not hard-wrap a sentence. Do not apply that convention to code blocks, tables, headings, link definitions, generated files, or formats where line breaks affect rendering.
Write the requested prose directly instead of discussing these rules unless the user asks. Prefer no net word-count growth when rewriting existing prose without adding requested information. Accept small growth only when it materially improves clarity without duplicating information. Treat source line breaks as formatting, not justification for growth. Before finishing, reread from the reader's perspective and remove anything that does not help them understand or act.