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