[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fz8Eki4_jAExgxGAlz0ZSy-jCpVey-ibdU6etrs5j2Zs":3,"$fJU-4tot_gC5fDkujNeoE-cGsdMy5V_KcdUXLuAnTFgw":16,"$fXim9onWYxHhDpSBdDcBQPmFZYcYn9WwXflK0TsR1du8":423},{"slug":4,"title":5,"description":6,"content":7,"content_html":8,"pub_date":9,"tags":10,"draft":15},"network-clash-config","Clash \u002F Mihomo 配置详解：规则、策略组与分流","深入解析 Clash\u002FMihomo 的核心配置结构，包括代理节点、策略组类型、规则优先级、DNS fake-ip 模式，以及一份实用的完整配置模板。","## Clash \u002F Mihomo 是什么\n\n**Clash** 是一个规则驱动的代理客户端内核，**Mihomo**（原 Clash.Meta）是它目前最活跃的分支，支持更多协议和特性。大多数 GUI 客户端（Clash Verge Rev、OpenClash 等）底层跑的都是 Mihomo 内核。\n\n> 注意：原版 Clash 仓库已于 2023 年 11 月删库，目前使用 Mihomo 内核。\n\n---\n\n## 配置文件结构\n\n一份 Clash 配置由以下几个部分组成：\n\n```yaml\n# 基础设置\nport: 7890          # HTTP 代理端口\nsocks-port: 7891    # SOCKS5 代理端口\nmixed-port: 7892    # HTTP + SOCKS5 混合端口（推荐用这个）\nallow-lan: false    # 是否允许局域网连接\nmode: rule          # 代理模式：rule \u002F global \u002F direct\nlog-level: info\n\n# DNS 配置\ndns: ...\n\n# 代理节点\nproxies: ...\n\n# 策略组\nproxy-groups: ...\n\n# 规则\nrules: ...\n```\n\n---\n\n## 代理模式\n\n| 模式 | 行为 |\n|------|------|\n| `rule` | 按规则分流，国内直连，国外走代理（**日常使用**）|\n| `global` | 全部走代理 |\n| `direct` | 全部直连，相当于关闭代理 |\n\n---\n\n## 策略组类型\n\n```yaml\nproxy-groups:\n  # 手动选择节点\n  - name: \"手动选择\"\n    type: select\n    proxies:\n      - \"香港 01\"\n      - \"日本 01\"\n      - DIRECT\n\n  # 自动测速，选延迟最低的\n  - name: \"自动选择\"\n    type: url-test\n    proxies:\n      - \"香港 01\"\n      - \"日本 01\"\n    url: \"https:\u002F\u002Fwww.gstatic.com\u002Fgenerate_204\"\n    interval: 300     # 每 5 分钟测速一次\n    tolerance: 50     # 延迟差在 50ms 内不切换\n\n  # 故障转移：第一个挂了自动换下一个\n  - name: \"故障转移\"\n    type: fallback\n    proxies:\n      - \"香港 01\"\n      - \"日本 01\"\n    url: \"https:\u002F\u002Fwww.gstatic.com\u002Fgenerate_204\"\n    interval: 60\n\n  # 负载均衡：多节点轮流用\n  - name: \"负载均衡\"\n    type: load-balance\n    proxies:\n      - \"香港 01\"\n      - \"香港 02\"\n    strategy: round-robin   # 或 consistent-hashing\n```\n\n---\n\n## 规则类型\n\n规则从上到下匹配，第一条命中则停止：\n\n```yaml\nrules:\n  # 域名完整匹配\n  - DOMAIN,example.com,DIRECT\n\n  # 域名后缀匹配（最常用）\n  - DOMAIN-SUFFIX,google.com,手动选择\n  - DOMAIN-SUFFIX,github.com,手动选择\n\n  # 域名关键词（慎用，容易误匹配）\n  - DOMAIN-KEYWORD,youtube,手动选择\n\n  # IP 段\n  - IP-CIDR,192.168.0.0\u002F16,DIRECT,no-resolve\n  - IP-CIDR,10.0.0.0\u002F8,DIRECT,no-resolve\n\n  # GeoIP 国家码（需要 geoip.dat 数据库）\n  - GEOIP,CN,DIRECT\n  - GEOIP,PRIVATE,DIRECT\n\n  # 规则集（从 URL 加载，减少配置体积）\n  - RULE-SET,reject,REJECT        # 广告拦截\n  - RULE-SET,direct,DIRECT        # 国内直连\n  - RULE-SET,proxy,手动选择       # 需要代理\n\n  # 兜底规则，必须放最后\n  - MATCH,手动选择\n```\n\n---\n\n## DNS 配置\n\nDNS 是 Clash 里最容易踩坑的部分。\n\n### fake-ip 模式（推荐）\n\n```yaml\ndns:\n  enable: true\n  listen: 0.0.0.0:53\n  ipv6: false\n  enhanced-mode: fake-ip         # 关键配置\n  fake-ip-range: 198.18.0.1\u002F16  # 分配给域名的假 IP 段\n  fake-ip-filter:                # 这些域名不用 fake-ip（NTP、局域网等）\n    - \"*.lan\"\n    - \"*.local\"\n    - \"time.*.com\"\n    - \"+.ntp.org\"\n  nameserver:\n    - 223.5.5.5      # 阿里 DNS（国内）\n    - 119.29.29.29   # 腾讯 DNS（国内）\n  fallback:\n    - \"https:\u002F\u002F1.1.1.1\u002Fdns-over-https\"   # Cloudflare DoH（国外）\n    - \"https:\u002F\u002F8.8.8.8\u002Fdns-over-https\"   # Google DoH（国外）\n  fallback-filter:\n    geoip: true\n    geoip-code: CN\n    ipcidr:\n      - 240.0.0.0\u002F4\n```\n\n**fake-ip 原理**：Clash 拦截 DNS 请求，立即返回一个假 IP（如 `198.18.0.1`），同时记录\"假 IP → 域名\"的映射。当实际连接请求到来时，Clash 查表得到真实域名，再按规则决定走代理还是直连，代理节点负责解析真实域名。\n\n好处：\n- 消除 DNS 污染（国内 DNS 不会污染走代理的域名）\n- 延迟更低（无需等待 DNS 解析）\n\n### redir-host 模式\n\n```yaml\nenhanced-mode: redir-host\n```\n\nClash 真正解析域名，得到 IP 后再匹配 `IP-CIDR` 规则。缺点：国内 DNS 可能污染域名，且多一次 DNS 往返。\n\n---\n\n## 完整配置示例\n\n```yaml\nmixed-port: 7890\nallow-lan: false\nmode: rule\nlog-level: warning\nipv6: false\n\ndns:\n  enable: true\n  listen: 0.0.0.0:53\n  enhanced-mode: fake-ip\n  fake-ip-range: 198.18.0.1\u002F16\n  fake-ip-filter:\n    - \"*.lan\"\n    - \"*.local\"\n    - \"+.ntp.org\"\n  nameserver:\n    - 223.5.5.5\n    - 119.29.29.29\n  fallback:\n    - \"https:\u002F\u002F1.1.1.1\u002Fdns-over-https\"\n  fallback-filter:\n    geoip: true\n    geoip-code: CN\n\nproxies:\n  - name: \"香港 01\"\n    type: vless\n    server: hk01.example.com\n    port: 443\n    uuid: \"your-uuid-here\"\n    network: ws\n    tls: true\n    ws-opts:\n      path: \u002Fws\n      headers:\n        Host: hk01.example.com\n\nproxy-groups:\n  - name: \"节点选择\"\n    type: select\n    proxies: [\"自动选择\", \"香港 01\", DIRECT]\n\n  - name: \"自动选择\"\n    type: url-test\n    proxies: [\"香港 01\"]\n    url: \"https:\u002F\u002Fwww.gstatic.com\u002Fgenerate_204\"\n    interval: 300\n\n  - name: \"广告拦截\"\n    type: select\n    proxies: [REJECT, DIRECT]\n\nrule-providers:\n  reject:\n    type: http\n    behavior: domain\n    url: \"https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FLoyalsoldier\u002Fclash-rules@release\u002Freject.txt\"\n    path: .\u002Fruleset\u002Freject.yaml\n    interval: 86400\n  cn:\n    type: http\n    behavior: domain\n    url: \"https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FLoyalsoldier\u002Fclash-rules@release\u002Fdirect.txt\"\n    path: .\u002Fruleset\u002Fcn.yaml\n    interval: 86400\n  proxy:\n    type: http\n    behavior: domain\n    url: \"https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FLoyalsoldier\u002Fclash-rules@release\u002Fproxy.txt\"\n    path: .\u002Fruleset\u002Fproxy.yaml\n    interval: 86400\n\nrules:\n  - RULE-SET,reject,广告拦截\n  - RULE-SET,cn,DIRECT\n  - RULE-SET,proxy,节点选择\n  - GEOIP,CN,DIRECT\n  - GEOIP,PRIVATE,DIRECT,no-resolve\n  - MATCH,节点选择\n```\n\n---\n\n## 常见问题\n\n### DNS 泄露\n\n症状：用代理访问 Google，但 DNS 请求走了国内服务器，暴露了访问意图。\n\n解法：开启 fake-ip 模式 + 确保 `fallback` 里的 DNS 走代理（在 Clash Verge 里开启\"系统代理\"或 TUN 模式）。\n\n### 某些 App 绕过 Clash\n\n原因：App 直接使用 IP 硬编码或 DNS-over-HTTPS，不走系统代理。\n\n解法：开启 **TUN 模式**（虚拟网卡，接管全局流量）：\n\n```yaml\ntun:\n  enable: true\n  stack: mixed      # gvisor \u002F lwip \u002F mixed（推荐）\n  dns-hijack:\n    - \"any:53\"\n  auto-route: true\n  auto-detect-interface: true\n```\n\n### 规则集更新失败\n\nClash Verge Rev 里手动点\"更新规则集\"，或检查 `rule-providers` 的 URL 是否可达。\n\n---\n\n## 规则集推荐\n\n- [Loyalsoldier\u002Fclash-rules](https:\u002F\u002Fgithub.com\u002FLoyalsoldier\u002Fclash-rules)：国内最广泛使用的分流规则\n- [blackmatrix7\u002Fios_rule_script](https:\u002F\u002Fgithub.com\u002Fblackmatrix7\u002Fios_rule_script)：更细粒度的 App 级规则","\u003Ch2 id=\"clash-mihomo-是什么\">Clash \u002F Mihomo 是什么\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Clash\u003C\u002Fstrong> 是一个规则驱动的代理客户端内核，\u003Cstrong>Mihomo\u003C\u002Fstrong>（原 Clash.Meta）是它目前最活跃的分支，支持更多协议和特性。大多数 GUI 客户端（Clash Verge Rev、OpenClash 等）底层跑的都是 Mihomo 内核。\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>注意：原版 Clash 仓库已于 2023 年 11 月删库，目前使用 Mihomo 内核。\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Chr>\n\u003Ch2 id=\"配置文件结构\">配置文件结构\u003C\u002Fh2>\n\u003Cp>一份 Clash 配置由以下几个部分组成：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-yaml\"># 基础设置\nport: 7890          # HTTP 代理端口\nsocks-port: 7891    # SOCKS5 代理端口\nmixed-port: 7892    # HTTP + SOCKS5 混合端口（推荐用这个）\nallow-lan: false    # 是否允许局域网连接\nmode: rule          # 代理模式：rule \u002F global \u002F direct\nlog-level: info\n\n# DNS 配置\ndns: ...\n\n# 代理节点\nproxies: ...\n\n# 策略组\nproxy-groups: ...\n\n# 规则\nrules: ...\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2 id=\"代理模式\">代理模式\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>模式\u003C\u002Fth>\n\u003Cth>行为\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>rule\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>按规则分流，国内直连，国外走代理（\u003Cstrong>日常使用\u003C\u002Fstrong>）\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>global\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>全部走代理\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>direct\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>全部直连，相当于关闭代理\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Chr>\n\u003Ch2 id=\"策略组类型\">策略组类型\u003C\u002Fh2>\n\u003Cpre>\u003Ccode class=\"language-yaml\">proxy-groups:\n  # 手动选择节点\n  - name: "手动选择"\n    type: select\n    proxies:\n      - "香港 01"\n      - "日本 01"\n      - DIRECT\n\n  # 自动测速，选延迟最低的\n  - name: "自动选择"\n    type: url-test\n    proxies:\n      - "香港 01"\n      - "日本 01"\n    url: "https:\u002F\u002Fwww.gstatic.com\u002Fgenerate_204"\n    interval: 300     # 每 5 分钟测速一次\n    tolerance: 50     # 延迟差在 50ms 内不切换\n\n  # 故障转移：第一个挂了自动换下一个\n  - name: "故障转移"\n    type: fallback\n    proxies:\n      - "香港 01"\n      - "日本 01"\n    url: "https:\u002F\u002Fwww.gstatic.com\u002Fgenerate_204"\n    interval: 60\n\n  # 负载均衡：多节点轮流用\n  - name: "负载均衡"\n    type: load-balance\n    proxies:\n      - "香港 01"\n      - "香港 02"\n    strategy: round-robin   # 或 consistent-hashing\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2 id=\"规则类型\">规则类型\u003C\u002Fh2>\n\u003Cp>规则从上到下匹配，第一条命中则停止：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-yaml\">rules:\n  # 域名完整匹配\n  - DOMAIN,example.com,DIRECT\n\n  # 域名后缀匹配（最常用）\n  - DOMAIN-SUFFIX,google.com,手动选择\n  - DOMAIN-SUFFIX,github.com,手动选择\n\n  # 域名关键词（慎用，容易误匹配）\n  - DOMAIN-KEYWORD,youtube,手动选择\n\n  # IP 段\n  - IP-CIDR,192.168.0.0\u002F16,DIRECT,no-resolve\n  - IP-CIDR,10.0.0.0\u002F8,DIRECT,no-resolve\n\n  # GeoIP 国家码（需要 geoip.dat 数据库）\n  - GEOIP,CN,DIRECT\n  - GEOIP,PRIVATE,DIRECT\n\n  # 规则集（从 URL 加载，减少配置体积）\n  - RULE-SET,reject,REJECT        # 广告拦截\n  - RULE-SET,direct,DIRECT        # 国内直连\n  - RULE-SET,proxy,手动选择       # 需要代理\n\n  # 兜底规则，必须放最后\n  - MATCH,手动选择\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2 id=\"dns-配置\">DNS 配置\u003C\u002Fh2>\n\u003Cp>DNS 是 Clash 里最容易踩坑的部分。\u003C\u002Fp>\n\u003Ch3 id=\"fake-ip-模式-推荐\">fake-ip 模式（推荐）\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-yaml\">dns:\n  enable: true\n  listen: 0.0.0.0:53\n  ipv6: false\n  enhanced-mode: fake-ip         # 关键配置\n  fake-ip-range: 198.18.0.1\u002F16  # 分配给域名的假 IP 段\n  fake-ip-filter:                # 这些域名不用 fake-ip（NTP、局域网等）\n    - "*.lan"\n    - "*.local"\n    - "time.*.com"\n    - "+.ntp.org"\n  nameserver:\n    - 223.5.5.5      # 阿里 DNS（国内）\n    - 119.29.29.29   # 腾讯 DNS（国内）\n  fallback:\n    - "https:\u002F\u002F1.1.1.1\u002Fdns-over-https"   # Cloudflare DoH（国外）\n    - "https:\u002F\u002F8.8.8.8\u002Fdns-over-https"   # Google DoH（国外）\n  fallback-filter:\n    geoip: true\n    geoip-code: CN\n    ipcidr:\n      - 240.0.0.0\u002F4\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>fake-ip 原理\u003C\u002Fstrong>：Clash 拦截 DNS 请求，立即返回一个假 IP（如 \u003Ccode>198.18.0.1\u003C\u002Fcode>），同时记录"假 IP → 域名"的映射。当实际连接请求到来时，Clash 查表得到真实域名，再按规则决定走代理还是直连，代理节点负责解析真实域名。\u003C\u002Fp>\n\u003Cp>好处：\u003C\u002Fp>\n\u003Cul>\n\u003Cli>消除 DNS 污染（国内 DNS 不会污染走代理的域名）\u003C\u002Fli>\n\u003Cli>延迟更低（无需等待 DNS 解析）\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"redir-host-模式\">redir-host 模式\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-yaml\">enhanced-mode: redir-host\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Clash 真正解析域名，得到 IP 后再匹配 \u003Ccode>IP-CIDR\u003C\u002Fcode> 规则。缺点：国内 DNS 可能污染域名，且多一次 DNS 往返。\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"完整配置示例\">完整配置示例\u003C\u002Fh2>\n\u003Cpre>\u003Ccode class=\"language-yaml\">mixed-port: 7890\nallow-lan: false\nmode: rule\nlog-level: warning\nipv6: false\n\ndns:\n  enable: true\n  listen: 0.0.0.0:53\n  enhanced-mode: fake-ip\n  fake-ip-range: 198.18.0.1\u002F16\n  fake-ip-filter:\n    - "*.lan"\n    - "*.local"\n    - "+.ntp.org"\n  nameserver:\n    - 223.5.5.5\n    - 119.29.29.29\n  fallback:\n    - "https:\u002F\u002F1.1.1.1\u002Fdns-over-https"\n  fallback-filter:\n    geoip: true\n    geoip-code: CN\n\nproxies:\n  - name: "香港 01"\n    type: vless\n    server: hk01.example.com\n    port: 443\n    uuid: "your-uuid-here"\n    network: ws\n    tls: true\n    ws-opts:\n      path: \u002Fws\n      headers:\n        Host: hk01.example.com\n\nproxy-groups:\n  - name: "节点选择"\n    type: select\n    proxies: ["自动选择", "香港 01", DIRECT]\n\n  - name: "自动选择"\n    type: url-test\n    proxies: ["香港 01"]\n    url: "https:\u002F\u002Fwww.gstatic.com\u002Fgenerate_204"\n    interval: 300\n\n  - name: "广告拦截"\n    type: select\n    proxies: [REJECT, DIRECT]\n\nrule-providers:\n  reject:\n    type: http\n    behavior: domain\n    url: "https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FLoyalsoldier\u002Fclash-rules@release\u002Freject.txt"\n    path: .\u002Fruleset\u002Freject.yaml\n    interval: 86400\n  cn:\n    type: http\n    behavior: domain\n    url: "https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FLoyalsoldier\u002Fclash-rules@release\u002Fdirect.txt"\n    path: .\u002Fruleset\u002Fcn.yaml\n    interval: 86400\n  proxy:\n    type: http\n    behavior: domain\n    url: "https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FLoyalsoldier\u002Fclash-rules@release\u002Fproxy.txt"\n    path: .\u002Fruleset\u002Fproxy.yaml\n    interval: 86400\n\nrules:\n  - RULE-SET,reject,广告拦截\n  - RULE-SET,cn,DIRECT\n  - RULE-SET,proxy,节点选择\n  - GEOIP,CN,DIRECT\n  - GEOIP,PRIVATE,DIRECT,no-resolve\n  - MATCH,节点选择\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2 id=\"常见问题\">常见问题\u003C\u002Fh2>\n\u003Ch3 id=\"dns-泄露\">DNS 泄露\u003C\u002Fh3>\n\u003Cp>症状：用代理访问 Google，但 DNS 请求走了国内服务器，暴露了访问意图。\u003C\u002Fp>\n\u003Cp>解法：开启 fake-ip 模式 + 确保 \u003Ccode>fallback\u003C\u002Fcode> 里的 DNS 走代理（在 Clash Verge 里开启"系统代理"或 TUN 模式）。\u003C\u002Fp>\n\u003Ch3 id=\"某些-app-绕过-clash\">某些 App 绕过 Clash\u003C\u002Fh3>\n\u003Cp>原因：App 直接使用 IP 硬编码或 DNS-over-HTTPS，不走系统代理。\u003C\u002Fp>\n\u003Cp>解法：开启 \u003Cstrong>TUN 模式\u003C\u002Fstrong>（虚拟网卡，接管全局流量）：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-yaml\">tun:\n  enable: true\n  stack: mixed      # gvisor \u002F lwip \u002F mixed（推荐）\n  dns-hijack:\n    - "any:53"\n  auto-route: true\n  auto-detect-interface: true\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"规则集更新失败\">规则集更新失败\u003C\u002Fh3>\n\u003Cp>Clash Verge Rev 里手动点"更新规则集"，或检查 \u003Ccode>rule-providers\u003C\u002Fcode> 的 URL 是否可达。\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"规则集推荐\">规则集推荐\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FLoyalsoldier\u002Fclash-rules\">Loyalsoldier\u002Fclash-rules\u003C\u002Fa>：国内最广泛使用的分流规则\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fblackmatrix7\u002Fios_rule_script\">blackmatrix7\u002Fios_rule_script\u003C\u002Fa>：更细粒度的 App 级规则\u003C\u002Fli>\n\u003C\u002Ful>\n","2026-04-30",[11,12,13,14],"网络","clash","代理","配置",false,[17,30,41,53,63,70,77,84,91,98,108,117,127,136,144,152,161,170,179,189,196,206,212,218,224,231,238,245,248,258,267,276,286,296,306,314,324,335,345,354,362,368,376,384,392,400,408,415],{"slug":18,"title":19,"description":20,"pub_date":21,"tags":22,"draft":15,"word_count":29},"ide-skills-guide","Agent Skills 完全指南：21 款第三方 Skill 深度评测与使用心得","全面评测 21 款第三方 Agent Skills，涵盖 Vue 生态、前端设计、构建工具、实用工具四大分类。从安装配置到实际使用场景，带你了解每个 Skill 的功能特点、最佳实践与使用心得。","2026-06-15",[23,24,25,26,27,28],"agent","skills","AI","效率工具","前端","Vue",4169,{"slug":31,"title":32,"description":33,"pub_date":34,"tags":35,"draft":15,"word_count":40},"linux-kernel-skeleton-struct-funcptr-container_of","Linux 内核骨架：struct、函数指针与 container_of","读懂 Linux 内核源码的三件套：巨大的 struct 组合代替继承、函数指针表实现虚派发、container_of 宏从嵌入成员找回完整对象。","2026-05-09",[36,37,38,39],"linux","kernel","C","container_of",1369,{"slug":42,"title":43,"description":44,"pub_date":45,"tags":46,"draft":15,"word_count":52},"astro-complete-guide-2025","Astro 5 深度剖析：Islands 架构原理、构建优化与 Cloudflare Workers 边缘部署","从编译器视角解析 Astro 5 的 Islands 架构实现原理，Content Layer API 的 Vite 插件机制，Server Islands 的流式渲染，以及如何在 Cloudflare Workers + D1 边缘环境下榨干性能。","2026-05-08",[47,48,49,50,51],"astro","frontend","cloudflare","performance","architecture",3663,{"slug":54,"title":55,"description":56,"pub_date":57,"tags":58,"draft":15,"word_count":62},"llm-prompt-engineering","Prompt Engineering 实战：让 LLM 真正听话的技巧","System prompt 怎么写、Few-shot 怎么设计、Chain-of-Thought 原理，以及常见失败模式和调试方法。","2026-05-03",[59,60,61],"ai","llm","工程实践",1723,{"slug":64,"title":65,"description":66,"pub_date":57,"tags":67,"draft":15,"word_count":69},"rag-system-design","RAG 系统设计：从 naive 到 production-ready","Retrieval-Augmented Generation 不只是「向量数据库 + LLM」，分块策略、召回质量、重排序、缓存才是工程核心。",[59,68,60,61],"rag",1613,{"slug":71,"title":72,"description":73,"pub_date":57,"tags":74,"draft":15,"word_count":76},"git-advanced-workflow","Git 进阶工作流：rebase、cherry-pick、bisect 的正确使用","merge 会了，但 rebase 总搞错？bisect 找 bug 提交？interactive rebase 整理历史？这篇一次说清楚。",[75,61],"git",1396,{"slug":78,"title":79,"description":80,"pub_date":57,"tags":81,"draft":15,"word_count":83},"docker-practical-guide","Docker 实战：从会用到用好","会 docker run 不够，Dockerfile 最佳实践、多阶段构建、Compose 编排、镜像瘦身才是日常真正需要的。",[82,36,61],"docker",1268,{"slug":85,"title":86,"description":87,"pub_date":57,"tags":88,"draft":15,"word_count":90},"anthropics-skills-guide","anthropics\u002Fskills：Anthropic 官方 Agent Skills 仓库解析","Anthropic 官方开源的 Agent Skills 标准仓库，127k stars，解析 SKILL.md 规范、17 个示例 skill 的设计模式，以及如何在 Claude Code \u002F Claude.ai \u002F API 中使用",[59,89,23,24],"Claude",2090,{"slug":92,"title":93,"description":94,"pub_date":57,"tags":95,"draft":15,"word_count":97},"karpathy-claude-code-guidelines","Karpathy 的 LLM 编码批评与 CLAUDE.md 最佳实践","基于 Andrej Karpathy 对 LLM 编程助手的观察，forrestchang 提炼出一个 CLAUDE.md 文件，4 条原则解决 AI 编码的典型失控问题：乱猜假设、过度设计、乱改代码、目标不清",[59,89,96,61],"Claude Code",2699,{"slug":99,"title":100,"description":101,"pub_date":57,"tags":102,"draft":15,"word_count":107},"typescript-advanced-patterns","TypeScript 高级模式：让类型系统为你工作","基础 TS 会了但类型总是 any？条件类型、映射类型、模板字面量类型、infer 关键字才是 TS 的真正威力。",[103,104,105,106],"typescript","类型系统","前端工程","高级模式",1419,{"slug":109,"title":110,"description":111,"pub_date":57,"tags":112,"draft":15,"word_count":116},"linux-performance-tuning","Linux 性能调优实战：从 top 到 perf 的完整工具链","遇到性能问题不知道从哪下手？这篇建立系统化的排查思路，从 CPU\u002F内存\u002FIO\u002F网络逐层分析。",[36,113,114,115],"性能","运维","系统编程",1524,{"slug":118,"title":119,"description":120,"pub_date":57,"tags":121,"draft":15,"word_count":126},"python-functional-programming","Python 函数式编程：map\u002Ffilter\u002Freduce 之外","Python 不是纯函数式语言，但 functools、itertools、偏函数、闭包这些工具用好了能让代码简洁一个量级。",[122,123,124,125],"python","函数式","闭包","装饰器",1867,{"slug":128,"title":129,"description":130,"pub_date":57,"tags":131,"draft":15,"word_count":135},"python-oop-guide","Python 面向对象：__init__ 之外你需要知道的","Python OOP 不只是 class + __init__，魔术方法、描述符、元类才是真正的武器。",[122,132,133,134],"OOP","面向对象","魔术方法",1792,{"slug":137,"title":138,"description":139,"pub_date":57,"tags":140,"draft":15,"word_count":143},"python-data-structures","Python 内置数据结构深度解析","list、dict、set、tuple 不只是数据容器，搞懂它们的底层实现和时间复杂度，才能写出高性能 Python。",[122,141,113,142],"数据结构","算法",1517,{"slug":145,"title":146,"description":147,"pub_date":57,"tags":148,"draft":15,"word_count":151},"python-basics-quick-start","Python 快速上手：写给有编程基础的人","已经会其他语言，想快速掌握 Python 的语法特性和思维方式，这篇是捷径。",[122,149,150],"入门","基础",1607,{"slug":153,"title":154,"description":155,"pub_date":57,"tags":156,"draft":15,"word_count":160},"python-dataclass-pydantic","Python dataclass vs Pydantic：数据类选型指南","dataclass 是标准库的轻量选择，Pydantic v2 是带验证的重武器，什么时候用哪个，这篇说清楚。",[122,157,158,159],"dataclass","pydantic","数据验证",1323,{"slug":162,"title":163,"description":164,"pub_date":57,"tags":165,"draft":15,"word_count":169},"python-asyncio-practical","Python asyncio 实战：从回调地狱到协程优雅","asyncio 是 Python 异步编程的核心，搞懂 event loop、Task、gather 这些概念才能写出真正高效的异步代码。",[122,166,167,168],"asyncio","并发","网络编程",1258,{"slug":171,"title":172,"description":173,"pub_date":57,"tags":174,"draft":15,"word_count":178},"python-type-hints-guide","Python 类型注解完全指南：从入门到实践","Python 3.5+ 引入类型注解，配合 mypy\u002Fpyright 让 Python 也能享受静态类型检查的好处。",[122,175,176,177],"typescript-style","type-hints","工具链",1102,{"slug":180,"title":181,"description":182,"pub_date":183,"tags":184,"draft":15,"word_count":188},"pwa-install-update-button","PWA 踩坑：为什么安装按钮从来不出现","从 beforeinstallprompt 到 Service Worker waiting，把 PWA 的安装与更新提示真正做对","2026-05-02",[185,186,187],"pwa","javascript","web",1683,{"slug":190,"title":191,"description":192,"pub_date":193,"tags":194,"draft":15,"word_count":195},"openclaw-vs-hermes-agent","OpenClaw vs Hermes Agent：两个本地优先 Agent 的设计差异","OpenClaw（Novita AI）和 Hermes Agent（Nous Research）都是本地运行的个人 AI Agent，但在记忆系统、技能学习、运行环境和模型生态上走了不同的路。深入对比两种架构的核心差异。","2026-05-01",[59,23,60],1679,{"slug":197,"title":198,"description":199,"pub_date":193,"tags":200,"draft":15,"word_count":205},"cpp-random-design-patterns","C++ 设计模式实战：RAII、观察者、工厂","用现代 C++（C++17\u002F20）实现三种高频设计模式：RAII 资源管理、观察者模式事件系统、工厂模式插件架构。每种模式给出问题场景、实现代码和真实工程案例。",[201,202,203,204],"cpp","设计模式","c++17","工程",2613,{"slug":207,"title":208,"description":209,"pub_date":193,"tags":210,"draft":15,"word_count":211},"data-structures-fundamentals","数据结构基础：从数组到红黑树","系统梳理常用数据结构的核心原理、时间复杂度和适用场景。数组、链表、栈、队列、哈希表、二叉树、堆、图，每种结构附实现要点和 C++ 代码片段。",[141,142,201,150],3004,{"slug":213,"title":214,"description":215,"pub_date":9,"tags":216,"draft":15,"word_count":217},"ai-agent-what-is","什么是 AI Agent？从 LLM 到自主执行","LLM 本身是无状态问答机，Agent 是什么让它’动’起来的？本文深入解析 Agent 的四个核心能力、ReAct 框架、工具调用原理，以及主流框架横向对比。",[59,23,60],2116,{"slug":219,"title":220,"description":221,"pub_date":9,"tags":222,"draft":15,"word_count":223},"ai-agent-memory","AI Agent 的记忆系统：从上下文窗口到长期记忆","深入拆解 AI Agent 的四种记忆类型、上下文窗口压缩策略、RAG 向量检索原理，以及三种典型失败模式和工程选型建议。",[59,23,68],2052,{"slug":225,"title":226,"description":227,"pub_date":9,"tags":228,"draft":15,"word_count":230},"network-proxy-vpn-guide","代理与翻墙技术原理：从 HTTP 代理到现代协议","深入解析代理与 VPN 的本质区别，梳理从 SOCKS5 到 Shadowsocks、V2Ray\u002FXray、Hysteria2 的协议演进，以及机场订阅的技术本质。",[11,13,229],"协议",2148,{"slug":232,"title":233,"description":234,"pub_date":9,"tags":235,"draft":15,"word_count":151},"algorithm-binary-search","二分查找：永远写不对？记住这个模板","彻底搞清楚二分查找的边界问题：闭区间和左闭右开两套模板、三道经典 LeetCode 题目完整 C++ 实现，以及二分答案的进阶思路。",[142,236,237,201],"二分查找","leetcode",{"slug":239,"title":240,"description":241,"pub_date":9,"tags":242,"draft":15,"word_count":244},"algorithm-sliding-window","滑动窗口算法：从暴力到 O(n) 的思维跃迁","系统讲解滑动窗口算法的核心模板、适用题型，配合三道经典 LeetCode 题目的完整 C++ 实现，彻底理解双指针收缩思路。",[142,243,237,201],"滑动窗口",1943,{"slug":4,"title":5,"description":6,"pub_date":9,"tags":246,"draft":15,"word_count":247},[11,12,13,14],1292,{"slug":249,"title":250,"description":251,"pub_date":252,"tags":253,"draft":15,"word_count":257},"hid-hotplug","HID 设备热插拔检测：从 udev 到 node-hid","在 Linux 上用 node-hid + usb 库实现可靠的 USB HID 设备热插拔检测，踩坑记录","2026-04-28",[201,254,36,255,256],"hid","nodejs","electron",2039,{"slug":259,"title":260,"description":261,"pub_date":262,"tags":263,"draft":15,"word_count":266},"electron-ipc-types","Electron IPC 类型安全：从 any 到完全类型化","用 TypeScript 泛型封装 Electron IPC，彻底消灭 any，preload 契约集中管理","2026-04-25",[256,103,264,265],"ipc","vue",1446,{"slug":268,"title":269,"description":270,"pub_date":271,"tags":272,"draft":15,"word_count":275},"element-plus-popover-hide","手动关闭多个 el-popover（不用 v-model:visible）","通过 ref + Reflect.get 调用 hide() 方法手动关闭 Element Plus Popover，解释 Vue3 Proxy 导致无法直接调用实例方法的原因。","2024-10-25",[265,273,274],"element-plus","vue3",1321,{"slug":277,"title":278,"description":279,"pub_date":280,"tags":281,"draft":15,"word_count":285},"vite-vue3-ts-elementplus-pinia","用 Vite+（vp）从零搭建 Vue3 + TypeScript + Element Plus + Pinia + Vue Router","使用 Vite+ 统一工具链（vp）一条命令搭建 Vue3 全家桶，涵盖按需导入、Pinia store、路由配置，以及常见坑的解决方案。","2024-08-27",[265,282,103,273,283,284],"vite","pinia","vite-plus",1960,{"slug":287,"title":288,"description":289,"pub_date":290,"tags":291,"draft":15,"word_count":295},"cef-lnk2038-iterator-debug-level","CEF LNK2038：解决 _ITERATOR_DEBUG_LEVEL 不匹配错误","分析 CEF（Chromium Embedded Framework）集成时出现的 LNK2038 _ITERATOR_DEBUG_LEVEL 链接错误，从根本原因到解决方案的完整指南。","2024-05-07",[201,292,293,294],"CEF","Visual Studio","链接错误",1509,{"slug":297,"title":298,"description":299,"pub_date":300,"tags":301,"draft":15,"word_count":305},"npm-electron-install-fix","彻底解决 npm 安装 Electron 失败的问题","分析 npm install electron 失败的根本原因（下载二进制超时\u002F被墙），通过国内镜像（npmmirror）彻底解决，并介绍多种备选方案和常见错误排查。","2024-03-01",[256,302,303,304],"npm","前端工具链","国内镜像",1494,{"slug":307,"title":308,"description":309,"pub_date":310,"tags":311,"draft":15,"word_count":313},"git-out-of-memory","解决 git 报错：Fatal: Out of memory, malloc failed","分析 git 大仓库操作时出现 Out of memory malloc failed 的根本原因，通过调整 pack.windowMemory、http.postBuffer 和 git repack 彻底解决。","2024-01-31",[75,36,312],"工具",2244,{"slug":315,"title":316,"description":317,"pub_date":318,"tags":319,"draft":15,"word_count":323},"vmware-tools-install","在 VMware 虚拟机中安装 open-vm-tools 完整指南","详解 VMware Tools 的作用、open-vm-tools 与官方 VMware Tools 的区别，以及在 Ubuntu 虚拟机中安装并生效的完整步骤和常见问题排查。","2023-11-21",[320,36,321,322],"VMware","Ubuntu","虚拟机",2523,{"slug":325,"title":326,"description":327,"pub_date":328,"tags":329,"draft":15,"word_count":334},"load-balancing-algorithms","负载均衡算法完全指南：从轮询到一致性哈希","系统梳理静态与动态负载均衡算法，涵盖轮询、随机、权重、IP Hash、一致性 Hash、最少连接、最快响应等，并对比 Nginx、Dubbo、Spring Cloud LoadBalancer 的实现差异。","2023-11-15",[330,331,332,333],"分布式","负载均衡","Nginx","微服务",1764,{"slug":336,"title":337,"description":338,"pub_date":339,"tags":340,"draft":15,"word_count":344},"win-cw2a-ca2w","ATL 字符串转换：CW2A 与 CA2W 完全指南","详解 ATL 宏 CW2A\u002FCA2W 在 Unicode 与 ANSI 之间的字符串转换用法、头文件依赖、USES_CONVERSION 宏的作用与常见陷阱。","2023-06-09",[201,341,342,343],"windows","ATL","字符串",1665,{"slug":346,"title":347,"description":348,"pub_date":339,"tags":349,"draft":15,"word_count":353},"csharp-sendmessage-cpp","C# 通过 SendMessage 向 C++ 窗口发送消息与字符串","使用 P\u002FInvoke 调用 user32.dll 的 SendMessage，从 C# 发送自定义 WM_USER 消息及字符串指针给 C++ 原生窗口，并在 C++ 侧正确接收和转换。",[350,201,341,351,352],"C#","互操作","PInvoke",1554,{"slug":355,"title":356,"description":357,"pub_date":358,"tags":359,"draft":15,"word_count":361},"win-postmessage-vector","Windows PostMessage 跨线程传递 std::vector 指针","通过 PostMessage 在 Windows 消息队列中传递 std::vector 指针，使用 reinterpret_cast 将指针装入 LPARAM，并在接收方正确释放内存。","2023-05-26",[201,341,360],"WinAPI",1823,{"slug":363,"title":364,"description":365,"pub_date":358,"tags":366,"draft":15,"word_count":367},"exe-dll-single-package","将 EXE 和 DLL 打包成单一可执行文件","介绍两种将 exe 和依赖 dll 打包成单文件的方案：Enigma Virtual Box 和 WinRAR 自解压，适合发布 Windows 桌面程序时简化分发流程。",[341,201,312],1619,{"slug":369,"title":370,"description":371,"pub_date":358,"tags":372,"draft":15,"word_count":375},"cpp-random-mt19937","C++ 现代随机数生成：用 mt19937 彻底告别 rand()","深入讲解为什么 rand() 不够用，以及如何用 C++11 的 \u003Crandom> 库正确生成高质量随机数，涵盖 mt19937、各种分布和线程安全。",[201,373,374],"c++11","random",1549,{"slug":377,"title":378,"description":379,"pub_date":380,"tags":381,"draft":15,"word_count":383},"win-startup-registry","C++ 实现程序开机自启动：注册表方式详解","通过操作 Windows 注册表 Run 键实现程序开机自启动，包括 HKCU 与 HKLM 区别、完整封装代码、工作目录问题和 UAC 权限处理。","2022-12-26",[341,201,382],"registry",1201,{"slug":385,"title":386,"description":387,"pub_date":388,"tags":389,"draft":15,"word_count":391},"mfc-cstring-wparam","MFC 中 CString 与 WPARAM 之间的转换","详解 MFC 消息传递中 CString 无法直接强转为 WPARAM 的原因，以及两种正确的转换方案，并介绍结构体指针传递的正确姿势。","2022-11-25",[390,201,341],"mfc",1546,{"slug":393,"title":394,"description":395,"pub_date":396,"tags":397,"draft":15,"word_count":399},"duilib-static-build","正确编译 Duilib 静态库：避免 ATL 依赖和链接错误","详解如何用 DuiLib_Static.vcxproj 编译 Duilib 静态库，解决 VARIANT 未定义、Unicode 配置不匹配和 ATL 依赖等常见问题。","2022-08-24",[201,398,341,390],"duilib",2639,{"slug":401,"title":402,"description":403,"pub_date":404,"tags":405,"draft":15,"word_count":407},"mfc-dpi-adaptive","MFC 界面自适应不同分辨率","MFC 对话框程序实现控件和字体随分辨率自动缩放的完整方案，附 DPI Awareness 配置说明","2022-08-17",[390,201,341,406],"dpi",1414,{"slug":409,"title":410,"description":411,"pub_date":412,"tags":413,"draft":15,"word_count":414},"mfc-drag-window","MFC 无标题栏窗口客户区拖动：三种方法对比","MFC 对话框去掉标题栏后如何实现拖动移动窗口，三种方案完整实现与适用场景分析","2022-08-16",[390,201,341],1633,{"slug":416,"title":417,"description":418,"pub_date":419,"tags":420,"draft":15,"word_count":422},"algorithm-number-complement","整数的补数：位运算掩码解法","LeetCode 476 题，用掩码 XOR 实现整数补数，附 C++\u002FPython\u002FJava 三种实现及补数与补码的区别","2021-03-08",[142,421,237],"位运算",1374,[]]