メニュー
Write or edit repository documentation, KDoc, contributor guidance, and PR descriptions. Covers this project's audience, documentation structure, and compiled examples.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/maplibre/maplibre-compose --skill docs-writingコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Update the hand-written MapLibre GL JS bindings after bumping the pinned maplibre-gl version. Use when changing `maplibre-js` in gradle/libs.versions.toml, or when the browser platform breaks against a new MapLibre GL JS release.
Align the MapLibre Compose style API with the published style spec. Use when adding layer or source properties, when a platform implements a property the other does not, after bumping MapLibre GL JS or maplibre-native-ffi, or when working on style-spec parity.
SKILL.md を表示中
| name | docs-writing |
| description | Write or edit repository documentation, KDoc, contributor guidance, and PR descriptions. Covers this project's audience, documentation structure, and compiled examples. |
Write plain technical English for readers who may use English as a second language. Library users usually know Compose but need MapLibre concepts explained. Contributors know Kotlin Multiplatform and need the reasons for project-specific decisions.
Lead with the fact, action, or decision the reader needs. Prefer concrete nouns, direct verbs, and explicit conditions. Avoid promotional language, stock transitions, and metaphors that obscure API behavior. Include the detail the reader needs to understand the subject.
Use paragraphs for explanations, lists for steps or parallel items, and tables for comparisons. Headings use sentence case and identify sections that readers can navigate. Link to existing explanations instead of repeating them.
Pages under docs/src/content/docs/ follow the site's Diátaxis structure:
Choose the page's primary purpose and keep it focused. Introduce the common path on the site and link to API details. Include platform differences, conditions, and implementation details when they affect the reader's decision or ability to complete the task.
Pages import Kotlin examples from // #region blocks in
demo-app/common/src/*/kotlin/org/maplibre/compose/docsnippets/, which compile
with the demo app. Add or update a snippet region instead of embedding an
untested Kotlin example in a page. Title file-oriented code blocks with the
destination filename, such as build.gradle.kts or App.kt.
KDoc defines behavior, parameter semantics, lifecycle requirements, and platform limitations that callers need.
PR descriptions follow .github/PULL_REQUEST_TEMPLATE.md and AI_POLICY.md.
Explain what reviewers need to understand the change, with detail proportional
to its complexity. Report validation accurately.
