What problem does it solve?
It clarifies how the LingTai TUI preset system distinguishes user-saved presets from built-in templates, preventing confusion about load order, override behavior, naming, and deletion semantics when working with ~/.lingtai-tui/presets/.
Core Features & Use Cases
- Directory-based source tracking: Explains that
Source (template vs saved) is derived purely from which directory a preset file lives in, with no serialized marker.
- Load and fallback semantics: Documents that saved presets override same-named templates, and that malformed saved files block fallback rather than silently falling through.
- Save/Delete/Bootstrap contract: Covers same-name overwrites in
saved/, <template>-N auto-naming for edited templates, delete-returns-nil-on-missing behavior, and RefreshTemplates rewriting templates on every launch.
- Use Case: When editing a built-in template in the preset editor, understand that saving creates a new
<template>-N file in saved/ that overrides the template on subsequent loads without touching the immutable template.
Quick Start
Explain how saved presets override templates and what happens when I save or delete a preset in the LingTai TUI.