// Apply or review Obsidian Korean style guide — voice, register, tone, terminology, and surface-specific rules for the ko locale. Use when editing, reviewing, or auditing Korean copy for the Help site, app UI, homepage, or release notes.
| name | obsidian-ko-style |
| description | Apply or review Obsidian Korean style guide — voice, register, tone, terminology, and surface-specific rules for the ko locale. Use when editing, reviewing, or auditing Korean copy for the Help site, app UI, homepage, or release notes. |
Apply the Obsidian Korean style guide to the given content.
Modern, restrained 해요체 across all surfaces. Direct and calm. Friendly, but still unmistakably documentation.
Default endings: 해요 / 이에요 / 예요 / 할 수 있어요 / 하세요
Core rule: Use 해요체, but write it like product documentation, not like a blog post, onboarding coach, or marketing page.
Never mix 해요체 and 합니다체 on the same page unless quoting existing source text.
For the Obsidian Korean Help site, the best default register is:
해요체Not recommended as the site-wide default:
합니다체Think:
| Surface | Register |
|---|---|
| Help site | Restrained 해요체. Neutral explanation. Practical, low-hype, low-drama. |
| App UI | Short labels and concise imperatives. |
| Homepage | Heading fragments or light 해요체. Slightly more expressive, still controlled. |
| Release notes | Neutral informative prose. Slightly warmer than Help, but not salesy. |
| Error messages | Direct and calm. State what happened and what to do next. |
For Help pages, prefer:
For Help pages, avoid:
Avoid sentence endings in headings. Use section labels, not full sentences.
✓ Obsidian이란 / 내 데이터를 직접 관리 / 리본 사용자 지정
✗ 데이터를 직접 소유하고 관리해요
정의: "X는 … 기능이에요."
기능: "…할 수 있어요." / "…를 지원해요."
지시: "…하세요." / "…를 선택하세요."
조건: "…하면 …할 수 있어요."
권장: "…하는 것이 좋아요." / "…를 권장해요."
설명: "…하는 데 도움이 돼요."
Aim for:
Avoid:
Keep fixed: Markdown, Canvas, CSS, API Transliterate: 볼트, 플러그인, 테마, 스니펫, 그래프 뷰, 백링크, 명령 팔레트
Avoid heavy abstractions — prefer plain phrasing:
| Avoid | Prefer |
|---|---|
| 어떻게 시작하냐고요? | 시작하려면 먼저 [[내부 링크]]를 만들어 보세요. |
| 링크는 최우선 시민이에요 | 링크는 Obsidian의 핵심 요소예요 |
| 자신의 두뇌를 맡기고 싶지 않으시죠? | 중요한 지식은 직접 소유하고 관리할 수 있어야 해요. |
| 진정한 힘은 놀라울 정도로… | 노트 사이의 관계를 찾는 데 도움이 돼요 |
| 당연히 모든 사람을 위한 단일 만능 솔루션은 없어요 | 모든 사람에게 맞는 단일 솔루션은 없어요 |
| 독선적이고 조립된 제품 | 정해진 방식을 강요하는 제품 |
| 최고이자 가장 세련된 사고 처리 도구 | Remove superlatives. State the feature or roadmap directly. |
A slightly less literal sentence that reads naturally is almost always the right call.
When clarity and literalness conflict, choose the version that sounds like polished Korean product documentation.
Bootstrap a brand-new locale for the obsidian-help repo from scratch — generating translated filenames, syncing stubs from EN, and running LLM translation. Use this skill whenever the user wants to add a new language to obsidian-help, start a new locale translation, or asks to localize/translate the help docs into a new language.
Sync recent English source changes into an existing obsidian-help locale — creating stubs for new pages, translating untranslated stubs, and retranslating manually flagged files. Use this skill whenever the user wants to update, sync, or refresh an existing locale translation in obsidian-help, catch up a locale with EN changes, or re-translate specific pages.
Publish all active obsidian-help locales (en, ja, pt-br, es, zh, fr) via ob publish. Use this skill whenever the user wants to publish or deploy the help site, push locale changes live, or run ob publish across all locales.
Apply or review Obsidian German style guide — voice, register, tone, terminology, and surface-specific rules for the de locale. Use when editing, reviewing, or auditing German copy for the Help site, app UI, homepage, or release notes.