Document LingTai's internal memory, filesystem, and runtime anatomy.
npx skills add https://github.com/huangzesen/lingtai --skill lingtai-anatomy
Please help me install this Agent Skill. Skill: lingtai-anatomy Source: https://github.com/huangzesen/lingtai/tree/main/tui/internal/preset/skills/lingtai-anatomy Command: npx skills add https://github.com/huangzesen/lingtai --skill lingtai-anatomy
This reference documents LingTai's internal architecture—memory, filesystem, and runtime—so engineers can reason about knowledge flow, state, and turn behavior without executing actions.
Read the anatomy reference to understand how LingTai stores memory, filesystem, and runtime state.
High-intent search queries and answers about installing and using this skill.
LingTai's architecture organizes state across a durability hierarchy for memory and a filesystem layer for manifests, system prompts, history, mailboxes, and logs. This structure enables engineers to trace knowledge flow and state transitions without executing agent actions.
Debugging LingTai prompt behavior and molt mechanics involves loading the anatomy reference into your system prompt to reason about the runtime turn loop, signal lifecycle, and mail delivery interactions across memory and filesystem layers.
Yes, the anatomy reference maps cross-layer interactions among memory stores, manifests, and mailbox systems. It provides structured architectural knowledge across runtime, memory, and filesystem layers to support state and turn behavior analysis.
Loading the anatomy reference into the system prompt is the intended method for reasoning about LingTai runtime state. It supplies the architectural context needed to analyze turn loops, signal lifecycles, and molt behavior without triggering execution.
Unexpected state transitions during the turn loop often stem from cross-layer interactions among memory stores, manifests, and mailbox systems. Reviewing the runtime anatomy covering signal lifecycle and molt mechanics clarifies these behaviors.
LingTai's filesystem structures include dedicated areas for manifests, system prompts, history, mailboxes, and logs. These filesystem components store the persistent state and runtime data required for agent execution and debugging.
seantempestaManage Seon runtime configuration and context-loading via EDN manifests.
Soul-Brews-StudioStore per-agent findings, context, and standing orders across sessions.
gountharExplain Shelby Protocol architecture for decentralized blob storage on Aptos.
blackpwnguinStream live PAI multi-agent activity and debugging traces via WebSocket.
