Mandatory repository-local development guide for LingTai's Go repository — the two binaries lingtai-tui and lingtai-portal plus the install pipeline. Use this before changing code, architecture documents, tests, packaging, capabilities, adapters, or developer documentation in this repository. Routes each task through…
Router for contributing to LingTai. Use when changing code or docs, setting up a dev environment, navigating the TUI/portal repo or Python kernel, developing MCP addons, troubleshooting a running network, auditing security, running a runtime self-check, prepping a PR review, or stewarding a new skill. For developers…
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/tokenledger.jsonl, the exact formula (sum(cached)/sum(input) per window), timestamp/timezone…
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…
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…
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…
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…
Protocol router for reporting bugs, stale info, missing capabilities, or design issues in any LingTai skill, capability, preset, or system behavior. Enter through this router, then load the one nested reference you need — evidence-checklist, report-template, or filing-flow. You always assemble a structured report and…
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.
Reference router for lingtai-portal internals — startup/opening, .portal/ files, topology/replay APIs, network response shape, and lifecycle/recording. Use when the human asks about visualization, network history, or the portal.
Dual-axis router for built-in preset questions: which of the 13 TUI-shipped provider templates, and which cross-cutting lifecycle mechanic — saving, checking availability, activating/refreshing, endpoint/capability facts, or troubleshooting. Read a child only when relevant; this does not describe arbitrary saved…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: