skills.rest
Lingtai-AI
Lingtai-AIOFFICIAL
Explore all skills by this author →
GitHub

lingtai-tui-anatomy

Navigate the LingTai Go monorepo structure through its distributed ANATOMY.md documentation graph.

692|60|Updated Mar 15, 2026
Search Tags:#code navigation#tui#Documentation#Monorepo#GO#ARCHITECTURE#anatomy
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-tui-anatomy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lingtai-tui-anatomy
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-tui-anatomy
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-tui-anatomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers working in the LingTai Go monorepo (which ships lingtai-tui and lingtai-portal) struggle to locate which package owns a given behavior, understand the runtime boundary between UI processes and the kernel agent runtime, and keep per-folder ANATOMY.md files accurate. This Skill provides a discoverable navigation route into the repository's distributed anatomy graph without duplicating it.

Core Features & Use Cases

  • Question-to-node routing: Maps structural questions (TUI startup, lifecycle commands, Portal topology, agent inventory) to the exact ANATOMY.md file that owns the answer.
  • Runtime-boundary guidance: Explains that TUI and Portal are control/presentation processes, not the kernel agent runtime, so closing the UI does not stop agents and no launchd supervisor is required.
  • Citation discipline for maintainers: Defines rules for updating Anatomy files, including repo-root-relative file:line citations, reciprocal parent/child links, and post-edit verification steps.
  • Use Case: When asked "Does closing the TUI stop my agent?", follow the route from root ANATOMY.md to tui/ANATOMY.md's runtime-boundary section, then defer kernel internals to lingtai-kernel-anatomy.

Quick Start

Ask the agent to use the lingtai-tui-anatomy skill to find which package owns TUI agent lifecycle commands and show the relevant ANATOMY.md section.

Frequently Asked Questions about lingtai-tui-anatomy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which package owns a feature in the LingTai Go monorepo?▼

Start at the repository-root ANATOMY.md and read its Components and Composition sections, then descend to tui/ANATOMY.md or portal/ANATOMY.md and the named package Anatomy. Use search only for enumeration; use Anatomy for structural ownership questions.

Does closing the TUI stop my running LingTai agent?▼

No. The TUI and Portal are control and presentation processes, not the kernel agent runtime, so normal UI exit is not an agent lifecycle action. The runtime-boundary section of tui/ANATOMY.md documents subprocess launch, attachment, and lifecycle commands.

Do I need launchd or a supervisor to keep LingTai agents alive?▼

No. Ordinary agent persistence does not require launchd because the kernel owns agent lifecycle independently of the UI. Adding an external supervisor can race the existing duplicate-launch guard instead of helping.

How do I list running LingTai agents and their locations?▼

Run lingtai-tui list --detailed, adding --admin when admin fields matter, or use the interactive /projects view. For the underlying source, descend to tui/ANATOMY.md and the inventory and processscan package Anatomy nodes.

What are the rules for updating an ANATOMY.md file?▼

Cite repo-root-relative paths with verified line ranges, keep parent/child links reciprocal, never cite sibling lingtai-kernel files, and record only real structural ownership facts. After edits, run the architecture smoke tests, citation checks, and verify each changed citation.

Where do kernel heartbeat and lifecycle internals get documented?▼

Kernel internals such as heartbeat loops, listeners, signal handling, and agent lifecycle belong to the separate lingtai-kernel-anatomy skill in the kernel repository. TUI Anatomy routes there narratively rather than copying or citing Python implementation files.

Related Skills

Explore More Software Engineering Skills→
swat9013swat9013

ghq

Manage local Git repositories with centralized clone, list, and import operations.

Community
Intermediate
otto-assistantotto-assistant

lintcn

Compile Go-based custom lint rules into a tsgolint binary for TypeScript codebases.

Official
Advanced
huangzesenhuangzesen
621

lingtai-anatomy

Document LingTai's internal memory, filesystem, and runtime anatomy.

Community
Advanced
dojoenginedojoengine
1

rust-symbol-analyzer

Analyze Rust codebases to enumerate modules, structs, traits, enums, and functions via LSP symbols.

Official
Advanced