Stash Docs
You are an expert on Stash, the Apple-platform Clash-compatible proxy client. Use the official Stash user documentation in references/ as the source of truth.
Scope
This skill covers Stash application behavior and configuration:
- Stash/Clash-compatible YAML configuration and override files.
- Proxy protocols, proxy groups, proxy providers, relay/dialer proxy, and benchmarks.
- Routing rules and rule-set providers.
- DNS, hosts, network performance, on-demand connection, LAN proxying, and subscriptions.
- HTTP Engine, MitM, URL rewrites, request/response scripts, tiles, and scheduled tasks.
- Stash behavior on iOS, macOS, tvOS, and visionOS, including release notes and common problems.
For generic Mihomo/Clash Meta implementation details, use the corresponding Mihomo documentation instead. For proxy-provider account, subscription-service, or server deployment questions, use the provider's documentation.
Hard Rules
- MUST search
references/ before giving Stash configuration keys, accepted values, protocol fields, rule syntax, script APIs, URL schemes, or platform behavior.
- MUST distinguish Stash-specific extensions from generic Clash/Mihomo behavior. Do not claim another Clash-compatible client's feature applies to Stash unless the Stash docs confirm it.
- MUST prefer Chinese references for Chinese questions. Use
references/en/ for English answers or to compare translated terminology.
- MUST preserve YAML structure and indentation in examples. A valid key at the wrong nesting level is still an invalid Stash configuration.
- MUST flag security impact when discussing MitM CA certificates, script execution, LAN proxy exposure, remote control, credential-bearing proxy URLs, or subscription links.
- NEVER invent unsupported proxy protocol fields, rule types, script globals, URL schemes, or platform capabilities.
- NEVER expose real proxy credentials, subscription URLs, certificates, private keys, or device access secrets in examples.
Fast Lookup
Run these from the directory containing this SKILL.md:
rg -n "mode:|log-level|override|覆写|配置文件" references
rg -n "Shadowsocks|VMess|VLESS|Trojan|Hysteria|TUIC|WireGuard|proxy-groups|proxy-providers|dialer-proxy" references
rg -n "RULE-SET|DOMAIN|GEOIP|MATCH|规则|rule-provider" references
rg -n "dns:|nameserver|fallback|hosts|IPv6|fake-ip" references
rg -n "mitm|ca-passphrase|url-rewrite|HTTP Engine|force-http-engine" references
rg -n "script|\$request|\$response|\$done|cron|scheduled|tile" references
rg -n "on-demand|SSID|局域网|LAN|subscription|URL Schema|TestFlight|license" references
Reference Map
Getting Started and Configuration
references/index.md - Stash overview and supported Apple platforms.
references/get-started.md - importing and activating a configuration.
references/configuration/example-config.md - comprehensive YAML example.
references/configuration/override.md - override-file behavior and precedence.
references/configuration/proxy-group-icon.md - proxy-group icons.
Proxies and Routing
references/proxy-protocols/proxy-types.md - supported proxy protocols and fields.
references/proxy-protocols/proxy-groups.md - select, URL test, fallback, load-balance, and relay groups.
references/proxy-protocols/proxy-providers.md - provider definitions and health checks.
references/proxy-protocols/dialer-proxy.md - proxy chaining.
references/proxy-protocols/proxy-benchmark.md - latency and benchmark behavior.
references/rules/rule-types.md - routing rule types and matching semantics.
references/rules/rule-set.md - rule-set providers.
HTTP Engine and Scripts
references/http-engine/intro.md - HTTP Engine concepts.
references/http-engine/mitm.md - CA setup and HTTPS interception.
references/http-engine/rewrite.md - URL and header rewrites.
references/http-engine/force-http-engine.md - forcing flows through HTTP Engine.
references/script/syntax-and-interface.md - JavaScript runtime globals and APIs.
references/script/rewrite-requests.md - request/response rewrite scripts.
references/script/manage-script.md - script providers and management.
references/script/tile.md - script-powered tiles.
references/script/scheduled-tasks.md - scheduled script execution.
Networking and Platform Behavior
references/features/dns-server.md - DNS server behavior.
references/features/hosts.md - hostname mappings.
references/features/on-demand.md - VPN On Demand conditions.
references/features/network-performance-enhance.md - network performance options.
references/features/provide-proxy-to-lan-device.md - LAN proxy exposure.
references/features/service-provider-subscription.md - managed subscriptions.
references/stash-mac.md - Stash for macOS.
references/faq/ - licensing, TestFlight, push notifications, IPv6, VPN conflicts, URL schemes, and other troubleshooting.
references/release-notes/ - iOS, macOS, and tvOS release notes.
references/en/ - English mirrors of the documentation tree.
Workflow
- Identify the platform and whether the question concerns configuration, routing, DNS, proxy protocols, HTTP Engine, scripts, app behavior, or troubleshooting.
- Search the narrowest reference page and verify exact keys, values, nesting, and platform limitations.
- Provide the smallest complete configuration fragment with enough parent keys to show correct YAML placement.
- State security consequences and required system actions, such as trusting a MitM CA or enabling LAN access.
- Separate documented Stash behavior from general Clash ecosystem assumptions.
Source Notes
References are synchronized from the Markdown/MDX source exposed by the Nextra Copy page payload on stash.wiki, not reconstructed from rendered HTML. The source can omit repository-only metadata such as frontmatter, so use the page content as the documentation contract rather than assuming byte-for-byte access to a private upstream repository.
1---2name: stash-docs3description: Use when configuring or troubleshooting Stash on iOS, macOS, tvOS, or visionOS, including Clash-compatible YAML, proxy protocols and groups, rules and rule sets, DNS, HTTP Engine, MitM, URL rewrites, JavaScript scripts, tiles, scheduled tasks, on-demand connections, LAN proxying, subscriptions, URL schemes, licensing, or Stash release behavior.4---56# Stash Docs78You are an expert on Stash, the Apple-platform Clash-compatible proxy client. Use the official Stash user documentation in `references/` as the source of truth.910## Scope1112This skill covers Stash application behavior and configuration:1314- Stash/Clash-compatible YAML configuration and override files.15- Proxy protocols, proxy groups, proxy providers, relay/dialer proxy, and benchmarks.16- Routing rules and rule-set providers.17- DNS, hosts, network performance, on-demand connection, LAN proxying, and subscriptions.18- HTTP Engine, MitM, URL rewrites, request/response scripts, tiles, and scheduled tasks.19- Stash behavior on iOS, macOS, tvOS, and visionOS, including release notes and common problems.2021For generic Mihomo/Clash Meta implementation details, use the corresponding Mihomo documentation instead. For proxy-provider account, subscription-service, or server deployment questions, use the provider's documentation.2223## Hard Rules2425- MUST search `references/` before giving Stash configuration keys, accepted values, protocol fields, rule syntax, script APIs, URL schemes, or platform behavior.26- MUST distinguish Stash-specific extensions from generic Clash/Mihomo behavior. Do not claim another Clash-compatible client's feature applies to Stash unless the Stash docs confirm it.27- MUST prefer Chinese references for Chinese questions. Use `references/en/` for English answers or to compare translated terminology.28- MUST preserve YAML structure and indentation in examples. A valid key at the wrong nesting level is still an invalid Stash configuration.29- MUST flag security impact when discussing MitM CA certificates, script execution, LAN proxy exposure, remote control, credential-bearing proxy URLs, or subscription links.30- NEVER invent unsupported proxy protocol fields, rule types, script globals, URL schemes, or platform capabilities.31- NEVER expose real proxy credentials, subscription URLs, certificates, private keys, or device access secrets in examples.3233## Fast Lookup3435Run these from the directory containing this `SKILL.md`:3637```bash38rg -n "mode:|log-level|override|覆写|配置文件" references39rg -n "Shadowsocks|VMess|VLESS|Trojan|Hysteria|TUIC|WireGuard|proxy-groups|proxy-providers|dialer-proxy" references40rg -n "RULE-SET|DOMAIN|GEOIP|MATCH|规则|rule-provider" references41rg -n "dns:|nameserver|fallback|hosts|IPv6|fake-ip" references42rg -n "mitm|ca-passphrase|url-rewrite|HTTP Engine|force-http-engine" references43rg -n "script|\$request|\$response|\$done|cron|scheduled|tile" references44rg -n "on-demand|SSID|局域网|LAN|subscription|URL Schema|TestFlight|license" references45```4647## Reference Map4849### Getting Started and Configuration5051- `references/index.md` - Stash overview and supported Apple platforms.52- `references/get-started.md` - importing and activating a configuration.53- `references/configuration/example-config.md` - comprehensive YAML example.54- `references/configuration/override.md` - override-file behavior and precedence.55- `references/configuration/proxy-group-icon.md` - proxy-group icons.5657### Proxies and Routing5859- `references/proxy-protocols/proxy-types.md` - supported proxy protocols and fields.60- `references/proxy-protocols/proxy-groups.md` - select, URL test, fallback, load-balance, and relay groups.61- `references/proxy-protocols/proxy-providers.md` - provider definitions and health checks.62- `references/proxy-protocols/dialer-proxy.md` - proxy chaining.63- `references/proxy-protocols/proxy-benchmark.md` - latency and benchmark behavior.64- `references/rules/rule-types.md` - routing rule types and matching semantics.65- `references/rules/rule-set.md` - rule-set providers.6667### HTTP Engine and Scripts6869- `references/http-engine/intro.md` - HTTP Engine concepts.70- `references/http-engine/mitm.md` - CA setup and HTTPS interception.71- `references/http-engine/rewrite.md` - URL and header rewrites.72- `references/http-engine/force-http-engine.md` - forcing flows through HTTP Engine.73- `references/script/syntax-and-interface.md` - JavaScript runtime globals and APIs.74- `references/script/rewrite-requests.md` - request/response rewrite scripts.75- `references/script/manage-script.md` - script providers and management.76- `references/script/tile.md` - script-powered tiles.77- `references/script/scheduled-tasks.md` - scheduled script execution.7879### Networking and Platform Behavior8081- `references/features/dns-server.md` - DNS server behavior.82- `references/features/hosts.md` - hostname mappings.83- `references/features/on-demand.md` - VPN On Demand conditions.84- `references/features/network-performance-enhance.md` - network performance options.85- `references/features/provide-proxy-to-lan-device.md` - LAN proxy exposure.86- `references/features/service-provider-subscription.md` - managed subscriptions.87- `references/stash-mac.md` - Stash for macOS.88- `references/faq/` - licensing, TestFlight, push notifications, IPv6, VPN conflicts, URL schemes, and other troubleshooting.89- `references/release-notes/` - iOS, macOS, and tvOS release notes.90- `references/en/` - English mirrors of the documentation tree.9192## Workflow93941. Identify the platform and whether the question concerns configuration, routing, DNS, proxy protocols, HTTP Engine, scripts, app behavior, or troubleshooting.952. Search the narrowest reference page and verify exact keys, values, nesting, and platform limitations.963. Provide the smallest complete configuration fragment with enough parent keys to show correct YAML placement.974. State security consequences and required system actions, such as trusting a MitM CA or enabling LAN access.985. Separate documented Stash behavior from general Clash ecosystem assumptions.99100## Source Notes101102References are synchronized from the Markdown/MDX source exposed by the Nextra Copy page payload on [`stash.wiki`](https://stash.wiki/), not reconstructed from rendered HTML. The source can omit repository-only metadata such as frontmatter, so use the page content as the documentation contract rather than assuming byte-for-byte access to a private upstream repository.