No description
Tested on the R1.05 test server 2026-10-09..12 with a user project (own objects only); not yet on CI-Eng-Sample (ISS-188). Only results that were tested are included; inferences, code-only and manual-only points and the untested sample layout change were left out. - layouts: 'logout' is a secondary logout, always disabled on the R1.05 web client; 'exit' closes the window and ends the session (ISS-182). - create-display: R1.05 web client table (String items in text vs textField, fixed text alignment, start-hidden limits ISS-183, two visibility conditions, On entry display actions, rectangle blinking, verified connections, first load). - java-class 4a: signal arrays at scale, write on change, attribute arrays, offline javac/javap check; change-reset-class: new signals need the object recreated, attributes lost (ISS-185); opcdbg reset in cmd, TRIGGER_1 via dssqld -m. - string-items (ISS-187), users-groups, modbus-station (400 registers, comm loss), export-dataset (NAME range filter), item-alarming. - new task system-management/package-project.md; tools/ModbusSim.java (tested on R1.05: FC03/04/06/16, exceptions, modes); AMSI (ISS-186). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/skills | ||
| examples | ||
| knowledge | ||
| tools | ||
| CLAUDE.md | ||
| README.md | ||
ci-server-engineer
A knowledge base that lets Claude Code work as a Yokogawa CI Server engineer. Open this repo in Claude Code and describe what you want to do in CI Server.
Versions
| CI Server | Use | Status |
|---|---|---|
| R1.05 | branch main |
Being moved over from R1.03 one skill at a time; see knowledge/version-differences.md and knowledge/progress.md |
| R1.03 | branch r1.03 (tag r1.03-final) |
Frozen; only fixes are added |
For an R1.03 system, check out the r1.03 branch, or keep it next to main as a separate
folder: git worktree add ../ci-server-engineer-r1.03 r1.03.
Layout
| Path | Contents |
|---|---|
CLAUDE.md |
Always-loaded instructions: role, version, where to look |
.claude/skills/ |
How to do things. One skill per CI Server area; each task is its own file |
knowledge/ |
Shared reference. Document map, glossary, known issues, cross-area concepts |
examples/ |
Verified, working artifacts (class descriptions, reports, scripts) |
tools/ |
Helper scripts Claude can run (e.g. the setup check) |
Prerequisites
Using the repo needs no manuals: the knowledge is in knowledge/ and .claude/skills/.
Only to extend the repo (summarize a manual, check a citation) you need the CI Server EN
manuals locally. They are not stored in this repo. They are installed in tls\doc\EN\ under
the CI Server data folder (%TLS_ALLUSERS_PATH%): C:\Yokogawa\CIServer\tls\doc\EN\ on the
R1.05 test server, C:\Users\Public\Yokogawa\tls\doc\EN\ on the R1.03 machine.
Contributing
- Add task knowledge under the matching skill:
.claude/skills/<area>/tasks/<task>.md, and add a row to that skill'sSKILL.mdindex. - Write in your own words, cite the manual (IM number + section) and the version, and mark the content as verified or from docs.