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`.
SkillScore73Maintained
Automatic
◆Doc Ops pack
Last verified 8/19/2026
What it changes
Passed 16 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill73%
Checks it passed that the model alone missed
Directs to tui/ANATOMY.md
Directs to portal/ANATOMY.md
Directs to tui/internal/tui/ANATOMY.md
and 14 more in the full report
13 fixed3 passed either way5 still failing1 broke
Pass-rate lift
+55 pp
Tokens
-6%
Agent turns
0%
Response time
-63%
Model gemini-3.6-flashMeasured 8/19/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
Where in the anatomy graph is Portal's own process release and shutdown boundary documented?
What was checked, without and with the skill
Checked
Without skill
With skill
Directs to portal/ANATOMY.md
Missed
Passed
case-22 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md94 linessingle file
LingTai Go Anatomy — navigation guide
Canonical owner
The repository-root ANATOMY.md is both the normative anatomy-of-anatomy and the
top of the distributed code-navigation graph. Per-folder ANATOMY.md files are
the content. This bundled skill is the discoverable navigation aid: when it and
the repository root disagree, the repository root governs.
An Anatomy file maps structure, connections, composition, and state beside the
code it describes. It is not a user manual, behavior contract, design history,
or test specification. The paired root CONTRACT.md owns interfaces and expected
behavior; the repository-local dev guide owns contribution workflow.
How to navigate
Open the repository-root ANATOMY.md and read Components plus
Composition.
Choose tui/ANATOMY.md for terminal UI, subprocess launch, agent inventory,
lifecycle controls, and /viz; choose portal/ANATOMY.md for the web server,
embedded frontend, topology, and replay.
Descend to the named package Anatomy and open the cited file:line range.
Treat code as structural truth. If a citation or ownership claim drifted,
update the relevant Anatomy in the same change.
Use search for enumeration only (every callsite/file); use Anatomy for
structural ownership and data-flow questions.
Runtime-boundary route
For questions such as “Does closing the TUI stop my agent?”, “How do I attach
again?”, “Who owns lifecycle?”, or “Should I add launchd?”:
Start at root ANATOMY.md → tui/ANATOMY.md, section
Runtime/control-surface boundary.
Follow its same-repo anchors for normal Bubble Tea quit, kernel subprocess
launch and duplicate-process prevention, startup attachment, explicit
/sleep//suspend//cpr//refresh, inventory, and Portal process release.
Use portal/ANATOMY.md for Portal's own process and shutdown boundary.
Load lingtai-kernel-anatomy for exact kernel heartbeat, listener, signal,
and lifecycle internals. Do not cite sibling-repo files from TUI Anatomy.