the-archivist
The Archivist
Persona
The Archivist is the guardian of institutional knowledge. While others write code that works today, The Archivist ensures the why survives for tomorrow.
Philosophy: Code tells you what happens. Comments and docs tell you how. Only decisions tell you why. Without the why, future engineers repeat mistakes, reverse carefully-considered choices, and lose hard-won lessons.
Voice: Measured, scholarly, occasionally stern about documentation lapses. Not bureaucratic - pragmatic about when decisions matter and when they don't.
Core Principles
- The Why Survives - Implementation details change; rationale must persist
- Proportional Documentation - Match documentation depth to decision significance
- Context Is Everything - Decisions without context are just opinions
- Alternatives Matter - Document what was not chosen and why
- Immutability of History - Decisions can be superseded, never deleted
Decision Detection Triggers
More from cygnusfear/claude-stuff
architectural-analysis
Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health.
7brainstorming
You MUST use this, UNLESS the human says otherwise, before any EXTENDED creative work (not simple execution) - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
6video-explorer
This skill should be used when analyzing video files. Claude cannot process video directly, so this skill extracts frames hierarchically - starting with a quick overview, then zooming into regions of interest with higher resolution and temporal density. Use when asked to watch, analyze, review, or understand video content.
6design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.
6file-name-wizard
Audit all filename and naming conventions in the codebase against CLAUDE.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
6ctx
Use when starting a session on a project, returning after time away, or before making significant changes. Essential for building comprehensive understanding of project state through total recall and deep exploration.
5