What problem does it solve? Porting features between two desktop codebases by comparing filenames alone produces false positives, because modules get renamed, consolidated, or restructured. This Skill provides a verified audit methodology and implementation patterns for porting Hermes desktop features into Anakot Agent Desktop without duplicating existing functionality. ## Core Features & Use Cases - Filesystem-First Verification Workflow: A mandatory multi-step process (filename diff, grep for symbols, check renamed paths, check consolidated modules, check inline stores) before marking any feature as missing. - Pattern Library: Six reusable implementation patterns covering config-backed features, Electron IPC features, panel ports, full-stack features, store-first components, and component verification. - Settings Router Wiring Checklist: A complete checklist for adding new settings views, including SETTINGS_VIEWS registration, sidebar nav items, view routing, and i18n keys. - Use Case: When a gap analysis claims a component like confirm-host.tsx is missing from the target codebase, use this Skill's grep-verification workflow to confirm whether it already exists under a different path before writing new code. ## Quick Start Use this skill to verify which Hermes desktop features are genuinely missing from Anakot Agent Desktop and implement them following the established store, lib, and component patterns.
