From infynon-trace
Manages canonical (validated, durable) memory in INFYNON Trace for architecture decisions, API contracts, promotion flows, and auditing notes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/infynon-trace:canonical-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Activate this skill when:
Activate this skill when:
Canonical memory is the smallest, most durable layer in Trace's three-tier system. It stores knowledge that has been deliberately validated and is intended to be trusted across the team.
Not all memory should be treated equally. "Truth memory which is always correct" is too strong a promise. Even canonical memory can become outdated when code changes. Use "canonical" or "validated" — never promise "always correct."
| Category | Example |
|---|---|
| Architecture decisions | "All auth flows go through middleware" |
| Stable API contracts | "POST /users returns 201 with Location header" |
| Config invariants | "Rate limit is always per-IP, never global-only" |
| Known security constraints | "Tokens are RS256 signed, never HS256" |
| Canonical module facts | "Error handling uses InfynonError enum via thiserror" |
| Migration rules | "All DB migrations must be backwards-compatible for 2 releases" |
A note should only enter canonical after:
# Find notes tagged for promotion
infynon trace retrieve --tag promote
# Or find long-lived, frequently-referenced team notes
infynon trace retrieve --layer team --tag architecture
Before promoting, verify:
infynon trace note add canonical-<topic> \
--title "<Clear, factual statement>" \
--body "<Details with validation evidence. Include: which PRs validated this, since which version, any constraints.>" \
--layer canonical \
--scope repo \
--tags <relevant-tags>
infynon trace note update <original-id> --status archived
Every canonical note should include in its body:
<Factual statement>
Validated: PRs #X, #Y, #Z
Stable since: vX.Y.Z
Constraints: <any conditions under which this might change>
Last verified: <date>
Canonical notes can go stale. Regularly audit:
# List all canonical notes
infynon trace retrieve --layer canonical
# Check for stale canonical notes
infynon trace retrieve --layer canonical --tag stale
For each canonical note, ask:
updated_at?If stale:
# Mark as stale for review
infynon trace note update <id> --status stale
# Or archive if no longer valid
infynon trace note update <id> --status archived
infynon trace retrieve --layer canonical at session start to ground yourselfnpx claudepluginhub d4rkninja/code-guardian --plugin infynon-traceStores, recalls, queries, and audits durable project knowledge as file-backed entries and a working notepad that survives conversation compaction.
Manages SSOT, project memory, and cross-tool memory search. Handles decisions.md, patterns.md, SSOT promotion, migration, merging, and sync. Use to save learnings or search past decisions.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.