.claude/skills/eew-architecture/SKILL.md
EEW(緊急地震速報)機能のアーキテクチャ解説。EEW関連のコード修正、予報電文・警報電文の処理フロー、キャッシュ管理、ソース優先順位の理解に使用。
npx skillsauth add ingen084/kyoshineewvieweringen eew-architectureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
EEW関連のコードを修正・理解する際は以下の手順に従う:
EewControllerの処理フローを追跡し、関連するイベントを確認EewMock.csでテストデータを確認・追加| ファイル | 役割 |
|---------|------|
| src/KyoshinEewViewer/Series/KyoshinMonitor/Services/Eew/EewController.cs | EEW統合管理コントローラ |
| src/KyoshinEewViewer/Series/KyoshinMonitor/Models/Eew.cs | EEWデータモデル |
| src/KyoshinEewViewer/Series/KyoshinMonitor/Controls/EewPanel.axaml | EEW表示UI |
| src/KyoshinEewViewer/Series/KyoshinMonitor/Services/Eew/EewTelegramSubscriber.cs | 電文受信・振り分け |
| src/KyoshinEewViewer/Series/KyoshinMonitor/Services/Eew/SignalNowFileWatcher.cs | SNPファイル監視 |
| src/KyoshinEewViewer/Series/KyoshinMonitor/Models/EewMock.cs | テスト用モックデータ |
EewControllerは2つの独立したキャッシュを管理:
| キャッシュ | 処理メソッド | 電文タイトル |
|-----------|-------------|-------------|
| EewCache | Update() | 緊急地震速報(地震動予報) |
| WarningEewCache | UpdateWarning() | 緊急地震速報(警報) |
重要: 予報電文と警報電文は報数(SerialNo)が別々に管理される。
[予報電文] → EewTelegramSubscriber → EewController.Update() → EewCache
[警報電文] → EewTelegramSubscriber → EewController.UpdateWarning() → WarningEewCache
↓
InvokeEewUpdated() → 両キャッシュをマージ → EewUpdated イベント発火
EewSource enum と優先順位:
詳細なMixEewロジックはreference.mdを参照。
予報電文の新しい報数を追加する場合:
EewTelegramSubscriberで電文を受信EewController.Update()を呼び出しEewCacheに新規エントリ追加または既存を更新InvokeEewUpdated()でイベント発火警報地域を追加表示する場合:
EewWarningAreasモデルを確認(reference.md参照)EewPanel.axamlのバインディングを確認EewController.UpdateWarning()の処理を修正詳細なモデル・イベント仕様はreference.mdを参照
tools
Guide for creating effective Claude Code Agent Skills. Use when users want to create, improve, or troubleshoot Skills that extend Claude's capabilities with specialized workflows, domain expertise, or tool integrations.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------