Update vive architecture documentation in Claude Code
Follow vive's mapping from code changes to concept, architecture, or requirements docs, then check against implementation and tests.
中文Install in Claude Code
The vive workspace in Claude Code. Determine whether the change affects internal architecture or the interface structure before applying its documentation map.
- Review `.claude/skills/doc-update/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/doc-update/` in your project and save the reviewed file as `.claude/skills/doc-update/SKILL.md`.
- Start Claude Code from that project's root, then select `/doc-update` in the slash menu.
Example task
The fictional change moves terminal filter rendering into a new tui module without altering user behavior or options. The fixture is `{change:'move filter renderer',area:'tui',behavior:'unchanged'}`.What to check
Update the terminal-interface section of architecture.md to record `filterRenderer=tui`. Keep the requirements status and confirm that tests still describe the same filtering behavior.
Original SKILL.md on GitHub · Updated
Frequently asked question
Which vive document covers a terminal interface layering change?
Use the architecture guide for interface layering and module organization. Revisit requirements when features or command-line options change, then check that the implementation and tests match.