lingtai-tui-dev

Guides development workflow for LingTai's Go binaries through baseline, validation, and PR gates.

692|60|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-tui-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lingtai-tui-dev
Source: https://github.com/Lingtai-AI/lingtai/tree/main/dev-guide-skill
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-tui-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contributing to the LingTai Go repository (lingtai-tui, lingtai-portal, install.sh) requires navigating distributed ANATOMY and CONTRACT documentation systems, shared on-disk state compatibility between two binaries, and strict pull-request safety gates. This Skill routes every development task through the correct baseline, documentation, validation, and authorization steps so changes stay consistent and reviewable.

Core Features & Use Cases

  • Baseline and Worktree Discipline: Establishes the task scope, verifies the worktree HEAD equals the selected baseline (normally origin/main), and enforces focused branches under .worktrees/.
  • Distributed Documentation Routing: Directs progressive reading of root ANATOMY.md and CONTRACT.md plus per-package anatomy/contract files before editing, and requires updating them in the same PR when structure or interfaces change.
  • Layered Validation and PR Gates: Prescribes Go test/vet runs, the anatomy citation scan, portal web builds, and a pre-commit checklist covering authorization, author identity, and staged diff review.
  • Use Case: Before modifying the portal's handling of a shared .lingtai/ state field, follow this Skill to confirm the baseline, read the relevant contract, keep lingtai-tui and lingtai-portal migration versions in lockstep, run focused tests, and open an authorized pull request.

Quick Start

Ask the agent to follow the lingtai-tui-dev guide to implement and validate a small change to the lingtai-portal codebase on a fresh branch off origin/main.

Frequently Asked Questions about lingtai-tui-dev

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

FAQPage Schema
How do I start a development task in the LingTai Go repository?

Re-read the latest maintainer instruction, name the baseline (normally origin/main), and create a clean worktree under .worktrees/ on a fresh branch. Verify HEAD equals the selected baseline before any analysis or editing.

What are ANATOMY.md and CONTRACT.md files used for?

ANATOMY.md documents where code lives and how it connects, while CONTRACT.md defines normative interface and behavior promises. Read the root files first, then descend to per-package versions before changing governed components.

How do I validate Go changes in lingtai-tui and lingtai-portal?

Run go test and go vet in both the tui and portal modules, plus git diff --check. When architecture graphs change, also run the TestArchitecture test and the anatomy citation scan; portal changes need the npm web build.

Do lingtai-tui and lingtai-portal need mirrored implementations?

No, only shared state is a cross-binary obligation. Changes to .lingtai/ fields or the shared meta.json migration version read by both binaries must stay compatible, but binary-specific state like portal-only .portal/ data does not require mirroring.

Can I push directly to main or merge my own pull request?

No, always use a pull request and never push directly to main. Commits, pushes, merges, releases, and configuration changes each require explicit maintainer authorization, and opening a PR does not imply permission to merge it.