cliu
e26d610e89
V1 eqpdbg main info and V2 setup_check.ps1 run read-only on the R1.05 test server (temporary copy deleted). setup_check.ps1 counted program-limited 'any port' rules (e.g. Remote Desktop Shadow) as allowing the CI Server ports; now only port rules or any-port rules without a program limit count. V3 checked in the installed form definitions. 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.