- 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> |
||
|---|---|---|
| .. | ||
| 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.