cliu
070e578129
Summarize the Release Information (known issues) and System Design/Management manuals, add the system-check and system-management skills practiced on the R1.03 test system, and add the progress tracker, issue register and a CI-Eng-Sample placeholder. CLAUDE.md now requires a version check, asks once per conversation whether to work directly or prepare files only, and treats the manuals as development-only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 lines
832 B
Markdown
19 lines
832 B
Markdown
# 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`.
|