lingtai

Official-source-led manual for the TUI `claude` template.

Base URL / API-compat / provider / model / capability declaration shape versus credentials and live probes; includes proven Codex OAuth quota inspection with exact agent query routing and dated official-vs-measured context-window evidence.

Thin dual-axis router for preset questions: which of the 12 TUI-shipped built-in preset templates (provider axis), and which cross-cutting preset lifecycle mechanic (operation axis) — saving, checking availability, activating/refreshing, endpoint/capability facts, or troubleshooting. Read a child only when it is relevant; this does not describe arbitrary saved presets.

Anything you need to know about LingTai TUI. Read this first for the stable mental model, major-feature map, interface and slash-command help, or the correct source/manual route for a TUI question. It stays thin: exact command prose lives in the localized help assets, precise Go structure lives in `lingtai-tui-anatomy` plus the repository ANATOMY graph, and independent domains such as presets, Portal, tutorials, updates, and addons keep their own top-level skills.

Nested tutorial-guide reference for lessons 10–12: TUI commands, lifecycle exercises, addons, external connections, and graduation.

The 12-lesson tutorial curriculum for teaching a human how Lingtai works. Router for orientation, agent runtime, communication, memory/molt, capabilities, operations, addons, and graduation. Invoke this skill when the human is ready to begin or continue the tutorial.

Official-source-led manual for the TUI `codex-pool` template, including the codex-auth-pool.json format and manual-edit protocol.

Official-source-led manual for the TUI `codex` template.

Official-source-led manual for the TUI `custom` template.

Official-source-led manual for the TUI `deepseek` template.

Official-source-led manual for the TUI `gemini` template.

Official-source-led manual for the TUI `kimi` template.

Official-source-led manual for the TUI `mimo` template.

Official-source-led manual for the TUI `minimax` template.

Official-source-led manual for the TUI `nvidia` template.

Official-source-led manual for the TUI `openrouter` template.

How a saved preset becomes the running default, first-run/setup choice semantics, propagation, and what /refresh actually switches.

Why Save on the preset editor blocks or warns — the live validity probe, its fingerprint, and the 429/503/529 retryable-vs-hard-block split.

How saved presets differ from templates, and the Load/Save/Delete/Bootstrap contract — order, atomicity, and naming.

Bounded first-pass triage for preset problems; routes deeper runtime/update/migration questions elsewhere instead of guessing.

Official-source-led manual for the TUI `zhipu` template.

Discoverable source-navigation guide for the LingTai Go monorepo that ships `lingtai-tui` and `lingtai-portal`. Read this for TUI/Portal structure, runtime-boundary evidence, exact Go ownership, or when updating an `ANATOMY.md`. The repository-root `ANATOMY.md` is the normative convention and top of the distributed graph; this skill teaches the route into that graph without duplicating it. Kernel internals remain owned by `lingtai-kernel-anatomy`.

Nested lingtai-dev-guide reference for the project architecture: Go TUI/portal monorepo, Python kernel, MCP addon repos, filesystem IPC, and where per-project/per-machine state lives.

Nested lingtai-dev-guide reference for computing the recent prompt-cache hit rate from LingTai token ledgers over rolling windows (default 1h / 5h / 1d / 3d). Explains the provider-agnostic input/cached fields in logs/token_ledger.jsonl, the exact formula (sum(cached)/sum(input) per window), timestamp/timezone handling, the daemon double-count hazard, and ships a read-only stdlib script (scripts/cache_hit_rate.py) that aggregates an agent workdir, a project root, or a single ledger file. Use when asked how effective prompt caching has been recently, or to diagnose a cache-hit-rate drop after a refresh/affinity/cache-key change.

Nested lingtai-dev-guide reference for contribution workflow: issue/worktree/PR discipline, worktree inventory and exact-object approval gates, daemon decomposition, portfolio sweeps, repo-specific build/test commands, skill changes, and anatomy maintenance.

Nested lingtai-dev-guide reference for diagnosing LingTai failures: agent process state, OOM/crashes, avatar spawn issues, post-molt memory loss, mail delivery, scheduled messages, tool timeouts, and escalation.

Nested lingtai-dev-guide reference for known implementation footguns: Bubble Tea v2 paste, textarea theming, dev-mode rebuilds, editable installs, migrations, localization, authorization gates, config conventions, and rebuild-gate test false-passes.

Nested lingtai-dev-guide reference for getting a PR review-ready: PR readiness gates, multi-model/daemon/Claude read-only review passes, self-contained local HTML explainers, PR body hygiene and gh pr edit troubleshooting, source-labeled deliverables with syntax/validation checks, and maintainer authorization boundaries for opening, editing, and merging PRs.

Read-only workflow for sweeping the Lingtai-AI GitHub org for open issues, open PRs, and recent activity. Use this when a LingTai developer/operator asks what changed across the org, wants to monitor non-self PRs/issues, or needs an idempotent repository-health digest. This is a nested lingtai-dev-guide reference, not a top-level intrinsic skill.

Nested lingtai-dev-guide reference for developer/operator runtime self-checks after a refresh, checkout, or preset/MCP change: probe which lingtai code is actually running, confirm the editable source and git HEAD, verify the active TUI/portal binary and dev-mode symlinks, rebuild the TUI from a clean release worktree, inspect MCP/addon module sources and tool surface, and report evidence safely with secrets redacted. Includes verifying that long-lived runtime objects (services/adapters/caches) were actually rebuilt after a refresh, not just that new source is imported.

Nested lingtai-dev-guide reference for security audits: secret scanning, file permissions, MCP config, communication security, data exposure, agent permission review, severity classification, and report format.

Nested lingtai-dev-guide reference for local developer environment setup: cloning repos, building TUI/portal, dev-mode symlinks, editable kernel install, MCP addon setup, and verification.

Nested lingtai-dev-guide reference for turning one-off experience into durable skills: when to write a skill vs leave it as notes, the router-vs-nested- reference pattern, distilling experience (归一) and session journals into triggered/executable SKILL.md files, de-privatizing and parameterizing local paths and human-specific details, a lightweight pre-publish benchmark/checklist, grooming shared-library candidates, and PR-ready skill cleanup.

Router for contributing to the LingTai project. Use this when you are about to change LingTai code or docs, set up a dev environment, navigate the Go TUI/portal repo or Python kernel, develop MCP addons, troubleshoot a running network, audit security, run a runtime self-check, get a PR review-ready, or steward a new skill. This is for developers and contributors; for end-user lessons, use tutorial-guide.

Nested lingtai-issue-report reference for deciding when an observation is worth reporting, what evidence to collect, and how to keep secrets out of a report. Read this first, while the problem is fresh, before drafting the report body.

Nested lingtai-issue-report reference for the filing decision — the always-required human consent boundary, the read-only gh probe, Path A (direct gh filing) and Path B (paste-ready handoff), token hygiene, and proactive surfacing. Read this once the report is drafted and you are deciding how it gets filed.

Nested lingtai-issue-report reference for the report skeleton — subject/title format, the structured body sections (what's wrong, where, reproduction, expected vs actual, severity, suggested fix), and how to send it via LingTai email or the human's active channel. Read this when you are ready to assemble the report.

Protocol router for reporting bugs, stale info, missing capabilities, or design issues you spot in any LingTai skill, capability, preset, or system behavior. Enter through this router, then load the one nested reference you need — evidence-checklist (when to report, what evidence to collect, secret hygiene), report-template (the report body/title structure), or filing-flow (human consent, the gh CLI path, and the paste-ready fallback). You always assemble a structured report and ask the human for permission before filing.

Nested lingtai-portal-guide reference for portal lifecycle-state interpretation, heartbeat staleness, recording, and tape reconstruction behavior.

Nested lingtai-portal-guide reference for portal purpose, opening the browser view, and the `.portal/` directory layout.