- layouts.md: tab set must be the last child of its frame set (web); desktop tab frames ignore zoom (navigate ... stretchDisplay); web activates the last tab loaded; web tab labels = display title; one layout command at a time; connectionState breaks the web layout (corrects 6.3); per-user layout verified on desktop and web - create-display.md: new section "Writing display XML directly" (text size, rounding, arc angles clockwise on both clients, Clicked b1, web item attributes, asDateTime, server-side command as CIX_PROCESS with group OPERATOR, alarm overview columns / white area) - deploy-displays.md: 8-display sample scripts; jwuiutl -v re-saves files - trend.md: CIENG_TrendLab as history, cieng_feed.ps1, 50-pen hairline trade-off, component opaque, micro trend "Record not found" without history - users-groups.md: PASSWORD "" for an empty password; sample user CIENG; open session blocks group removal (DSSSDA03 stopped) - configure-audit.md, L25 / R30 / C50 summaries, SKILL.md, issues ISS-068..075, progress rows - Every statement tested on CI Server R1.03.00 2026-10-02..06 (desktop and web, test display and test layouts removed afterwards) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 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.