## Summary - `graphics/tasks/layouts.md` §6: tested reference of every `Layouts.xml` parameter for the Operator Interface (desktop) and the HTML display (web) — frames, window options, menu/toolbars/status line, all commands, popups/modal/maximumOpen, translations, debug key, tabs. - New rules: web-compatible frame shape (one `n*` per frame set, nested frame set only in that slot), `type="check"` required for `toolbar`/`statusline`/`playback record` (else the desktop client does not start), profile initial display replaces `initialDisplay` of frame `default`, always set `title`. - Issues ISS-062..067 (readme differences and web limits), progress row, skill index. ## Test plan - [x] 5 rounds of test layouts (`LT_*`) in a marked block of `Layouts.xml`; desktop via `jwuipoi -layout <name>` with window captures/recorder, web via `?d=…&l=…` in the browser and the web client code (CI Server R1.03.00). - [x] Launcher display `LT_Launcher` for layouts opened from a display. - [x] Clean-up: test system restored to its pre-test state; `LT_Launcher` removed. - [ ] Not tested: print orientation/margins, playback, second-screen positions, `maximumTabs` limit for new tabs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: cliu/ci-server-config#23 Co-authored-by: cliu <cliu@noreply.git.yokogawa.tech> Co-committed-by: cliu <cliu@noreply.git.yokogawa.tech> |
||
|---|---|---|
| .. | ||
| alarm-management | ||
| audit-trail | ||
| authorization | ||
| class-object-engineering | ||
| data-access | ||
| equipment | ||
| graphics | ||
| high-availability | ||
| history-management | ||
| installation-security | ||
| item-engineering | ||
| portal-setup | ||
| reporting | ||
| system-check | ||
| system-management | ||
| README.md | ||
Skills
One skill per CI Server area, following knowledge/document-map.md. Nested skill folders
are not used for grouping; group tasks inside each skill instead:
<area>/
├── SKILL.md # frontmatter (name, description with task keywords) + task index
├── tasks/ # one file per task
└── reference/ # area-specific details
The description in SKILL.md decides when Claude uses the skill. List the words users
will actually say.
Skills must work on any R1.03 system, so never use names from a particular system (items,
sections, stations, nodes). Write placeholders such as <Section>.<Tag> and, where an example
helps, use names from the sample project CI-Eng-Sample (examples/CI-Eng-Sample/).
Test-system evidence belongs in knowledge/progress.md and knowledge/issues.md.