mirror of
https://github.com/samber/cc-skills-golang.git
synced 2026-09-11 19:46:44 +03:00
fix(docs): correct relative asset link and skill count (#60)
- Fix broken relative path in golang-performance/references/observability.md: assets/ → ../assets/ - Fix skill count mismatch in golang-how-to/references/project-config.md: 13 → 11, ~1,400 → ~1,100 tokens
This commit is contained in:
@@ -33,7 +33,7 @@ If the block already exists, read it and confirm with the user whether to update
|
||||
|
||||
## Step 3 — Confirm the skill set with the user
|
||||
|
||||
Use `AskUserQuestion` to confirm which skills to always load. Present the ⭐️ recommended skills as the default selection. Remind the user of the token budget (each always-loaded skill adds its description tokens to every session — the 13 recommended skills add ~1,400 tokens at startup).
|
||||
Use `AskUserQuestion` to confirm which skills to always load. Present the ⭐️ recommended skills as the default selection. Remind the user of the token budget (each always-loaded skill adds its description tokens to every session — the 11 recommended skills add ~1,100 tokens at startup).
|
||||
|
||||
Recommended ⭐️ set for most projects:
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@ Third-party monitoring tools complement local profiling (pprof, benchmarks) by p
|
||||
|
||||
### Alerting rules (examples)
|
||||
|
||||
[Example alerting rules](assets/prometheus-alerts.yml) — adjust thresholds to your application; a high-throughput data pipeline will have different baselines than a lightweight API server.
|
||||
[Example alerting rules](../assets/prometheus-alerts.yml) — adjust thresholds to your application; a high-throughput data pipeline will have different baselines than a lightweight API server.
|
||||
|
||||
→ See `samber/cc-skills@promql-cli` skill for interactively testing these PromQL expressions against your Prometheus instance from the CLI.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user