# Lingtai Manual

> Read before changing character/identity in `system/lingtai.md`, choosing forced versus self-evolve mode, or applying durable identity edits.

- Skill: `lingtai-ai/lingtai-manual` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lingtai-ai/lingtai-manual`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lingtai-ai/lingtai-manual/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lingtai-ai (https://skillmd.com/u/lingtai-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lingtai-ai/lingtai-manual

---


# LingTai Manual

LingTai (`灵台`) is the character that distinguishes this agent from others.
Its durable source is `system/lingtai.md`; reconstruction renders it into the
protected `character` prompt section.

## Public call

```text
psyche(action="lingtai", input={}, reasoning="load identity guidance")
```

This is the only public LingTai call and only returns this manual. It performs no
disk or prompt mutation; there is no update, load, or reload action or alias.

## Change durable identity

Rewrite with
`file(action="write", input={"file_path": "system/lingtai.md", "content": "..."}, reasoning="rewrite identity")`
or make a bounded exact change with
`file(action="edit", input={"file_path": "system/lingtai.md", "old_string": "...", "new_string": "...", "replace_all": null}, reasoning="edit identity")`.
Preserve all character content you intend to keep when rewriting.
Neither hot-loads the prompt; use one
`context(action="rebuild", input={}, reasoning="apply identity change")`.

- **Self-evolve:** an absent or empty **resolved** `lingtai` value (inline or
  from `lingtai_file`) preserves and composes the self-authored file. These
  inputs belong to top-level `init.json`, not `settings/psyche.json`.
- **Forced:** a nonempty configured identity materializes into the file on every
  reconstruction, so a file edit is replaced at the next rebuild, refresh, or
  molt.

Keep character separate from operator `covenant`, third-party `base_prompt`, and
mechanical `identity`; names remain `system(action="name_set"|"name_nickname")`.
Before molt, update identity only when the task's lessons genuinely changed who
you are, then use `context-manual` for the journal/summary/molt procedure.