enhance xce-build skill

CLAUDE.md

@@ -8,20 +8,26 @@ This project uses OpenWolf for context management. Read and follow .wolf/OPENWOL
 # XCE Cluster Management System
 
 ## Overview
-XCE is an HPC cluster management system providing job scheduling, queue management, and cluster resource control. The Go-based API/CLI tier fronts C/C++ system daemons (controller, worker, scheduler).
+XCE is an HPC cluster management system providing job scheduling, queue management, and cluster resource control. The Go-based API/CLI tier fronts C system daemons (controller, worker, scheduler).
 
 ## Tech Stack
 - **Go 1.23.4**: REST API server (`src/frontend/apiserver`), CLI tool (`src/frontend/xcecli`)
-- **C/C++**: Core daemons — controller, worker, scheduler, shared lib
+- **C (gnu17)**: Core daemons — controller, worker, scheduler, shared lib
 - **Build**: Meson + Nix flakes for C components; `make` for Go components
 - **Go key deps**: Gin v1.10.0, JWT v4, Zap logging, Viper config, Cobra CLI
 
 ## Development Commands
 ```bash
-# Full dev build — all components (debug + ASAN)
-/xce-build                                       # Preferred: builds everything via nix develop + meson
+# Build with /xce-build skill (debug + ASAN, clean build, runs tests)
+/xce-build                  # Build all components + run all tests
+/xce-build lib              # Build libxce + run lib tests
+/xce-build controller       # Build lib + controller + run controller tests
+/xce-build scheduler        # Build lib + scheduler + run scheduler tests
+/xce-build worker           # Build lib + worker (no unit tests registered)
+/xce-build apiserver        # Build lib + apiserver + xcecli + run Go unit tests
+/xce-build xcecli           # Build xcecli only + run xcecli Go tests
 
-# From src/frontend/
+# From src/frontend/ (manual Go dev loop)
 make build-server       # Build apiserver binary → /tmp/apiserver
 make build-cli          # Build xcecli binary → /tmp/xce_static (CGO_ENABLED=0)
 make test               # Unit tests (no live server required)
@@ -156,7 +162,7 @@ Kiro-style Spec-Driven Development on an agentic SDLC
   - `/kiro-spec-design {feature} [-y]`
   - `/kiro-validate-design {feature}` (optional: design review)
   - `/kiro-spec-tasks {feature} [-y]`
-- Phase 2 (Implementation): `/kiro-spec-impl {feature} [tasks]`
+- Phase 2 (Implementation): `/kiro-impl {feature} [tasks]`
   - `/kiro-validate-impl {feature}` (optional: after implementation)
   - `/kiro-verify-completion {feature}` — validate all acceptance criteria are met
 - Debugging: `/kiro-debug {feature}` — systematic debugging with spec context