sanctuary-spec-kitty
Sanctuary Spec-Kitty Configuration
Status: Active
Domain: Project Sanctuary
Depends on: spec-kitty-plugin (generic spec-driven development framework)
Purpose
This skill is the Sanctuary-specific glue layer that knows how to configure and use the generic spec-kitty-plugin for Project Sanctuary's development workflow.
The spec-kitty-plugin has two layers:
- Auto-synced commands (from upstream CLI) — generic, overwritten on update
- AUGMENTED.md files (our custom best practices) — project-specific, never overwritten
This skill documents what's Sanctuary-specific about our spec-kitty setup.
Sanctuary-Specific Configuration
Constitution
More from richfrem/project_sanctuary
excel-to-csv
>
1sanctuary-memory
Project Sanctuary-specific memory configuration. Maps the generic memory-management tiered system to Sanctuary's actual file paths, storage backends (RLM, Vector DB, Obsidian, HuggingFace), and persistence workflows.
1sanctuary-soul-persistence
Project Sanctuary-specific skill for managing Soul persistence to HuggingFace. Knows the exact .env parameters, discovery tags, dataset structure, and persistence workflows for this project. Uses the generic huggingface-utils plugin.
1sanctuary-obsidian-integration
Project Sanctuary-specific skill for managing the Obsidian vault as an external hippocampus. Knows the vault path, naming conventions, and integration patterns. Uses the generic obsidian-integration plugin.
1sanctuary-orchestrator-integration
Sanctuary-specific integration skill connecting the Guardian to the Agent Loops Orchestrator. Maps the Separation of Concerns between strategic workflow definition (Spec-Kitty), cognitive execution (Orchestrator tracks), and environmental sovereignty (Guardian closures).
1