ci-server-engineer/.claude/skills
cliu a298fdebc1 Layouts: every Layouts.xml parameter tested on desktop and web (#23)
## 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>
2026-10-02 22:26:29 +10:00
..
alarm-management Add alarm manual summaries (L15, C20, E30) and alarm-management skill 2026-10-01 11:41:45 +10:00
audit-trail ISS-049: operator writes audited per AUDIT_INFO; mode buttons on CIENG_Tank, 19b_audit_item_df 2026-10-01 18:57:44 +10:00
authorization Add login-methods and active-directory tasks to the authorization skill 2026-10-01 19:12:45 +10:00
class-object-engineering ISS-028: Engineering Module class reset verified 2026-10-01 18:23:43 +10:00
data-access Add RDBMS data exposure task to the data-access skill (tested in R1.05 only) 2026-10-02 14:47:33 +10:00
equipment Add data-access skill, BUS utilities task and licence run-time notes 2026-10-01 10:46:28 +10:00
graphics Layouts: every Layouts.xml parameter tested on desktop and web (#23) 2026-10-02 22:26:29 +10:00
high-availability Add high-availability skill (HAC checks, redundant set-up, stand-alone recovery) 2026-10-01 19:12:44 +10:00
history-management Issue review: forced rollover limit; ISS-005 and ISS-027 ready to close 2026-10-01 18:12:52 +10:00
installation-security Record RDBMS exposure in manual summaries, progress and issues ISS-057..061 2026-10-02 14:47:33 +10:00
item-engineering Issue review: test ISS-011, ISS-020, ISS-022, ISS-025; unlicensed shutdown after 1 h 10 min 2026-10-01 17:52:25 +10:00
portal-setup Add phase 4 CI Portal setup and Setup File Editor summaries, portal-setup skill 2026-09-30 16:41:02 +10:00
reporting ISS-048: report item prompt filter works (ITEM_DF filter on items) 2026-10-01 18:35:28 +10:00
system-check Issue review: test ISS-011, ISS-020, ISS-022, ISS-025; unlicensed shutdown after 1 h 10 min 2026-10-01 17:52:25 +10:00
system-management Issue review: reproduce ISS-038, forced rollover limit, ISS-005/027 ready to close 2026-10-01 18:12:38 +10:00
README.md Add phase 0-1 knowledge and system skills 2026-09-30 13:07:37 +10:00

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.