Router for contributing to the LingTai project. Use this when you are about to change LingTai code or docs, set up a dev environment, navigate the Go TUI/portal repo or Python kernel, develop MCP addons, troubleshoot a running network, audit security, run a runtime self-check, get a PR review-ready, or steward a new skill. This is for developers and contributors; for end-user lessons, use tutorial-guide.
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 9/20/2026
What it changes
Passed 21 of 23 test cases with the skill, and 3 of 23 without it.
Without skill13%
With skill91%
Checks it passed that the model alone missed
routes known footguns to reference/gotchas/SKILL.md
routes environment setup to reference/setup/SKILL.md
recommends skills-manual for limit-aware authoring mechanics
and 20 more in the full report
18 fixed3 passed either way2 still failing0 broke
Pass-rate lift
+78 pp
Tokens
+88%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 9/20/2026v421 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 18
Prompt
A new developer just joined and needs to set up a local development environment for the Go TUI portal and Python kernel. Which nested reference file contains the setup instructions?
What was checked, without and with the skill
Checked
Without skill
With skill
routes environment setup to reference/setup/SKILL.md
Missed
Passed
case-15 · gemini-3.6-flash · 9/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md207 linessingle file
LingTai Developer Guide
The cross-repository developer router for LingTai. The root stays short on
purpose; detailed procedures live under reference/<topic>/.
Before using this guide, look for developer guidance maintained by the current
repository and read it first. When it exists, follow it for repository-specific
rules; it takes precedence over this global guide. Use this guide afterward — or
when the local guide routes here — to select the deeper cross-repository topic
you need, then read that nested reference before touching code. Do not substitute
generic procedures here for local guidance, or restate local rules from memory.
Non-negotiable rules
Progressive disclosure: router → nested reference → anatomy skill → code +
tests. Never jump from memory straight to edits.
Code is truth: reference files route and summarize; cited source files,
tests, and ANATOMY.md files are authoritative.
Anatomy travels with code: if you move/rename/split/delete code cited by an
ANATOMY.md, update the anatomy in the same commit, following the ANATOMY
frontmatter contract below.
Explicit human authorization gates: do not open/merge PRs, push commits,
file issues, close/delete resources, or change config unless the human gave an
imperative authorization for that side effect.
Human-facing deliverables prefer HTML: substantial plans, audits, release
notes, and PR-readiness reports should be standalone HTML unless waived.
Release/install docs rule: LingTai runtime is normally managed by the
TUI-created project venv; do not present bare pip install/upgrade lingtai as
the standard user path. Manual pip/venv commands are for developer,
diagnostic, or verification contexts only.
Patch-to-self ownership rule: a merged PR or rebuilt checkout is not
automatically live in the agent. The update/build owner must identify the
actual runtime interpreter, imported source/package, HEAD/version, and intended
selectors, then hand off the cutover target evidence. Kernel system-manual →
reference/refresh-precheck/SKILL.md alone owns the refresh transaction and
targeted receipt. Load reference/runtime-self-check/SKILL.md only for the
relevant provenance assertion or a suspected mismatch; an ordinary
same-runtime reload does not invoke its deep diagnostic library.