What problem does it solve?
Configuration changes in Xberg can silently do nothing due to duplicate Default impls, ignored unknown keys, and misunderstood precedence rules, making debugging config behavior frustrating and error-prone.
Core Features & Use Cases
- Precedence Reference: Documents the exact precedence order for CLI mode (flags > inline JSON > config file > auto-discovery > defaults) and server/MCP mode (CLI args > env vars > [server] section > defaults).
- Discovery Rules: Clarifies that auto-discovery walks parent directories for xberg.toml only, while YAML/JSON configs require an explicit --config flag.
- Silent Failure Diagnosis: Identifies the two mechanisms that make config changes no-ops: duplicate TesseractConfig Default impls and serde silently ignoring unknown keys in nested configs.
- Use Case: When adding a new config flag or debugging why a setting in xberg.toml is not taking effect, consult this Skill to trace which precedence layer wins and whether a typo'd key is being silently dropped.
Quick Start
Ask the AI to explain why my xberg.toml setting for chunking max_chars is not taking effect and which precedence layer is overriding it.