geo-software-ux-design SKILL.md skillA
geo-software-ux-design from yuiseki/geo-software-factory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yuiseki/geo-software-factory/geo-software-ux-design@git:20261113.0d9593dPins git:20261113.0d9593d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yuiseki/geo-software-factory
- Path
.agents/skills/geo-software-ux-design/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261113.0d9593d, committed Nov 13, 2026
- First version recorded
- Nov 12, 2026
- Size
- 11,919 bytes
- Repository stars
- 12
- License
- Apache-2.0
地図プロダクトの UI と UX を設計する。マーカーが多すぎるとき (クラスタリング、ヒートマップ、ベクトルタイル化)、検索と入力補完、現在地、モバイルの操作 (スクロールの奪い合い、ジェスチャ)、初期表示の速さ、配色と注記、アクセシビリティ (スクリーンリーダー、キーボード、色覚) を扱う。「マーカーが多くて重い」「地図の検索 UI」「スマホで地図が操作しにくい」「地図のアクセシビリティ」と言われたら使う。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# geo-software-ux-design 地図プロダクトの画面と操作を設計する。地図が画面の中で担う役割を先に決め、地物の量、検索、現在地、端末、読み込み、配色、アクセシビリティの順に、手段を 1 つずつ選んで理由を残す。手段の事実と出典は下の表の reference にある。どのライブラリで描くかは geo-software-library で選び、このスキルはそのライブラリで画面をどう作るかを決める。 | reference | 読むとき | 中身 | |---|---|---| | [many-features](references/many-features.md) | 表示する地物が数百件を超えるとき | クラスタリング、ヒートマップ、ベクトルタイル化、集計の使い分けと、件数ごとの実測 | | [search-ux](references/search-ux.md) | 地図に検索をつけるとき | 検索ボックス、入力補完、日本語の入力 (IME) と住所の表記ゆれ、結果と地図の連動 | | [geolocation-ux](references/geolocation-ux.md) | 現在地を使うとき | 許可を求める時機、誤差の円、追従、許可が無いときの代わり | | [mobile-interaction](references/mobile-interaction.md) | スマートフォンで使うとき、地図をページに埋め込むとき | スクロールの奪い合い (cooperative gestures)、タッチの的の大きさ、一覧と地図の切り替え | | [initial-load](references/initial-load.md) | 初期表示を速くしたいとき、地図が主役でないページのとき | 遅延読み込み、日本語のグリフ、場所の確保 (CLS)、静的な画像での代替 | | [cartography](references/cartography.md) | 配色や注記を決めるとき、主題図を描くとき | 注記の読みやすさ、色覚の多様性に配慮した配色、コロプレスの階級区分 | | [feedback-from-builds](references/feedback-from-builds.md) | 画面の部品と導線を決めるとき、夜に見た目で迷ったとき | 作ったものへの本人の指摘を一般化した既定: 画面の主役と導線、地図の表示範囲、書けない人への見せ方、常時表示の画面、位置を示す 2 つの縮尺の地図、狭い場所の文字 | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_es2fh3mzftdjprhk/10b408053d03ce69c6c9092817d82109855a7288c73494f9528f9b467d724e16.json
Then /plugin install geo-software-ux-design@markdownregistry-es2fh3mzftdjprhk in Claude Code. It installs git:20261113.0d9593d, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add yuiseki/geo-software-factory/geo-software-ux-design@sha256:10b408053d03ce69The line at the top of this page pins the label git:20261113.0d9593d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_es2fh3mzftdjprhk)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in yuiseki/geo-software-factory/geo-software-ux-design since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of geo-software-ux-design from somewhere else? Ask it: where did my geo-software-ux-design come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Nov 12, 2026 and Nov 13, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.0d9593d latest | 2026-11-13 | 0d9593d | 11,919 B | A | view · diff |
| git:20261112.632dcee | 2026-11-12 | 632dcee | 11,672 B | A | view · diff |
| git:20261112.173df88 | 2026-11-12 | 173df88 | 11,574 B | A | view · diff |
| git:20261112.c078140 | 2026-11-12 | c078140 | 11,272 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/geo-software-ux-design/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11919 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yuiseki/geo-software-factory · 12 stars · license Apache-2.0 · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_es2fh3mzftdjprhk GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-ux-design GET https://markdownregistry.com/api/v1/blob/10b408053d03ce69c6c9092817d82109855a7288c73494f9528f9b467d724e16
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from yuiseki/geo-software-factory
Every file in yuiseki/geo-software-factory
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.