Refresh Project Knowledge Skills
Scan the codebase and update all knowledge skills in .claude/skills/ with current information.
Instructions
For each skill listed below, read the source-of-truth files, compare against the current SKILL.md content, and update anything that is stale, missing, or incorrect. Preserve the YAML frontmatter (name, description, user-invocable, disable-model-invocation) but update the description if the scope changed.
Do NOT rewrite skills that are already accurate. Only touch what changed.
Skills and their source-of-truth files
| Skill | Read these files to refresh |
|---|---|
| architecture | docs/architecture-overview.md, src/signaldb-bin/src/main.rs, Cargo.toml (workspace members) |
| storage-layout | docs/design/storage-layout.md, src/common/src/storage.rs, src/common/src/wal/mod.rs, src/common/src/catalog_manager.rs, src/common/src/schema/iceberg_schemas.rs |
| flight-schemas | schemas.toml, src/common/src/flight/schema.rs, src/writer/src/schema_transform.rs, src/common/src/schema/schema_parser.rs, src/common/src/schema/iceberg_schemas.rs |
| multi-tenancy | src/common/src/auth.rs, src/common/src/config/mod.rs, src/router/src/admin.rs, docs/architecture-overview.md (Multi-Tenancy section) |
| service-discovery | docs/design/service-discovery.md, src/common/src/catalog.rs, src/common/src/service_bootstrap.rs, src/common/src/flight/transport.rs |
| dev-workflow | CLAUDE.md, .serena/memories/task_completion_checklist.md, scripts/run-dev.sh, docker-compose.yml |
| rust-patterns | docs/ai/rust.md, docs/ai/development.md, Cargo.toml (edition, rust-version, workspace.dependencies) |
| crate-map | Cargo.toml (workspace members), then src/*/src/lib.rs or src/*/src/main.rs for each crate to check module structure |
| adding-new-signal | Cross-reference with architecture, flight-schemas, and storage-layout skills for consistency |
| tempo-api | src/router/src/tempo.rs, src/router/src/admin.rs, src/grafana-plugin/ |
| configuration | src/common/src/config/mod.rs, signaldb.dist.toml, docs/architecture-overview.md (Configuration section) |
Refresh procedure
- •Read all source-of-truth files for a skill (batch reads where possible)
- •Read the current SKILL.md
- •Diff mentally: are there new fields, renamed modules, changed ports, new config options, new endpoints, removed features?
- •If changes found: edit the SKILL.md with minimal, targeted updates
- •If no changes: skip, report "up to date"
- •After all skills are checked, report a summary of what changed
What to look for
- •New workspace members added to
Cargo.toml - •New or renamed modules in any crate
- •Schema changes in
schemas.toml(new fields, new versions, new signal types) - •New config options in
src/common/src/config/mod.rs - •New API endpoints in router
- •Port changes in any service
- •New dependencies that affect patterns (e.g., new error handling crate)
- •Rust edition or MSRV changes in
Cargo.toml - •New Flight RPC methods or query types
Output format
After refreshing, print a summary like:
code
Skills refresh complete: - architecture: updated (added new Querier port, updated deployment notes) - storage-layout: up to date - flight-schemas: updated (new log schema v2 fields) - ...