clash-doctor
Clash-doctor diagnoses Clash Verge/Mihomo proxy configuration issues and manages routing rules for AI tools like Claude, Codex, Cursor, and Warp. Use it when troubleshooting network connectivity problems, setting up proxy routing configurations, switching between subscription profiles, viewing or cloning Clash settings, and performing connectivity verification through profile inspection and API probing.
git clone --depth 1 https://github.com/majiayu000/spellbook /tmp/clash-doctor && cp -r /tmp/clash-doctor/skills/clash-doctor ~/.claude/skills/clash-doctorSKILL.md
# Clash Verge Diagnostics Inspect Clash Verge or mihomo, manage profile-specific routing, and diagnose connectivity. ## Routing - Confirm the target profile, constraints, requested access path, and done-when signal. - Load `references/full-guide.md` for commands, templates, and diagnosis matrices. - Load `references/local-hub.md` before `hub`, `align`, `roles`, `clone`, `setup-ai`, or `switch`, and whenever the user says a previous sync did not apply. - Keep the change limited to the requested target. ## Safety - Diagnose and align are read-only. Writes require a shown summary and explicit confirmation. - Edit enhancement overlays or the confirmed local-hub YAML. Do not edit raw subscription dumps. - `tun.route-exclude-address` is union-only. `DIRECT` is not a TUN bypass. - Never invent or print node IPs, credentials, subscription UIDs, or machine hostnames. - After an overlay or hub-YAML write, quit and reopen Clash Verge. `PUT /configs` does not re-merge overlays. ## Modes | Argument | Mode | |---|---| | empty or a hostname | diagnose | | `profiles` / `list` / `ls` | list local and remote profiles | | `status` | live kernel, TUN, and selected nodes | | `hub` / `roles` | local-hub topology | | `align` / `sync-check` | read-only multi-machine comparison | | `switch-check` / `health` | pre-switch health | | `clone` / `setup-ai` / `switch` | confirmed profile writes | | `rustdesk` / `bypass` | TUN exclusion for a relay IP | Resolve the named target before `setup-ai`. Apply airport-style enhancement overlays only when that target is `type: remote`; edit the named hub YAML when it is `type: local`. ## Verify - Parse the target YAML after every write. - Query mihomo by trying both Unix sockets and then the configured HTTP controller; fall back on request failure, not socket existence alone. - For routes, `chains[-1]` is the matched group and `chains[0]` is the dialed node. - Report files changed, commands run, evidence, and remaining risk. ## References - `references/full-guide.md` — commands, templates, and diagnosis matrix - `references/local-hub.md` — hub ownership, node roles, alignment, and landmines
Audit AND optimize a CLAUDE.md / AGENTS.md instruction file — score it against the five high-leverage patterns, flag anti-patterns, then apply approved fixes in place. Use when the user says 优化 CLAUDE.md / 优化 AGENTS.md / optimize my agent doc / 帮我改 claudemd, or after an audit when they want the fixes applied (not just reported).
Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.
Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.
Evidence-driven architecture research for understanding real systems and making technical decisions. Use when doing architecture landscape studies, source-backed system archaeology, build-vs-buy or adopt/adapt/build decisions, open-source and commercial comparisons, revisiting an earlier architecture choice, or handling requests such as 架构调研, 架构选型, 竞品架构, 技术尽调, 同类方案, 开源替代, how is X built, and what should we learn from X. Do not use for small mechanical changes, market-only discovery, or detailed design after the technology direction is already fixed.
Ask Grok or Gemini via opencli (browser-session based, no API cost). Use when the user says "问 grok", "问 gemini", "ask grok", "ask gemini", "用 grok 查", "grok 怎么看", "让 gemini 分析", or wants a second opinion from Grok/Gemini without paying API tokens. Routes to opencli which drives the already-logged-in Chrome session.