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 the exact baseline, the distributed ANATOMY/CONTRACT systems, focused validation, and pull-request safety gates.
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
Without skill32%
With skill73%
Checks it passed that the model alone missed
executes go test -run TestArchitecture ./...
specifies the path pattern .worktrees/<slug>/
specifies reading ANATOMY.md before reading CONTRACT.md
and 7 more in the full report
10 fixed6 passed either way5 still failing1 broke
Pass-rate lift
+41 pp
Tokens
+76%
Agent turns
0%
Response time
-54%
Model gemini-3.6-flashMeasured 8/19/2026v116 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
You updated component node mappings in `tui/ANATOMY.md` and want to run the specific Go test target designed for architecture validation. What exact Go test command should be executed?
What was checked, without and with the skill
Checked
Without skill
With skill
executes go test -run TestArchitecture ./...
Missed
Passed
case-13 · 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.md157 linessingle file
LingTai TUI/Portal Development
Read this skill before every development task in this repository. It owns the
workflow, not the architecture facts or interface promises. Follow its links
instead of copying the root documents into this file. This repository ships the
Go side of LingTai: lingtai-tui, lingtai-portal, and install.sh. The
Python kernel lives in the sibling lingtai-kernel repository and is launched
as a subprocess; this repository never imports it.
First establish the task and baseline
Re-read the latest human or maintainer instruction. Separate the requested
change from suggested follow-up work and from unauthorized side effects.
Name the selected baseline: normally live origin/main, or an explicit tag
or commit chosen by the maintainer.
Work in a real repository worktree. Before analysis or editing, prove the
worktree is clean and HEAD equals the selected baseline. A directory name
or recorded SHA without equality is not enough. This repository's convention
is .worktrees/<slug>/ on a fresh branch off origin/main.
Use a focused branch and keep unrelated local/runtime worktrees untouched.
Both this repository and its sibling kernel see concurrent branches and
stashed WIPs; editing the main checkout has repeatedly lost in-flight work.
See README.md and CLAUDE.md for the public
orientation and the Claude Code entry rules that route here.
Read the distributed systems before editing
Use progressive disclosure in this order:
Read root ANATOMY.md, then descend through the nearest
child anatomy (tui/ANATOMY.md, portal/ANATOMY.md, or a per-package
anatomy) until cited code answers where the relevant files, connections,
composition, and state live.
Read root CONTRACT.md. If the component is governed, read
its paired local contract before changing its interface or expected behavior.
Read the cited code and narrow tests. Anatomy is navigation, not evidence in
place of code; Contract is the normative promise, not a description to weaken
when implementation drifts.
Load a narrower manual only when the task needs its commands, examples, or