메뉴
Quality principles for clear, readable prose. Combines Excellent Writing (15 principles for density), Plain Language (active voice, short sentences), and Information Mapping (scannability, chunking). Use during drafting and editing for maximum clarity.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | clear-writing |
| description | Quality principles for clear, readable prose. Combines Excellent Writing (15 principles for density), Plain Language (active voice, short sentences), and Information Mapping (scannability, chunking). Use during drafting and editing for maximum clarity. |
Three complementary approaches to writing that readers understand immediately.
Core: Less is more. Every word earns its place.
| Principle | Rule | Example |
|---|---|---|
| No filler | Remove empty words | "really important" -> "critical" |
| Info density | Every sentence adds new info | No repetition |
| Economy | Shorter words win | "utilize" -> "use" |
| One example | If one makes the point, stop | Don't over-prove |
| Direct statements | State what things do, not that they're important | "X enables..." not "X is important because..." |
| Start with meat | Lead sections with specifics | No "let me explain why this matters" |
Cut these phrases:
Core: Readers understand immediately - no rereading required.
| Weak | Strong |
|---|---|
| utilize | use |
| facilitate | enable |
| make a decision | decide |
| perform analysis | analyze |
| advance planning | planning |
Core: Optimize for how humans actually read (F-pattern, 5-9 chunk limit).
| Content Type | Paragraph Length | Heading Frequency |
|---|---|---|
| Website | 2-4 sentences | Every 3-4 paragraphs |
| Documentation | 4-6 sentences | Every 5-6 paragraphs |
| Books | 5-8 sentences | Section-based |
Before publishing, verify:
Structured Writing -> What to say and in what order
Clear Writing -> How to say it readably
Apply clear writing principles AFTER structure is set.
@import ./content.md (full principles with examples)
This skill should be used when the user asks to "housekeep", "sweep stray transition dirs", "clean up agent-infra debris", "find misplaced .workspace or .claude dirs", or when auditing project trees for the class of debris caused by hooks writing to the wrong project root (nested repos, worker-pool worktrees, stub-only session files, doubled path prefixes). Do NOT use for general project cleanup (see `/system:cleanup`) or for memory garbage collection (see `/memory-gc`).
Write clear, impactful website content for scanners. Use when writing landing pages, service descriptions, CTAs, or above-the-fold content. Covers the 50% test, sentence surgery, power words, page-type guidelines, mobile-first brevity, and techniques for reducing wordiness while maintaining impact.
Match content to what users actually want when they search. Use when creating website pages, blog posts, or any content for search engines. Covers 4 intent types (informational, navigational, transactional, commercial investigation), SERP analysis, query modifiers, and buyer journey mapping.
Technical SEO writing techniques for web content. Use when writing website pages, landing pages, service descriptions, or blog posts for organic search traffic. Covers keyword placement, meta descriptions, heading hierarchy, E-E-A-T principles, internal linking, long-tail keywords, schema markup, and measuring SEO success.
Complete D2 language reference for creating diagrams. Covers shapes, connections, containers, special types (SQL tables, sequences), icons, styling, and advanced features. Use for all D2 diagram generation tasks.
Clarity and simplicity principles for effective diagrams. Focus on essential elements, minimize visual noise, maintain consistency, and use single abstraction levels. Ensures diagrams communicate clearly without clutter.