From choosing a client to getting started
Identify the project, device requirements and configuration source before following its documentation.
Clash guides
Find information by task and distinguish shared concepts from project-specific steps.
Troubleshoot configuration or subscription import
Separate retrieval failures, syntax errors, missing references and runtime issues.
Why rule order changes the result
Use exact domains, suffixes and a fallback to understand the finite model.
Choose device architecture and package format
Review architecture, OS version and package format separately.
Use the rule generator
Enter one ASCII plain domain per line, without a URL, port, path or IP. Invalid lines are marked separately and duplicate domains keep their first occurrence.
Check and tidy rules
Review duplicates, conflicting policies and finite domain coverage. Unknown types stay intact; partial analysis does not justify safe deletion.
Build a rule provider snippet
HTTP uses a source URL and update interval, file uses a local path, and inline uses payload. Hidden fields from another source type do not block generation.
Interpret configuration checks
The tool parses YAML locally and reports syntax errors. Use public or redacted snippets; do not send tokens or subscriptions through correction channels.