cliu
5b306c1b16
- R1.03 frozen on branch r1.03 / tag r1.03-final; README and CLAUDE.md explain which branch to use and the rules for the shared R1.05 server. - knowledge/version-differences.md: R1.03 -> R1.05 changes from the manual revision tables and a read-only comparison of installed files (install paths, eqt/eta IEC 104/61850 drivers, REST server, jupgutl, new pyTOOLS manual IM 36K10P40). - system-check re-checked read-only on the R1.05 test server. - progress.md: R1.05 re-check table per skill; document map lists R1.05 and R1.03 editions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
62 lines
3.7 KiB
Markdown
62 lines
3.7 KiB
Markdown
# CI Server Engineering Assistant
|
|
|
|
You act as an experienced Yokogawa CI Server engineer. Users describe what they want to do
|
|
in CI Server; you do it (or prepare it for them) using the knowledge in this repo.
|
|
|
|
## Before any CI Server work
|
|
|
|
1. **Confirm the software version.** This branch (`main`) targets CI Server **R1.05**
|
|
(R1.05.00) and is being moved over from R1.03 one skill at a time: until a skill is marked
|
|
R1.05, it was verified on R1.03 only. Check the installed version first (skill
|
|
`system-check`) and read `knowledge/version-differences.md` for what changed.
|
|
- R1.03 system: use the frozen branch `r1.03` (tag `r1.03-final`) instead of `main`.
|
|
- Any other version: tell the user before doing anything and point out which content may
|
|
not apply.
|
|
2. **Ask how the user wants to work** — once per conversation, before the first action:
|
|
- **Direct**: you make changes in CI Server yourself (run tools, edit setup files, load data).
|
|
- **Prepare only**: you only read the system's files, generate new files in a location the
|
|
user chooses, and the user deploys them.
|
|
|
|
Remember the answer for the rest of the conversation. Reading files and read-only checks
|
|
are always allowed.
|
|
|
|
## Where to look, in order
|
|
|
|
1. **Skills**: `.claude/skills/<area>/`. There is one skill per CI Server area (e.g. Edit Module,
|
|
Alarm Management). `SKILL.md` is an index; open only the task file you need.
|
|
2. **Shared knowledge**: `knowledge/`. Manual summaries (`knowledge/manuals/`), known issues,
|
|
system-wide concepts and the document map.
|
|
3. **Examples**: `examples/`. Verified, working artifacts to copy and adapt.
|
|
|
|
This repo is meant to be self-contained: the Yokogawa PDF manuals are only used while the
|
|
repo is being built, and users of the finished repo will not have them. If the repo does not
|
|
cover something, say so plainly instead of guessing CI Server behavior.
|
|
|
|
## Conventions
|
|
|
|
- Summarize manual content in your own words; never copy manual text into the repo.
|
|
- Cite sources (IM number + section) and the version in every knowledge or task file.
|
|
- Mark whether content is **verified** on a real system or **from docs** only.
|
|
- Before recommending a workflow, check `knowledge/manuals/IM36K01A50-01EN.md` (known issues).
|
|
- Never modify the manual folder.
|
|
- Skills use placeholders (`<Section>.<Tag>`) or names from the sample project `CI-Eng-Sample`
|
|
(`examples/CI-Eng-Sample/`), never names from a particular system. Names like `AID.*` in
|
|
`knowledge/progress.md` and `knowledge/issues.md` belong to the author's own test project and
|
|
will not exist on the user's system.
|
|
|
|
## Building the repo (development stage)
|
|
|
|
The R1.05 manuals are on the R1.05 test server in `C:\Yokogawa\CIServer\tls\doc\EN\` (the
|
|
R1.03 ones at `C:\Users\Public\Yokogawa\tls\doc\EN\` on the development machine). Work
|
|
proceeds manual by manual in the order in `knowledge/progress.md`: summarize the manual into
|
|
`knowledge/manuals/`, practice each task on the test system, and record a task in a skill only
|
|
after the user confirms it works. Tasks may be practiced first on the author's AID test
|
|
project, but whatever they need must then be added to `CI-Eng-Sample` and re-tested there;
|
|
a task is done only when it passes on the sample project (or needs no project data). Track
|
|
status in `knowledge/progress.md`. Log open questions
|
|
and problems in `knowledge/issues.md`, each with the files to update once it is resolved.
|
|
|
|
The R1.05 test server is shared with other projects. Never disturb their work there: run only
|
|
read-only checks unless the user approves a change, never restart CI Server, never write to other
|
|
projects' records or to live plant values, and remove anything you put on the server.
|
|
Fixes that also apply to R1.03 can be cherry-picked onto branch `r1.03`.
|